canonical: https://jentic.com/apis/enigma.com/enigma

# Enigma Public API

Enigma's Public API provides U.S. small-business identity, financial profile, Know Your Business (KYB) verification, and sanctions screening from a curated set of public records sources. Four operations cover the core flows: match a noisy business string to a canonical record, retrieve a full profile by ID, run KYB verification on a company, and screen against sanctions and watchlists. The API is designed for fintech, insurance, and lending teams who need to identify and de-risk SMB customers programmatically.

## For AI agents

Match U.S. businesses to canonical records, retrieve firmographic profiles, run KYB checks, and screen against sanctions lists.

## Scope

Does not handle consumer KYC, international company data, or credit underwriting decisions - use for U.S. small-business match, profile lookup, KYB, and sanctions screening only.

## Capabilities

- Match a fuzzy business name and address string to a canonical Enigma business record
- Retrieve a full business profile by Enigma business ID for downstream enrichment
- Run a Know Your Business verification on a company to satisfy onboarding requirements
- Screen a business against sanctions and watchlist sources to flag compliance risk
- Use match scores and confidence values to gate automated underwriting decisions

## Use cases

### SMB Onboarding KYB

Run KYB verification on small-business customers during onboarding by calling POST /v1/kyb with the supplied business details. Enigma returns identity, status, and signal data drawn from public records, allowing fintechs and lenders to satisfy compliance obligations before extending services. Replaces multi-vendor manual lookups with a single API call.

Example prompt: Call POST /v1/kyb with the business name 'Acme Bakery LLC', EIN, and street address, then surface the verification status and any flagged signals.

### Lead-to-Account Match for CRM Enrichment

Take a noisy business string entered on a marketing form and resolve it to a canonical Enigma record via POST /businesses/match. Use the returned ID with GET /businesses/{id} to pull the full profile and write firmographics back into the CRM. This eliminates manual research time on inbound leads and standardises company records across systems.

Example prompt: Send POST /businesses/match with name 'acme bakery brooklyn' and address '123 Main St', then call GET /businesses/{id} on the top match to load the full profile.

### Sanctions Screening for Compliance

Screen a counterparty against sanctions and watchlist sources using POST /evaluation/sanctions/screen before approving a transaction or onboarding a vendor. The endpoint returns hit data with source attribution so the compliance team can review and clear or escalate. Useful for OFAC and similar screening obligations.

Example prompt: Call POST /evaluation/sanctions/screen with the business identifier and review any returned hits before approving the counterparty.

### AI Agent KYB Through Jentic

An AI agent runs structured KYB verification on inbound business applicants by discovering Enigma's POST /v1/kyb operation through Jentic, loading its schema, and executing the check. The Enigma API key stays in your Jentic One instance. The agent can chain match, profile retrieval, and sanctions screening into a single decision.

Example prompt: Search Jentic for 'verify a small business', load the Enigma KYB operation, and execute it with the applicant's business name and EIN.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /businesses/match | Match a noisy business string to a canonical record |
| GET | /businesses/{id} | Retrieve a business profile by Enigma ID |
| POST | /v1/kyb | Run a KYB verification on a business |
| POST | /evaluation/sanctions/screen | Screen a business against sanctions sources |

## Key resources

- **Match** — Resolve a fuzzy business string to a canonical Enigma business record via POST /businesses/match.
- **Lookup** — Retrieve a full business profile by Enigma ID via GET /businesses/{id}.
- **KYB** — Run Know Your Business verification on a small business via POST /v1/kyb.
- **Screening** — Run sanctions and watchlist screening via POST /evaluation/sanctions/screen.

## Why Jentic

- **Setup:** Wiring Enigma by hand means handling its x-api-key header auth, learning the split between the POST match and KYB calls that take a business in the request body and the GET lookup keyed on a business id, and building your own retry handling against api.enigma.com. Through Jentic you install once, import the Enigma Public API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Enigma sends the match, KYB, and sanctions-screen targets in the request body rather than the URL, so scope the agent to the operations it needs, such as POST /businesses/match or POST /evaluation/sanctions/screen. You pick that allowed set, so an operation like the KYB call at POST /v1/kyb is only reachable if you include it.
- **Credential handling:** Your Enigma API key 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 'verify a U.S. small business' or 'screen a company against sanctions lists', and Jentic returns the matching Enigma operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Clearbit** — Company and contact enrichment API with broader B2B coverage
- **FullContact** — Identity resolution and contact enrichment API
- **HubSpot** — Write enriched Enigma firmographics back into HubSpot company records

## FAQ

### What authentication does the Enigma Public API use?

The Enigma Public API uses an API key passed in the x-api-key header on every request. Through Jentic the key is stored in your Jentic One instance and injected at execution time so it never enters the agent context.

### Can I run KYB verification with the Enigma API?

Yes. POST /v1/kyb runs a Know Your Business check on a small business and returns identity and risk signals drawn from public records. It is the dedicated endpoint for compliance-grade verification.

### How does the Enigma API handle fuzzy business name matching?

POST /businesses/match accepts a noisy business name and address string and returns ranked candidate records with confidence scores. Use the top match's id with GET /businesses/{id} to load the full profile.

### What are the rate limits for the Enigma API?

The OpenAPI spec does not publish explicit rate limits. Limits are tied to your Enigma account plan; contact Enigma's API support if you need higher throughput for bulk match or KYB workloads.

### How do I screen a business for sanctions hits through Jentic?

Search Jentic for 'screen a business for sanctions', load the POST /evaluation/sanctions/screen operation, and execute it with the business identifier. Get started with Jentic One, the self-hosted execution layer.

### Does Enigma cover non-U.S. businesses?

Enigma's Public API is focused on U.S. small businesses drawn from U.S. public records sources. For international company data, pair Enigma with a complementary global firmographics provider.

### Can I limit what my agent is allowed to do with the Enigma Public API?

Yes. Because you run Jentic One yourself, your own rules decide which Enigma operations and credentials the agent may use. Since Enigma sends the match, KYB, and sanctions-screen targets in the request body rather than the URL, you scope the agent to just the operations it needs, such as POST /businesses/match or POST /evaluation/sanctions/screen. You pick that allowed set, so the KYB call at POST /v1/kyb is only reachable if you include it.