# BrazilMCP

> Brazilian company data for AI agents: official registry, lawsuits signal,
> government contracts and sanctions. Pay per call in USDC via the x402
> protocol (HTTP 402 flow) — no signup, no API key.

## Tools

- `company_lookup` — `GET https://api.brazilmcp.dev/v1/company_lookup?query=<CNPJ or name>` — US$ 0.005/call: Brazilian company registry lookup by CNPJ or company name — official Receita Federal (RFB) data for KYB and business verification in Brazil: registration status, legal and trade name, CNAE activities, address, partners (QSA), tax regime
- `company_sanctions` — `GET https://api.brazilmcp.dev/v1/company_sanctions?query=<CNPJ or name>` — US$ 0.02/call: Sanctions and debarment screening of a Brazilian company by CNPJ across 5 federal lists: CEIS (debarred companies), CNEP (anti-corruption penalties), CEPIM (barred non-profits), leniency agreements (Acordos de Leniência) and the forced-labor employers register (Lista Suja/MTE) — entries with validity dates and an is_currently_sanctioned verdict. The Brazilian complement to OFAC/EU/UN global screening, for KYB and compliance
- `company_dossier` — `GET https://api.brazilmcp.dev/v1/company_dossier?query=<CNPJ or name>` — US$ 0.25/call: Aggregated due-diligence (KYB) dossier on a Brazilian company by CNPJ: official registry, litigation signal from court communications (name-match), government contracts and procurement history (PNCP), sanctions screening across 5 federal lists (CEIS/CNEP/CEPIM/leniency/forced-labor) and derived compliance risk flags; every section declares source and coverage

MCP server (streamable HTTP): https://api.brazilmcp.dev/mcp — same tools and prices; attach
the signed x402 payment to the `x402/payment` key of the request `_meta`.

## Payment (x402 — v2 and v1 clients supported)

1. Request without payment returns HTTP 402. v2 clients: requirements in
   the `PAYMENT-REQUIRED` response header (base64). v1 clients: same
   requirements as a JSON `accepts` envelope in the body.
2. Sign the EIP-3009 authorization (USDC on Base) with any x402 client and
   retry — v2: `PAYMENT-SIGNATURE` header; v1: `X-PAYMENT` header.
3. Settlement receipt comes in `PAYMENT-RESPONSE` (v2) and
   `X-PAYMENT-RESPONSE` (v1). Same signed authorization retried = same
   response, no double charge. Internal failures are never charged;
   `not_found` for a nonexistent CNPJ is a valid, charged answer.

## Response contract

Versioned JSON (`schema_version`, semver; additive changes in minor).
Schemas: https://api.brazilmcp.dev/schemas/company_lookup.schema.json,
https://api.brazilmcp.dev/schemas/company_sanctions.schema.json and
https://api.brazilmcp.dev/schemas/company_dossier.schema.json
OpenAPI 3.1: https://api.brazilmcp.dev/openapi.json

## Honesty notes

- Lawsuits are matched by party name over DJEN/CNJ judicial communications
  (`match_method: party_name`, `coverage: partial`, disclaimer in payload).
- Contracts (PNCP) are verified supplier matches; aggregates cover the
  verified set and declare their window.
- Sanctions screening covers 5 federal lists (CEIS, CNEP, CEPIM, leniency
  agreements, forced-labor register); lists that could not be checked are
  declared in `lists_unavailable`.
- Companies only; no personal data beyond partner names as registered.