canonical: https://jentic.com/apis/abm.dev/abm

# ABM.dev API

The ABM.dev API enriches B2B people and company records and returns every field with a citation to its source and a confidence score. It runs enrichment jobs, people-finder jobs that locate contacts at target accounts, and account-based campaigns that surface candidates for review, with progress streamed as jobs run. Enriched results can be previewed as a diff and written back to a connected CRM.

## For AI agents

Enrich and source B2B people and company data with every field cited to a source and confidence score, then preview and write the results back to your CRM. Runs enrichment, people-finder, and account-based campaign jobs.

## Scope

Does not handle email sending, ad buying, or deal pipeline management. Use for B2B people and company data enrichment only.

## Capabilities

- Enrich B2B people and company records with every field cited to a source and a confidence score
- Find contacts at target companies through people-finder jobs and stream their progress
- Run account-based campaigns that surface candidate contacts for review and approval
- Preview a CRM writeback diff before pushing enriched fields back to your CRM
- Inspect the source breakdown and field-level attribution behind each enriched record
- Start batch enrichments from an uploaded spreadsheet of companies

## Use cases

### Agent-driven account research

An AI agent researching a target account can create an enrichment, stream its progress, and read back each field alongside the source and confidence that produced it. Because the ABM.dev API cites every value, the agent can decide whether a contact meets a confidence threshold before acting on it rather than trusting an uncited guess.

Example prompt: Create an enrichment for a company domain, stream progress until it completes, then read the field attribution to keep only values above a confidence threshold

### CRM hygiene with reviewed writeback

Keeping a CRM current usually means trusting a bulk sync that can overwrite good data. The ABM.dev API lets a team preview the exact writeback diff first, so a reviewer sees which fields would change and which source each new value came from before approving. Approved changes are then pushed back to the connected CRM.

Example prompt: Preview the writeback diff for an enrichment, approve it, then execute the writeback to the connected CRM

### People finding for ABM campaigns

A sales team targeting a set of accounts needs named contacts in specific roles. The ABM.dev API runs people-finder jobs against a company list and campaigns that return candidate contacts with their citations, so the team approves real people rather than scraping and guessing. Jobs stream progress so long-running searches can be polled.

Example prompt: Create a people-finder job for a list of company domains and poll the job until it returns candidate contacts with sources

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v1/enrichments` | Create an enrichment job |
| GET | `/v1/enrichments` | List enrichment jobs |
| GET | `/v1/enrichments/{id}/sources` | Get the source breakdown for an enrichment |
| POST | `/v1/people-finder` | Create a person finder job |
| POST | `/v1/campaigns/confirm` | Confirm and start an account-based campaign |
| POST | `/v1/enrichments/{id}/writeback` | Execute the CRM writeback for an enrichment |

## Key resources

- **Enrichments** — Create, list, stream, approve, and write back enrichment jobs, with source and field attribution
- **People finder** — Run and poll jobs that locate contacts at target companies
- **Campaigns** — Run account-based campaigns and review candidate contacts before approval
- **CRM config** — Manage CRM integrations, platform health, and field mappings for writeback

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 64 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 82 / 100
  - Developer Experience & Jentic Compatibility: 59 / 100
  - AI-Readiness & Agent Experience: 46 / 100
  - Agent Usability: 91 / 100
  - Security: 63 / 100
  - AI Discoverability: 72 / 100
- **View full report:** https://jentic.com/apis/abm.dev/abm/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the ABM.dev API by hand means handling its two credentials (an X-API-Key header for the API and a Clerk JWT bearer for signup), its streamed job progress, and CRM writeback config yourself. Through Jentic you install once, import ABM.dev from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** Jobs are addressed by an id in the URL path, but a rule bounds which operations your agent may call rather than which record it touches. You choose the operations it may call, such as creating and reading enrichments, so a CRM writeback execution or an API key revocation is not included unless you add it.
- **Credential handling:** Your ABM.dev credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'enrich a company with contacts' or 'find people at a target account', and Jentic returns the matching ABM.dev operation with its input schema so the agent calls the right endpoint without reading the reference docs.

## Related APIs

- **Apollo** — Apollo offers B2B contact and company data with outreach built in, where ABM.dev focuses on cited enrichment and CRM writeback.
- **People Data Labs** — People Data Labs provides person and company datasets for bulk enrichment, where ABM.dev adds per-field citations and campaign workflows.
- **Clearbit** — Clearbit adds firmographic attributes to a company ABM.dev has identified.
- **FullContact** — FullContact resolves and enriches individual contact identities found through ABM.dev.

## FAQ

### What authentication does the ABM.dev API use?

The ABM.dev API authenticates API calls with an API key sent in the X-API-Key header, and uses a Clerk-issued JWT bearer token for the organization signup bootstrap, as declared in its OpenAPI spec. Through Jentic the credential is stored once and injected at call time, so it never appears in your agent's prompt or logs.

### Can I see which source supplied each enriched field from the ABM.dev API?

Yes. Every enrichment carries a source breakdown and field-level attribution, so for each value the API returns which source produced it and the confidence score, letting an agent gate on confidence before acting.

### What are the rate limits for the ABM.dev API?

The OpenAPI spec does not state numeric rate limits for the ABM.dev API. Check the vendor documentation at https://abm.dev for current limits before running large batch enrichments.

### How do I enrich a company through Jentic with the ABM.dev API?

Search Jentic for 'enrich a company with contacts', which returns the POST `/v1/enrichments` operation with its input schema, then stream progress and read the result. To run it on your own infrastructure, install Jentic One from its GitHub repo.

### Can I limit what my agent is allowed to do with the ABM.dev API?

Yes. Write a rule that allows only the enrichment and people-finder read and create operations, so the agent can research and enrich accounts but cannot execute a CRM writeback or revoke an API key, and every call it makes is logged. You decide which operations are in the rule, so nothing destructive runs unless you add it.