Integrations

This page covers how the things you already use reach that data: Claude and other agents, scripts and terminals, and the HubSpot, LinkedIn, Notion, and Slack workflows people ask about most.

Two ways in

There are two surfaces. Pick by where the work happens.

• Agents talk to the MCP server. The agent calls abm.dev as a tool, mid-conversation.
• Scripts and terminals call the REST API directly. Two endpoints, one key.

Everything below is one of those two.

Claude and other MCP agents

The MCP server lives at:

https://mcp.abm.dev/mcp

It exposes abm.dev’s enrichment tools inside Claude. The exact tool list is unverified here — see /for-agents for what’s available.

Claude. Settings → Connectors → Custom → paste the URL above. Claude can then enrich a person, company, or domain inside a conversation.

Cursor, Claude Code, Windsurf. No menu. Paste a prompt that tells the agent to do the setup itself:

The agent reads the machine-readable docs, provisions itself, and proves the round trip before it touches your real data. See /for-agents.

Scripts and the terminal: the REST API

Two endpoints. Submit an enrichment, then read it back.

POST https://api.abm.dev/api/v2/enrichments
GET  https://api.abm.dev/api/v2/enrichments/{id}

Headers:

x-api-key: YOUR_API_KEY
Content-Type: application/json

Body — each target accepts an email, a LinkedIn URL, or a company domain:

{
  "targets": [
    { "type": "person", "email": "[email protected]" }
  ]
}

The response is eighty-nine canonical fields — forty-three for the person, forty-six for the company — plus forty signals. Each value carries its source, a confidence score from 0 to 1, and a selection_reason. Higher confidence means more of the ten sources agree. No fabricated facts. A value is cited or it is not returned. Field and concept detail: canonical fields, confidence scores, data sources.

Full request and response shapes: /api-reference/enrichment. For the command-line workflow, /docs/cli is the source of truth — treat any specific binary name, command, or flag as unverified until you read it there.

Real time and batch

Two modes, depending on how the work arrives.

• Agent loops get real-time results over SSE streaming — the answer arrives as it resolves, not after a poll.
• Batch jobsfire a webhook when they finish, so you don’t sit on a GET.

Webhook endpoint paths, headers, signatures, and retry behaviour are not documented here — see /api-reference/jobs before wiring one up.

HubSpot, LinkedIn, Notion, Slack

The honest version. These are workflows, not buttons.

abm.dev’s job is the enrichment. It returns clean, cited fields and signals over the REST API and the MCP server. What you do with those fields — write them to a HubSpot record, attach them to a LinkedIn prospecting list, drop them into a Notion database, post a summary to Slack — runs in your agent, your script, or the tool’s own automation. abm.dev supplies the data; the destination is yours.

• LinkedIn is both an input and a source. You can enrich from a LinkedIn profile URL (pass it as the input), and LinkedIn is one of the ten sources behind the response. Setup notes: /docs/integrations/linkedin.
• HubSpot — keep CRM records current by enriching on the email or domain you already hold, then writing the fields back from your own automation. /docs/integrations/hubspot.
• Notion — enrich a row, store the cited fields alongside it. (Roadmap — drive it from the API today.)
• Slack — surface an enrichment or a signal where the team already talks. (Roadmap — drive it from the API today.)

The exact connection steps for each live in their own pages above. Where a page claims a capability that isn’t reflected in the API reference, trust the API reference.

What it costs

Per enrichment. No subscription. Credits never expire. All ten sources included in the price — no per-source bills, no per-field charges, no silent fallbacks. From about €0.29 per enrichment. Packs:

The playground is free. New accounts get launch credits with the code LAUNCHCODES. Full pricing: /#pricing.

Start

1. Sign up and grab a key.
2. Try a request in the free playground.
3. Agents: paste https://mcp.abm.dev/mcp into Claude, or hand your coding agent the prompt above.
4. Scripts: read getting started and the API reference.

Built for developers and agents. /for-developers · /for-marketers.

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