Skip to main content
30 seconds

Install + first enrichment

One npx drops a SKILL.md into your repo so Claude / Cursor / Windsurf can call abm.dev natively. Then either pipe it through your AI agent or curl the API yourself.

Install

Requires Node 18+. Drops SKILL.md + .abm-dev.json into the current directory.

$npx -y @abmdev/cli@latest init --all -k <YOUR_API_KEY>

Prefer not to pass the key as a flag? Set it in your shell first and use -k env:

$export ABM_DEV_API_KEY=abmdev_live_…$npx -y @abmdev/cli@latest init -k env

Grab a key from Settings → API Keys.

First enrichment — via your AI agent

With the SKILL.md in place, hand this prompt to Claude / Cursor / Windsurf and let it drive the API for you. We’ve filled in Stripefrom your signup domain — swap it for any company you’d like to enrich.

I want to enrich a company with abm.dev.  Here's the
SKILL.md I dropped into the repo — read it and then call the API to
enrich "Stripe" (domain: stripe.com).  Use my ABM_DEV_API_KEY env
var for auth.  Return a short bulleted summary with citations.

First enrichment — direct curl

Or skip the agent and fire the API yourself. The response carries an enrichment ID you can poll on /v1/enrichments/{id} until status flips to completed.

$curl -X POST https://api.abm.dev/v1/enrichments \$  -H "Authorization: Bearer $ABM_DEV_API_KEY" \$  -H "Content-Type: application/json" \$  -d '{$    "type": "company",$    "input": { "companyName": "Stripe", "domain": "stripe.com" }$  }'

What you get back

Every value carries a source, confidence (0–1), and a citation URL. Conflicts between providers surface under conflicts. Streaming progress events are on /v1/enrichments/{id}/stream.

Environment variables

Useful for CI and ephemeral environments.

VariablePurpose
ABM_DEV_API_KEYLong-lived API key from /settings/api-keys.
ABM_DEV_BASE_URLOverride the gateway endpoint. Defaults to https://api.abm.dev.

Next steps