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

# Enigma Business API

Jentic publishes the only available OpenAPI specification for Enigma Business API, keeping it validated and agent-ready. Enigma's Business API exposes US small business data: business matching from partial inputs, identity lookup by Enigma ID, KYB (know your business) verification, and OFAC and global sanctions screening for entities and beneficial owners. The 4-endpoint surface is purpose-built for fintech onboarding, lending, and compliance workflows that need to verify a business is real, active, and not on a sanctions list before opening accounts or extending credit.

## For AI agents

Match US small businesses from partial inputs, look up business identity records, run KYB verification, and screen entities against OFAC and global sanctions lists.

## Scope

Does not handle individual KYC document verification, credit bureau scoring, or transaction monitoring - use for US business matching, KYB, and sanctions screening only.

## Capabilities

- Match a business record from partial inputs like name, address, or phone
- Retrieve a full business identity profile by Enigma business ID
- Run a KYB verification request that returns identity confidence and risk signals
- Screen a business or individual against OFAC and global sanctions lists
- Resolve duplicate or thin business records into a single canonical entity

## Use cases

### Merchant Onboarding KYB

Run know-your-business checks on new merchants applying to a payments or lending platform. Match the applicant against Enigma's US small business data, fetch the identity record, and run a KYB call that returns confidence in legal name, address, and operating status. Replaces manual document review with structured, auditable risk signals in seconds.

Example prompt: POST `/businesses/match` with applicant business name and address, then POST `/v1/kyb`/ with the returned business ID to obtain a KYB verification result

### Sanctions Screening at Application

Screen a business and its beneficial owners against OFAC and global sanctions lists at the point of application. The `/evaluation/sanctions/screen` endpoint returns matches with confidence scores so compliance teams can investigate rather than block on every fuzzy hit. Reduces false positives compared to keyword-only screening.

Example prompt: POST `/evaluation/sanctions/screen` with the business legal name and country to receive sanctions match candidates with confidence scores

### Lending Risk Decisioning

Enrich a small business loan application with Enigma's identity data before underwriting. Match on submitted application fields, retrieve the business profile by ID, and feed firmographic signals into the risk model. Improves matching against thin-file applicants where partial inputs are common.

Example prompt: GET `/businesses/{id}` with the matched Enigma business ID to retrieve operating status, address, and identifiers for the underwriting model

### AI Agent Compliance Check via Jentic

An AI agent automating merchant or borrower intake can call Enigma through Jentic to run business match, KYB, and sanctions screening as a single decisioning step. Jentic isolates the x-api-key credential and exposes the four operations as discoverable tools, so the agent only needs the input schema, not the docs.

Example prompt: Search Jentic for 'verify a business and screen for sanctions', chain POST `/businesses/match` > POST `/v1/kyb`/ > POST `/evaluation/sanctions/screen` and return a single decision payload

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/businesses/match` | Match a business from partial inputs |
| GET | `/businesses/{id}` | Retrieve a business identity profile by ID |
| POST | `/v1/kyb/` | Run KYB verification on a business |
| POST | `/evaluation/sanctions/screen` | Screen a business or individual against sanctions lists |

## Key resources

- **Match** — Match a business from partial inputs to an Enigma business ID
- **Identity** — Retrieve a full business identity profile by ID
- **KYB** — Run KYB verification on a matched business
- **Screening** — Screen entities and individuals against OFAC and global sanctions lists

## Why Jentic

- **Setup:** Wiring Enigma by hand means setting up its API key auth and coding your own calls to the business match, KYB, and sanctions screening endpoints. Through Jentic you install once, import the Enigma Business API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Enigma puts the business id in the URL path (`/businesses/{id}`) for lookups, while match, KYB, and screening targets travel in the request body, so limit the agent to the operations it needs, such as reading a business or running a sanctions screen. Every operation you grant is your explicit choice.
- **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 'match a US business by name' or 'screen a business against sanctions', 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

- **OpenCorporates** — Global company registry data covering jurisdictions outside Enigma's US small business focus
- **Onfido** — Identity verification for individuals via document and biometric checks
- **Clearbit** — B2B data enrichment focused on firmographic and contact data for sales and marketing

## FAQ

### Why is there no official OpenAPI spec for Enigma Business API?

Enigma does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Enigma Business API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

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

Enigma uses an API key passed in the x-api-key request header. Through Jentic, the key is stored in the encrypted vault and injected at execution time so it never enters agent context.

### Can I match a business from partial information like just a name and ZIP?

Yes. POST `/businesses/match` accepts partial inputs (name, address fragments, phone) and returns ranked candidates with match confidence. Take the top candidate's ID into GET `/businesses/{id}` for the full identity record.

### Does this API cover sanctions screening for individuals as well as businesses?

Yes. POST `/evaluation/sanctions/screen` accepts both business legal names and individual names (useful for screening beneficial owners) against OFAC and global sanctions lists.

### How do I run a complete KYB and sanctions check through Jentic?

Run pip install jentic, then search 'verify a business and screen for sanctions'. Jentic returns the match, KYB, and screening operations with their schemas. Chain them in sequence, passing the matched business ID into the KYB call and the legal name into the screening call.

### Does Enigma cover non-US businesses?

The match and KYB endpoints are focused on US small business data. The sanctions screening endpoint covers global lists (OFAC plus international consolidated lists). For non-US business matching, pair with OpenCorporates or similar global business registries.

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

Yes. Because Jentic One is self-hosted, you decide which Enigma operations your agent can call and which credential it uses. You can grant only the operations the task needs, for example allowing a read of a business profile by ID (GET `/businesses/{id}`) or a sanctions screen (POST `/evaluation/sanctions/screen`) while withholding business match (POST `/businesses/match`) or KYB verification (POST `/v1/kyb`/). Every operation the agent can reach is one you explicitly grant.