Brazil
RunOnProof's Brazil portfolio is production-certified at runtime release b6a5b32add4e0a867bc5f404700eed859af2051b. It contains nine technical products, five composed solutions, and one Company Capability Passport. Together, the 15 canonical offers cost 1.68 USDC when purchased individually.
The currently certified API origin is https://cdo-production.up.railway.app. The custom API hostname becomes canonical only after its DNS verification is complete.
Typical starting point
A Brazilian workflow normally begins by resolving the legal entity from a strong identifier, such as a CNPJ, or from enough identifying information to avoid a name-only guess. The next check reads the supported registration or status evidence. Deeper workflows can then apply supplier, invoice, payee, change, or payment rules when their required evidence is available.
What a basic company result can support
A scoped result may support facts such as the resolved legal name, registration identity, jurisdiction, and supported current-status observations. It does not automatically prove financial strength, beneficial ownership, invoice authenticity, bank-account ownership, absence from every restriction source, or suitability for every business policy.
Canonical portfolio
| Offer | Route | Price |
|---|---|---|
| Legal Entity Resolution | POST /v1/br/entities/resolve | 0.01 USDC |
| Company Legal Status | POST /v1/br/companies/legal-status | 0.03 USDC |
| Invoice-to-Company Match | POST /v1/br/invoices/match-company | 0.05 USDC |
| Business Payee Match | POST /v1/br/payees/match-business | 0.05 USDC |
| Supplier Approval | POST /v1/br/suppliers/approve | 0.20 USDC |
| Payment-Detail Change Authorization | POST /v1/br/vendors/authorize-payment-detail-change | 0.15 USDC |
| Business Payment Authorization | POST /v1/br/payments/authorize | 0.15 USDC |
| Restricted Business Party Screen | POST /v1/br/restricted-parties/screen | 0.01 USDC |
| Continue Vendor Authorization | POST /v1/br/vendors/authorizations/continue | 0.15 USDC |
| Company Check solution | POST /v1/br/solutions/company-check | 0.04 USDC |
| Supplier Approval solution | POST /v1/br/solutions/supplier-approval | 0.20 USDC |
| Invoice & Payee Verification solution | POST /v1/br/solutions/invoice-payee-verification | 0.09 USDC |
| Payment Authorization solution | POST /v1/br/solutions/payment-authorization | 0.25 USDC |
| Vendor Change & Continuous Authorization solution | POST /v1/br/solutions/vendor-change-continuous-authorization | 0.20 USDC |
| Company Capability Passport | POST /v1/br/company-passports | 0.10 USDC |
The runtime catalog and OpenAPI contract are the machine-readable sources of truth. Catalog presence is not payment authorization.
Request a quote without paying
Omit Payment-Signature. The certified route returns HTTP 402 with a bound quote; that response is a commercial boundary, not permission to pay.
curl -i -sS -X POST https://cdo-production.up.railway.app/v1/br/solutions/company-check -H 'Content-Type: application/json' -H 'Idempotency-Key: docs-br-company-check-0001' -H 'X-CDO-Request-Body-Digest: sha256:575bf9f1a9e1bac5107721496949b05eed72734a5df84a10b2eeeb53a1986192' --data '{"cnpj":"33000167000101","idempotency_key":"docs-br-company-check-0001"}'
No-decision paths do not charge. Exact replay of a settled execution does not create a second charge.
MCP boundary
Public MCP execution is not enabled. The canonical /mcp surface remains metadata-only until an explicitly approved, allowlisted, rate-limited, payload-limited, timeout-bounded, credential-free production design is activated.
Evidence rules
- Prefer unique identifiers over names.
- Preserve accents, legal suffixes, and source identifiers in the evidence record.
- Distinguish headquarters, branches, and other registrations when the source does.
- Record observation time and source health.
- Keep tax, legal-status, restriction, invoice, and payee claims separate.
- Never expand a state-level or source-specific fact into nationwide proof without declared coverage.
Example: adding a supplier
An agent receives a trading name, CNPJ, address, and invoice. RunOnProof first resolves the CNPJ to the legal entity. It then checks the supported legal-status facts and any additional evidence required by the buyer's onboarding policy. If the invoice name differs only because of a recognized trading name, that relationship must still be supported rather than assumed. If required payee evidence is missing, the supplier check may pass one stage while the payment stage remains REVIEW.
Limitations to keep visible
Brazil has many public and private data sources with different purposes, terms, quotas, and geographic reach. Availability in one source does not grant permission to scrape another or combine claims beyond their legal and technical scope. RunOnProof should use legitimate access paths and fail closed when a required source cannot support the promised result.
Operational checklist
Confirm the CNPJ or resolution strength, intended action, named policy, active product state, required sources, freshness, price, and downstream handling of REVIEW before using a Brazilian decision in production.