OutreachGraph now has an agent API: keys, dollar budgets, an inbox and suppress lists

OutreachGraph runs B2B outreach: it finds people, researches them, drafts grounded messages and sends within limits a policy engine enforces. Until today the only way to drive it from a script was a process-wide service token plus two headers naming the workspace. Now there is a proper surface for agents.

Read it the way an agent would. The quick guide is at https://outreachgraph.com/api/v1/public/llms.txt and the schema at https://outreachgraph.com/api/v1/public/openapi.json. Both are keyless and rendered from one table in the codebase, so a route cannot appear in one and not the other. A test refuses any documented route that does not exist.

What you can do with it

Everything lives under /api/v1/autogtm. A project is one product you sell. It has a daily ceiling in dollars and an autopilot switch. A campaign is one audience for one project, with its own daily limit, targeting, instructions and inbox.

curl -H "X-API-Key: og_live_..." https://outreachgraph.com/api/v1/autogtm/campaigns

The inbox is tabbed by who spoke last: need_reply, replied, sent, unsubscribed. A reply is text only. The subject and threading are handled, and the reply still passes the policy engine as a human-approved follow-up, so a lead who opted out cannot be written to. There is a hot-leads feed across campaigns that polls with a since parameter, named suppress lists for email addresses and company domains, and an import that makes a campaign from your own list of up to 5,000 leads per call.

Dollars become caps

A daily limit in dollars is stored on the campaign next to the cap the policy engine already reads. One contact costs what the smallest credit pack charges per credit, so ten dollars a day is sixty-six contacts a day. Turn autopilot on for a project and the ceiling is split across its campaigns by reply rate, with a fifth of it shared evenly so a new campaign is not starved before it has produced anything. The split is deterministic. The same numbers always give the same budgets.

Keys

Mint a key on the settings page. It is shown once, stored as a hash, and acts with your current role. Removing someone from the organization kills their keys. A key cannot mint keys.

What is not in this release

Lead data and a pre-warmed sending domain pool. Those are what an outreach vendor actually sells you, and they are bought, not built. Sends still leave through your own mailbox or ours.

This post was drafted with an AI assistant and edited by a human.