Skip to main content
abm.dev
3 min read

Getting support

Something broke. A field came back empty. The agent connected, then didn’t. Whatever it is, this is where you tell us.

Open a ticket

One door. Open a support ticket.

Tell us what you expected and what happened instead. The more concrete, the faster the fix.

Include, where you have them:

  • The request you sent. The endpoint, the body shape, the response — minus your key.
  • A timestamp. When it happened, with a rough timezone.
  • For an enrichment, the id you got back from POST /api/v2/enrichments. That id is the thread we pull.

Keep secrets out of tickets

Never paste your API key, a password, or anyone’s raw personal data into a ticket. We don’t need it to help, and you shouldn’t send it.

Before you write: try the docs

Most answers are already written down. A few good starting points:

If the answer’s there, you skip the wait.

The enrichment call

Two endpoints. You create an enrichment, then you read it back.

HTTP
POST https://api.abm.dev/api/v2/enrichments
x-api-key: YOUR_API_KEY
Content-Type: application/json

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

Each target also takes a LinkedIn URL or a company domain. To read a result back:

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

Note

Send your key as either the x-api-key header (used here) or Authorization: Bearer on POST /api/v2/enrichments. The full, live contract is at the API reference before you build, and tell us in your ticket which one you used.

A few things people ask about first

A field came back empty.

That’s by design. abm.dev cites a value or it doesn’t return one. No guesses, no silent fallbacks. Every value that does come back carries its source, a confidence score from zero to one, and a selection_reason — why that value was chosen. A higher confidence means more of the sources agreed. See /docs/concepts/confidence-scores.

The agent won’t connect.

The MCP server lives at https://mcp.abm.dev/mcp. In Claude, add it under Settings → Connectors → Custom and paste the URL. That server exposes abm.dev’s enrichment tools inside Claude; the exact list of tools isn’t documented here — see /for-agents. For Cursor, Claude Code, or Windsurf, point the agent at /docs/getting-started and have it request a key and run a test enrichment.

A charge looks wrong.

Pricing is per enrichment. No subscription, no per-seat fee, no per-field charge, no per-source bill. Credits never expire, and all ten sources are included in every call. Rates start around €0.29 per enrichment; packs run from thirty credits at €2.89 up to two thousand at €119.99. The full breakdown is at /#pricing. If a charge still doesn’t add up, open a ticket and quote the enrichment id.

You don’t have a key yet.

Sign up, then try the free playground. New accounts can claim free launch credits with the code LAUNCHCODES.

Who you’re writing to

abm.dev is account-based marketing for AI agents — eighty-nine canonical fields and forty signals, resolved from ten data sources into one cited response.

The service is operated by Foxley Farm Operations Ltd (UK Company No. 16392009), Oakham, United Kingdom. Data handling is GDPR-compliant.

When in doubt, open a ticket. A real person reads it.