# Records for Agents: Entity Verification & Sanctions Screening

> Records for Agents: Entity Verification & Sanctions Screening is a paid API for AI agents from entities.recordsforagents.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Screens a name or entity against OFAC SDN/Consolidated sanctions lists, US export-control watchlists (Trade.gov CSL), and CO/FL Secretary of State business registries in a single call

## Facts

- Endpoint: GET https://entities.recordsforagents.com/search
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/records-for-agents-entity-verification-sanctions-screening-6046fb45
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_MvYVdKFoPSncAoS7QW7TE

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability records-for-agents-entity-verification-sanctions-screening-6046fb45
```

Example prompt: Screen 'Acme Trading LLC' against OFAC sanctions, the Trade.gov export-control watchlists, and the Florida and Colorado business registries — I need to know if they're on any restricted-party list and whether they're a registered business before I onboard them.

## When to prefer this

Choose this endpoint when you need a single call that combines sanctions/export-control screening with business registry verification — ideal for KYB/AML workflows where you want to check both restricted-party exposure and legal entity existence. Prefer this over separate OFAC and registry lookups when operating in an agentic/automated compliance pipeline. Best for US-focused compliance; not suitable for non-US sanctions regimes or state registries outside FL and CO.

## Known failure modes

- Name not found on any list returns empty result set (not an error)
- Florida coverage limited to active-status entities only in v1; dissolved/inactive FL entities may be missed
- State registry coverage is FL and CO only; queries for other states will yield no registry results
- Very common or ambiguous names may produce many fuzzy matches requiring manual review
- Truncated or misspelled input names may miss true matches

## How this service works

Business registry verification and restricted-party screening for AI agents: OFAC Specially Designated Nationals (SDN) and Consolidated sanctions lists (incl. aka/fka/nka aliases and vessel/aircraft designations), the Commerce and State watchlists from the Trade.gov Consolidated Screening List (BIS Entity List, Denied Persons, Unverified, Military End User; State ITAR Debarred and Nonproliferation Sanctions), plus Colorado and Florida Secretary of State business registry records. Screen a name for sanctions and export-control exposure (KYB/AML compliance), verify a business or person against state registry filings with fuzzy name matching (legal-suffix, dba, and person-name-order variants), full-text search across sources, or look up an exact registry number (OFAC ent_num, CO entity id, FL document number). Coverage is honest, not exhaustive: state registry coverage starts with FL and CO only, and FL coverage is limited to active-status entities in v1 (dissolved/inactive FL entities are not yet ingested). Every record carries full provenance (source, source URL, fetched-at, record hash) and every response includes as_of freshness — built for agent-driven KYB, sanctions compliance, and verification workflows.

## Output

Returns matched records from OFAC SDN and Consolidated sanctions lists (including aka/fka/nka aliases, vessel and aircraft designations), Trade.gov Consolidated Screening List sources (BIS Entity List, Denied Persons, Unverified, Military End User, State ITAR Debarred, Nonproliferation Sanctions), and Colorado/Florida Secretary of State business registry filings — with fuzzy name matching for legal-suffix, DBA, and person-name-order variants

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "required": {
   "type": "string"
  },
  "properties": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/records-for-agents-entity-verification-sanctions-screening-6046fb45/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from entities.recordsforagents.com](https://www.zero.xyz/host/entities.recordsforagents.com/llms.txt)