01Why this exists
Outbound runs on a stack of eight tools: a lead database, an enrichment waterfall, an email verifier, an intent feed, a domain registrar, a mailbox provider, a sequencer and a reply inbox. Each has its own login, its own plan, its own API and its own idea of what a contact is. A person can juggle them. An AI agent cannot — it has no dashboard to click through and no patience for eight billing relationships.
We wanted to hand an agent a single key and say: find fifty executives at healthcare companies hiring sales leaders, get their verified emails, draft the campaign and wait for me to approve it. Nothing on the market could do that on one credential. So we built the thing that does.
The model is the one OpenRouter proved for language models: one key, one balance, and the best provider routed behind each call. GTMRouter does that for go-to-market.
02What it is
GTMRouter is a unified go-to-market API for AI agents. Nine verbs cover the loop — find leads, find intent, enrich, verify, set up sending, create and launch campaigns, read replies, and call an LLM — and every verb is both a REST endpoint and a tool on our hosted MCP server. Claude, Cursor, Codex and ChatGPT can use it directly; so can anything that speaks HTTP.
It is paid for in prepaid credits, spent only on outcomes: a lead returned, an email verified, a company with a real signal. A miss costs nothing. There are no seats, no plans and no minimum spend beyond the first top-up. New accounts start with free credits and no card.
Underneath, each verb is routed across specialist data and sending providers through a single adapter interface. When one provider misses, the next is tried; when one is down, the verb stays alive. You never see a provider name in a response — you see a result and its exact charge.
03How we run it
- Humans approve what money and reputation depend on. An agent can research and draft freely, but buying sending capacity and launching a campaign each wait for a person to confirm in the console. The server enforces it; there is no flag to turn it off.
- Opt-outs are permanent. A reply, an unsubscribe or a bounce suppresses the address across the workspace for good, at draft time, at launch and mid-flight.
- Every charge is disclosed, and settled once. The response envelope tells you what a call cost. An append-only ledger is the only source of truth for balances; retries with the same idempotency key replay the result without charging again.
- Boring reliability over clever features. Encrypted backups every twelve hours in two places, restores tested, an audit trail on every administrative action, and no passwords anywhere to leak.
- No lock-in. Export your data whenever you like. Your API key works in any client; the OAuth flow exists so directories can list us, not so we can hold you.
04Who is behind it
GTMRouter is built by a small team in the United Kingdom that runs its own outbound through the API every day. It started as the tool we wished existed; it stays honest because we are also its most demanding customer.
We are in beta and shipping most days. The changelog is the truthful record of what changed and when, including prices.
05Talk to us
Questions, partnership ideas, a verb you need, a provider you think we should route to, or something that looks wrong: write to founders@gtmrouter.dev. A person reads every message.
Prefer to see it first? Same address, subject “demo”, and we will walk you through it on your own use case.