4 min read

Beta features & feature flags

Some of what abm.dev ships is still settling. We put those parts behind feature flags. You opt in, you get the new surface early, and you also accept that the shape can change before it’s final.

This article covers what “beta behind a flag” means, which surfaces are in beta today, and how to reach them.

What a feature flag is here

A flag is a switch on your account. Off by default. On when you turn it on. Nothing in beta changes your existing calls until you flip the switch.

Two rules hold for everything behind a flag:

The stable API keeps working. Beta is additive, not a migration.
Beta shapes can change. Treat field order, optional extras, and timing as provisional until the feature graduates.

No surprise migrations. No silent rewrites of what you already call.

The stable core (not a flag)

Everything below sits on the same foundation, so it helps to state it once.

Enrichment is one request. You send a type and an input.

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]" } ] }

Note

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

Each target also accepts a LinkedIn URL or a company domain.

You read the result back with its id:

HTTP

GET https://api.abm.dev/api/v2/enrichments/{id}
x-api-key: YOUR_API_KEY

The response carries eighty-nine canonical fields — forty-three for a person, forty-six for a company — plus forty signals. Ten sources resolve into one answer. Every value carries three things: its source (which provider it came from), a confidence score from zero to one, and a selection_reason (why that value was chosen).

Higher confidence means the sources agreed more. There are no bands and no thresholds to memorise — read the number, weigh it, decide. A value is either cited or it isn’t returned. No fabricated facts. See Confidence scores and Canonical fields.

Beta surface: streaming for agent loops

Long enrichments resolve ten sources. An agent in a loop doesn’t want to block on a single answer.

The beta surface is real-time streaming over SSE. Progress arrives as the enrichment runs, instead of one reply at the end. It’s built for agent loops — read partial state, decide, keep moving.

The stream is provisional. Event shape and ordering can change before it graduates. Confirm the current contract in the API reference before you depend on it.

Beta surface: webhooks on batch completion

For work you submit and walk away from, a webhook fires when the batch job finishes. You don’t poll. You get told.

What is not yet settled: the endpoint paths, headers, signatures, retry behaviour, and event names are not established here. Do not hard-code any of them from guesswork. The Jobs reference is the source of truth — check it before you build against batch webhooks.

How to reach abm.dev

Three ways in. Pick the one that matches how you work.

Claude

Add the MCP server. Settings → Connectors → Custom → paste https://mcp.abm.dev/mcp. The server exposes abm.dev’s enrichment tools inside Claude. The exact tool list isn’t verified here — see For agents.

Coding agents (Cursor, Claude Code, Windsurf)

Paste a prompt that tells the agent to read llms.txt, request a key, save it to a .env, run one test enrichment, and report back with citations. The agent wires itself up.

Scripts and terminal

Call the REST endpoint directly with x-api-key. See Getting started and For developers. A CLI exists; treat its binary name, commands, and flags as unverified and read the CLI docs for specifics.

Turning a flag on

Feature flags are an account setting. Where exactly to toggle them in your dashboard isn’t documented here — start from the relevant reference ( enrichment, jobs) and open a support ticket if you need a flag enabled.

What beta does not change

Pricing. Per-enrichment, no subscription. Credits never expire. All ten sources included, no per-source bills and no per-field charges. From about €0.29 per enrichment. See pricing.
Honesty. A value is cited or it isn’t returned. No silent fallbacks. Beta doesn’t loosen that.
Your stable calls. They keep working exactly as before.

The playground is free — try a flagged surface there before you ship against it.

Who runs it

abm.dev is account-based marketing for AI agents, operated by Foxley Farm Operations Ltd (UK Company No. 16392009, Oakham, United Kingdom). GDPR-compliant.