Normalize corporate registry records API

Normalize supplied company registry fields and legal-name tokens. Missing identifiers stay blank rather than invented.

The Normalize corporate registry records operation is part of the Corporate Ownership, Sanctions & Investigation API on BRAINIAC.software. Normalize supplied company registry fields and legal-name tokens. Missing identifiers stay blank rather than invented. It is exposed as POST /api/v1/corporate-intelligence/registry-record-normalize and priced at $0.04 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Caller-supplied registry, ownership, sanctions, and enforcement records OFAC SDN (no API key) when fetchOfac is requested Limitations: No paid corporate-data provider is used and no API key is required. Uncertain name matches are labeled possible only and are never treated as confirmed sanctions or enforcement matches. Confirmed flags require an exact normalized-name or registry-number match. Ownership chains use only supplied edges. Missing percentages are not invented. OFAC SDN is used only when fetchOfac is requested. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Cross-check company identity, List corporate director history, Map company ownership chains, Resolve corporate name variants. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.04 USDC
/api/v1/corporate-intelligence/registry-record-normalize

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/corporate-intelligence/registry-record-normalize" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "companies": [
    {
      "id": "CO-1",
      "legalName": "Example Construction LLC",
      "tradingName": "Example Construction",
      "registry": "OpenCorporates excerpt",
      "registryNumber": "12345678",
      "country": "US",
      "status": "active",
      "source": "Caller-supplied registry excerpt",
      "sourceUrl": "https://example.invalid/registry/12345678"
    },
    {
      "id": "CO-2",
      "legalName": "Other Holdings Limited",
      "registry": "Caller-supplied Companies House excerpt",
      "registryNumber": "87654321",
      "country": "GB",
      "status": "active",
      "source": "Caller-supplied registry excerpt"
    }
  ]
}
JSON

An unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.

FAQ

  • Do I need an API key? No. Pay the listed USDC amount with x402.
  • What network? Base (eip155:8453), USDC.
  • Is this an official determination? No. Results are for human review against the cited sources.

Related APIs

Corporate Ownership, Sanctions & Investigation APIFull docsHow it works