Agentic software should be a dependency. Dependencies should behave.
AstroFabric exists because go-to-market data kept shipping as dashboards and exports while the people building pipeline needed agents: capability that sources, enriches, verifies and delivers, under rules, with receipts. Agentic AI for Business Intelligence, in seven positions, each checkable in the product.
The API is the product
We built a full dashboard first. It was pretty, and it sat between the data and the people who wanted to act on it. So we deleted it: tens of thousands of lines of UI, gone in one commit. What survived is the part that did the work, exposed as endpoints. The console we ship today is a window onto those same functions - every button calls the API you can call - and your product, your cron jobs and your own AI agents are equally first-class front-ends, because they can act.
curl -X POST .../api/v1/agents/prospecting \
-H "Authorization: Bearer ek_live_..." \
-d '{"input": {"icp": "US fintech, 50-500 employees",
"count": 100, "verify": true}}'
{ "ok": true, "status": "completed",
"output": { "list_id": "lst_8f2c", "rows": 100, ... } }Agents are first-class callers
Half the requests hitting this platform will come from software that reasons. That changes the contract: every tool carries a machine-readable schema, every error is structured enough for a model to recover from, and the MCP server exposes the same catalog under the same scopes and meters as REST. An assistant with your key can build a real list and can never outspend your workspace.
{
"mcpServers": {
"astrofabric": {
"url": ".../api/mcp"
}
}
}
// one permission entry;
// the whole platform behind itCredentials are our problem
Ad platforms guard their audience APIs with developer tokens, partner reviews and app audits that take weeks. We hold those approvals so you do not have to: connect an ad account with an OAuth click and the platform stages and pushes audiences through managed partner credentials. The same goes for your CRM and outreach tools. You bring the account. We bring the access.
Budgets are enforced, never advised
Every workspace runs under a credit grant the ledger treats as law. Paid data calls reserve credits before they execute and settle after; a lookup that finds nothing settles at zero. Under pressure the platform degrades freshness first, fidelity second, coverage last, and at the ceiling it stops with a 402 you can catch in code. A platform that cannot stop spending is a liability with a nice logo.
Isolation is structural
Tenant scoping is not a code-review convention here. The data layer exports no unscoped query path, every read and write is bound to a workspace resolved against the database, and row-level security stands behind that as a second line. Your lists, your suppression lists and your audiences are yours alone; careless code returns zero rows instead of someone else’s data.
Worst cases are bounded by construction
When an agent pushes an audience, it lands staged. Nothing reaches an ad platform until a person on your team approves it, the identifiers are hashed before they leave, and the push is idempotent so a retry can never upload twice. If the platform cannot confirm the match, the audience is marked failed and targets nobody. The worst case is a staged audience waiting for a decision, by construction.
Data is licensed, never scraped
Every company and person record on this platform comes from licensed business data providers under contract, queried source by source with the specific question your list needs. The platform never scrapes member networks, never logs in anywhere as you, and never messages anyone on your behalf. Audiences are hashed before they leave; suppression lists are honoured on every list and every push. Data you can build a business on has to be data you are allowed to use.
Positions are cheap. Products are proof.
Open a workspace, read the docs, build a list - every claim on this page is live in the platform.