Check public procurement exclusions API

Compare companies to a supplied procurement exclusion list. Only exact name or registry matches are confirmed exclusions.

The Check public procurement exclusions operation is part of the Corporate Ownership, Sanctions & Investigation API on BRAINIAC.software. Compare companies to a supplied procurement exclusion list. Only exact name or registry matches are confirmed exclusions. It is exposed as POST /api/v1/corporate-intelligence/public-procurement-exclusion-check 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 Normalize corporate registry records, Cross-check company identity, List corporate director history, Map company ownership chains. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.04 USDC
/api/v1/corporate-intelligence/public-procurement-exclusion-check

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/corporate-intelligence/public-procurement-exclusion-check" \
  -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",
      "registryNumber": "12345678"
    },
    {
      "id": "CO-2",
      "legalName": "Clean Vendor Inc",
      "registryNumber": "999"
    }
  ],
  "exclusions": [
    {
      "id": "EXC-1",
      "companyName": "Example Construction LLC",
      "registryNumber": "12345678",
      "authority": "Caller-supplied debarment excerpt",
      "reason": "debarred",
      "effectiveOn": "2025-01-01",
      "source": "Caller-supplied"
    },
    {
      "id": "EXC-2",
      "companyName": "Example Constructing Co",
      "authority": "Caller-supplied debarment excerpt",
      "reason": "suspended",
      "effectiveOn": "2025-06-01",
      "source": "Caller-supplied"
    }
  ]
}
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