COMPANYPROOF · BUSINESS VERIFICATION API
Business verification API. Evidence for every company claim.
Connect business identity verification to the company facts your application uses. CompanyProof checks supported claims against company records, returns corrections and preserves the evidence for your onboarding, procurement or AI workflow.
What a business verification API should establish
Start with the exact legal entity. A trading name, a website and a registered company name can refer to different businesses. Use the registration number and jurisdiction where possible; if the match is ambiguous, confirm the company before evaluating its claims.
CompanyProof separates identity resolution from claim verification. A successful company lookup establishes which record was found. A verified claim establishes that a particular value matched the available evidence at the time of the check. Keeping these results separate helps your team investigate exceptions.
One integration, two useful contracts
Use Company Profile REST when you need a structured company record. Use claim verification when you already have an answer or a set of supported company-identity assertions to check. The website also accepts pasted text and asks for missing company details.
The deterministic verification contract currently covers registered name, registration number, company status, incorporation date, VAT or tax ID and legal form. Extended company-profile modules can return officers, shareholders, group structure and financial information where available. Returning those records does not by itself produce a verified ownership or financial claim.
- Search: GET /v2/companies/search
- Profile: GET /v2/companies/{id}/profile
- Claim verification: POST /v2/claims/verify
- Agent access: /v2/mcp
Evaluate the API using your exceptions
Build a representative sample of active and inactive entities, duplicate names and jurisdictions your customers actually use. Measure correct entity matches, evidence availability and cases requiring review. Count a missing source separately from a contradicted claim.
Agree your decision policy before automating approvals. Company registration alone does not establish payment safety, creditworthiness, sanctions status or that the person contacting you controls the company. Keep any additional controls your workflow requires, then use the evidence ledger to retain the company facts behind the decision.
Checks and evidence
| Input or result | What to preserve | How your team uses it |
|---|---|---|
| Company identity | Jurisdiction and registration number | Confirm the correct legal entity |
| Claim verdict | Claimed value and observed value | Accept, correct or review the assertion |
| Evidence | Source details and retrieval time | Explain what supported the result |
| Monitoring | Previous value, new value and event | Reopen decisions when eligible facts change |
Validate your use case.
Review the available countries and fields, inspect the evidence ledger and compare current plans and credit usage. For an enterprise evaluation, send your countries, required fields and representative cases.
Discuss your workflowFREQUENTLY ASKED QUESTIONS
Business verification API: your questions answered
What is a business verification API?
It lets software retrieve and compare business identity information using company records. CompanyProof also checks supported assertions and retains claim-level evidence.
Is company verification the same as KYB?
Company verification is one part of a Know Your Business process. A complete KYB workflow may also require ownership review, screening, identity checks and ongoing risk assessment.
Which company fields can the API verify?
The deterministic contract supports registered name, registration number, status, incorporation date, VAT or tax ID and legal form. See the documentation for the current schema.
Can I search by company name?
Yes. Add the country and, where relevant, a state or province. A registration number helps distinguish companies with similar names.
Does a registered company mean it is safe to pay?
No. Registration establishes an entity record. Confirm the beneficiary, payment instructions and any other risk controls before authorising a payment.
Can I verify an AI-generated company answer?
Yes. Use the text checker or the documented verification contract. The result distinguishes supported assertions, contradictions and information that remains unverified.
Does every country return the same information?
No. Availability varies by registry, field and access. Test the countries and modules your workflow needs before selecting a plan.
Can the API return ownership and financial records?
Company Profile REST can return extended modules where available. These records are separate from the deterministic company-identity verification fields.
Can I monitor a verified claim?
Eligible live claims can be connected to monitoring. A changed or no-longer-returned supporting value can trigger a stale-claim event.
How do developers start?
Review the API documentation, create an account and API key, test the documented sandbox fixture, then validate live coverage and credit usage for your workflow.