DOCUMENTATION / OVERVIEW

Company Data API Documentation

Company data API documentation with exact response attributes, authentication, company search, financial data, ownership, verification and MCP integration guides.

BASE URLhttps://companyproof.ai/v2JSON · Bearer authentication

COMPANY INTELLIGENCE · DEVELOPER GUIDE

Start with the response your product needs.

Find a company, retrieve its profile, verify a claim or connect an AI agent. Use the guide below to choose your starting point, then inspect the exact attribute names and response types.

01 / BUILD AN INTEGRATIONRetrieve a company profile

Search an entity, validate the match and fetch its records.

Open quickstart →02 / EXPLORE THE DATAFind an exact attribute

Browse field paths, types, allowed values and response shapes.

Open attribute explorer →03 / GO DEEPERFinancials & ownership

Inspect reporting periods, metrics, shareholdings and corporate groups.

Explore financial data →04 / TRACK CHANGESMonitoring & webhooks

Understand monitored claims, change events and signed deliveries.

Open monitoring guide →

Run a sandbox verification →Ownership reference →Company change events →MCP & AI agents →

Two clearly labelled references

CompanyProof schemas document the endpoints you can call with your CompanyProof key. The extended financial, ownership and watch catalogues identify upstream-provider direct-API attributes and their separate access requirements.

Using the browser text checker?

Paste up to 20,000 characters on the homepage or dashboard to extract and check company claims. Guests can check up to 5 selected facts per question; paid accounts up to 20. Each result shows its sources and available source dates. This browser workflow is separate from the six-field deterministic REST/MCP contract. Saved text proofs are not automatically monitored.

Ready to integrate?

Create a key, download the OpenAPI 3.1 contract and start with the CompanyProof sandbox fixture. Issue a live key only when you are ready to retrieve eligible company records.

Create an API key

Developer frequently asked questions

FREQUENTLY ASKED QUESTIONS

Company verification API FAQs

What is the base URL for the CompanyProof REST API?

The documented REST API uses https://companyproof.ai/v2. Start with the OpenAPI contract for endpoint paths, request fields and response schemas instead of inferring the interface from marketing examples.

Open the API specification

How do I authenticate CompanyProof API requests?

Send your CompanyProof key in the Authorization header using the Bearer scheme. Keep keys on the server, protect them from logs and public repositories, and revoke any key that is exposed.

What is the difference between a test key and a live key?

Test keys use the documented sandbox fixture and a separate test allowance. Live keys access eligible company verification services only when the account has the required paid entitlement; advanced operations reject test keys.

How do I find a company before requesting its profile?

Call POST /v2/companies/search with the identifier and jurisdiction, validate the returned match, then use its company ID in GET /v2/companies/{id}/profile. Check optional module availability before using enrichment fields.

Which claims can POST /v2/claims/verify check?

Its deterministic contract supports registered name, registration number, status, incorporation date, legal form and VAT or tax identifier. Broader browser text extraction and extended profile modules do not expand that contract automatically.

How do I check remaining CompanyProof API credits?

Call GET /v2/usage to read the plan, billing state and remaining allowance. It consumes a request in the rate window but does not consume a claim credit.

How can I retry a verification without duplicate credit use?

Use an idempotency key with the same request. An accepted replay returns the saved proof without another claim charge; reusing the key for materially different input returns an idempotency conflict.

What do HTTP 402 and HTTP 429 mean?

HTTP 402 indicates a billing entitlement problem. HTTP 429 indicates a rate or quota limit. Inspect error.code and any Retry-After or usage headers; reconnecting authentication will not resolve a billing suspension.

How are CompanyProof API calls metered?

Each accepted verification claim and monitored claim recheck consumes one credit. An accepted company search, profile retrieval or adaptive-intelligence request also consumes one credit. Requests stop at the plan allowance.

What evidence should my application preserve from a response?

Keep the company identifier, claim, verdict, observed value, proof identifier and available source metadata. Preserve missing-data states and distinguish retrieval time from the source’s update date.

Review evidence records