4 min read

REST from an agent

A script is the shortest path to abm.dev. No SDK. No client library. One endpoint, one key, one header. The agent here is yours — a cron job, a bash one-liner, a Python worker, a terminal session. They all speak the same REST.

What you need

An API key. Sign up, then create one from your dashboard.
A terminal that can make an HTTPS request. curl is enough.

New accounts get free launch credits with the code LAUNCHCODES. The playground is free if you want to feel the shape of a response before you write a line of code.

The one call

Send a POST to the enrichment endpoint. Identify what you want — a person or a company — and give it something to start from: an email, a LinkedIn URL, or a company domain.

Bash

curl -X POST https://api.abm.dev/api/v2/enrichments \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"targets":[{"type":"person","email":"[email protected]"}]}'

Note

Send your key as either x-api-key (used here) or Authorization: Bearer on POST /api/v2/enrichments. The full, live contract is at the API reference.

Swap the target for what you have:

JSON

{"targets":[{"type":"company","domain":"acme.com"}]}

A LinkedIn URL works too. The full request and response contract lives at /api-reference/enrichment.

Reading the result

You get one resolved record. Eighty-nine canonical fields — forty-three for a person, forty-six for a company — plus forty signals. Ten sources, among them LinkedIn, Companies House, Perplexity, Tavily, and Hunter, are resolved into a single answer.

Every value carries its receipts:

source — which provider it came from.
confidence— a score from zero to one. Higher means the sources agree more; lower means they don’t. Read it qualitatively, not as a pass/fail line. More on the scale at /docs/concepts/confidence-scores.
selection_reason — why that value was chosen.

A value is cited or it is not returned. No fabricated facts. No silent fallbacks. The shape of the field set is documented at /docs/concepts/canonical-fields, the sources at /docs/concepts/data-sources.

Fetching it again

Each enrichment can be read back by its identifier:

Bash

curl https://api.abm.dev/api/v2/enrichments/THE_ID \
  -H "x-api-key: YOUR_API_KEY"

Use this to poll a result or to re-read one you ran earlier. The identifier and the exact response envelope are defined in the API reference — follow it rather than guessing the field names.

Inside an agent loop

If your script is the inner loop of a long-running agent, abm.dev streams progress over SSE in real time, so the agent can act as the answer assembles rather than waiting on a single blocking response. For batch work, jobs can notify you when they finish. The mechanics of streaming and job completion are documented at /api-reference/jobs — read it there; the specifics aren’t restated here.

A terminal agent, not a script

Running this through Cursor, Claude Code, or Windsurf instead of a hand-written script? Don’t dictate the call. Hand the agent the map and let it work:

Hand the agent this

Read https://abm.dev/llms.txt. Request an abm.dev API key, save it to .env, run one test enrichment, and report back with the citations on each field.

That’s the whole onboarding. The agent reads the contract, gets a key, proves it works, and shows its sources. See /for-agents for the agent-first walkthrough.

If you’d rather wire abm.dev into Claude directly, the MCP server at https://mcp.abm.dev/mcp exposes abm.dev’s enrichment tools inside Claude — in Claude, go to Settings → Connectors → Custom and paste the URL. The exact tool list is unverified here; see /for-agents.

What it costs

Pay per enrichment. No subscription. Credits never expire, and all ten sources are included in the price — no per-source bills, no per-field charges. Enrichments start at about €0.29.

Packs:

thirty — €2.89
one hundred — €9.29
five hundred — €36.99 (best value)
two thousand — €119.99

Full pricing at /#pricing.

If something fails

Read your request body against the enrichment reference. The body shape is small and exact.
Confirm the endpoint and the auth header against the live API reference — the surfaces disagree (see the Note above).
Start at /docs/getting-started if you’re setting up for the first time.
Still stuck? Open a ticket.

A command-line tool is also on offer; the binary, install, and commands are the source of truth at /docs/cli rather than here.

abm.dev is operated by Foxley Farm Operations Ltd (UK Company No. 16392009), Oakham, United Kingdom. GDPR-compliant.