Claim Verification API

Business verification API.
Every claim, accounted for.

Verify submitted company identity claims against available company records. CompanyProof returns a claim-level verdict, the observed value and source evidence. It covers six identity fields; ownership, screening, payment and credit decisions require separate controls.

Verify company information Explore the API

THE CLAIM INSPECTORInteractive example Sandbox data

02 / THE SUBMITTED ANSWERGB · CP000001

CompanyProof Sandbox Limited is an incorporated in .

Select an underlined claim to inspect the evidence.

2 matching claims · 1 correction

THE COMPANY RECORD[ 02 ]

Incorporation dateCorrected

Submitted~~2021~~

On record2020

Submitted claim: 15 January 2021
Source value: 15 January 2020

The source gives a different date. Return the correction or send it for review.

COMPANY DATA EXPERTISE

Over a decade of company data expertiseOfficial registry sourcingExplore field and country coverage ↗

CHOOSE THE RIGHT CONTRACT

What this verifies—
and what it does not.

“Business verification” can mean a registry lookup, a company profile or a complete KYB workflow. CompanyProof separates them so your product does not turn an identity match into a broader risk conclusion.

01 / CLAIM VERIFICATION

You already have an assertion.

Submit one or more supported company-identity claims. Receive verified, corrected or unsupported for each claim, with the observed value and evidence.

POST /v2/claims/verifyUse this page

02 / COMPANY PROFILE

You need the underlying record.

Resolve the legal entity, then retrieve available identity, officer, ownership, group and financial modules. A returned record is not automatically a claim verdict.

GET /v2/companies/{id}/profileExplore company profiles →

03 / KYB WORKFLOW

You need an approval decision.

Combine entity verification with the ownership, screening, person, payment and risk controls required by your policy. Company registration alone does not approve a counterparty.

Policy + multiple controlsPlan supplier due diligence →

01 / BUSINESS IDENTITY VERIFICATION

Verify the facts.
Keep the detail.

Business identity verification starts with the correct legal entity. Provide a company name and country, add a registration number to distinguish similar businesses, then compare these six supported fields with the returned record.

THE COMPANY RECORDSample data

Company identity

CompanyProof
Sandbox Limited

Registered company name: CompanyProof Sandbox Limited
Registration number: CP000001
Company status: Active
Incorporation date: 15 January 2020
VAT or tax identifier: Not returned
Legal form: Private limited company

Source value identifiedincorporation_date

Compare the submitted incorporation date with this source value.

NEED THE WIDER COMPANY PICTURE?

Extend the review with company profiles.

Retrieve officers, shareholders, group structure and financial records where available. Inspect each module’s availability and preserve reporting periods, currency and source context.

Explore the company data API ↗

Directors & officersShareholdersGroup structureFinancial records

Profile records support further analysis. Automatic claim verdicts cover the six identity fields above.

02 / THE EVIDENCE

Every outcome has
a next step.

A matching name is the beginning of a check. Keep each claim’s outcome separate so your team can see what matched, what changed and what needs attention.

ILLUSTRATIVE OUTCOME02 / 04

The evidence changes the answer.

Submitted15 Jan 2021

Observed15 Jan 2020

NEXT ACTION

Use the correction or assign a reviewer.

Map each outcome to an explicit next action.

A request status, a claim verdict and your counterparty decision are different things. Preserve all three instead of collapsing them into a single “passed” flag.

Illustrative application policy—not an automatic approval rule or a compliance determination.
Returned condition	What it establishes	Your application’s next step
`verified`	The supported claim matches the observed value.	Retain the claim and evidence. Apply your other approval controls separately.
`corrected`	The observed value differs from the submitted value.	Keep both values. Apply an agreed correction policy or assign review.
`unsupported`	The available record cannot support that claim.	Request more evidence or route the gap for review; do not label the claim false.
Request error	A request was rejected or could not complete; this is not a claim verdict.	Inspect the error response and safe-retry rules before retrying.
`stale` after monitoring	A confirmed change affects a previously supported value.	Reopen that claim. An unavailable recheck preserves the last successful evidence; it does not itself establish a change.

Worked example: one company, three different claim outcomes

Fictional example, not a live lookup. An application submits status “Active”, incorporation date “2021-01-15” and a VAT identifier. The sample record supports “Active”, reports incorporation on “2020-01-15” and returns no VAT value. Keep status as verified, route the corrected date under your policy and leave the VAT claim unsupported. Two usable results do not remove the third claim’s evidence gap or approve the company.

Inspect the response and evidence fields →Understand monitoring and failed rechecks →

OPERATING MODEL

Plan the exception workload.

Verification only scales when corrected and unsupported claims have defined next steps. Model your own volumes and exception assumptions before deciding what to automate and what to review.

Set your own assumptions. The defaults—1,000 checks, three claims and two 5% exception rates—exist only to demonstrate the formula; they are not CompanyProof performance data.

Company checks / monthClaims / checkAssumed corrected %Assumed unsupported %

The corrected and unsupported percentages must total 100% or less. Stale outcomes are excluded because they arise after a monitored fact changes.

ILLUSTRATIVE MONTHLY CLAIM OUTCOMES

300 claim outcomes needing policy or review

Verified: 2,700
Corrected: 150
Unsupported: 150
Total: 3,000

1,000 checks × 3 claims = 3,000 claim outcomes. Corrected and unsupported outcomes are shown separately because they need different policies.

This models claim outcomes, not unique review cases, API credits, staffing time, approval rates or a compliance decision. Your policy may automate a correction, request evidence or assign a reviewer.

Scope an enterprise evaluation →

03 / YOUR WORKFLOW

Build verification into
the moment it matters.

Use the same company evidence across onboarding, procurement and AI applications. Your team sets the decision rules.

01 / PROCUREMENT

Check the company behind the supplier.

Compare a supplier questionnaire with the legal entity on the contract. Check its name, registration number and status before the review progresses.

Supplier due diligence

SUPPLIER REVIEW

CP / Company identitySupplier questionnaire

Legal entityMatched

Company statusActive

Incorporation dateReview

Exception ready
for a reviewer

Illustrative workflow

02 / ONBOARDING

Resolve identity before approval.

Find the right entity when an application uses a trading name or a common company name. Compare submitted facts and route discrepancies for review.

Discuss your onboarding flow

ENTITY RESOLUTION

Name + country + registration number

Candidate 01Different IDCP000001Selected entityCandidate 03Different ID

Illustrative workflow

03 / AI APPLICATIONS

Check the facts inside the answer.

Validate supported company assertions before they reach a customer or feed an operational decision. Return corrections with the source that supports them.

AI company fact checking

AI ANSWER VERIFICATION

Generated answer

Incorporated in ~~2021~~.

Evidence-backed correction

Incorporated in 2020^[1].

[1] CompanyProof Sandbox

Illustrative workflow

Company identity verification supports your decision. Payment instructions, sanctions screening and credit approval require their own controls.

04 / THE INTEGRATION

A clear request.
A result you can use.

Send individual assertions or a company answer. Receive the published value, observed value, verdict and evidence together in a structured JSON response.

POST/v2/claims/verify

curl --request POST \
  'https://companyproof.ai/v2/claims/verify' \
  --header "Authorization: Bearer $COMPANYPROOF_TEST_KEY" \
  --header 'Content-Type: application/json' \
  --header 'Idempotency-Key: sandbox-verification-001' \
  --data '{
  "company": {
    "name": "CompanyProof Sandbox Limited",
    "country": "GB",
    "registration_number": "CP000001"
  },
  "claims": [
    {
      "field": "status",
      "published": "Active"
    },
    {
      "field": "incorporation_date",
      "published": "2021-01-15"
    }
  ],
  "monitor": false
}'

const response = await fetch(
  "https://companyproof.ai/v2/claims/verify",
  {
    method: "POST",
    headers: {
      Authorization: "Bearer " + process.env.COMPANYPROOF_TEST_KEY,
      "Content-Type": "application/json",
      "Idempotency-Key": "sandbox-verification-001"
    },
    body: JSON.stringify({
      "company": {
        "name": "CompanyProof Sandbox Limited",
        "country": "GB",
        "registration_number": "CP000001"
      },
      "claims": [
        {
          "field": "status",
          "published": "Active"
        },
        {
          "field": "incorporation_date",
          "published": "2021-01-15"
        }
      ],
      "monitor": false
    })
  }
);
const proof = await response.json();
if (!response.ok) throw new Error(proof.error?.message);
console.log(proof.claims);

{
  "field": "incorporation_date",
  "published": "2021-01-15",
  "observed": "2020-01-15",
  "verdict": "corrected",
  "explanation": "The published value conflicts with the sample company record.",
  "evidence": {
    "source_name": "CompanyProof Sandbox",
    "source_url": "https://companyproof.ai/docs#environments",
    "source_updated_at": null,
    "source_record_id": "sandbox_company_001",
    "retrieved_at": "2026-09-08T09:00:00.000Z"
  }
}

Sandbox fixture · use your own test API key

RESOLVE A COMPANYPOST /v2/companies/search

Find candidates in the right country and reuse the selected company ID.

GET THE FULL RECORDGET /v2/companies/{id}/profile

Bring identity and available company modules into one profile.

CONNECT AN AI AGENT/v2/mcp

Access CompanyProof through the Model Context Protocol.

05 / FROM EVALUATION TO PRODUCTION

Test the exceptions.
Then scale the workflow.

Evaluate the countries, entity types and fields your product actually uses. Include difficult cases so your team can assess what happens when a check cannot be completed.

Prove the integration

Create an account and test key. Use the documented sandbox company to exercise a match and a correction before connecting live data.

Test and live environments ↗

Validate your coverage

Sample active and inactive companies, similar names and missing records. Measure correct matches and required-field completion.

Countries and field availability ↗

Make retries predictable

Keep API keys on your server. Use an idempotency key for retries, and handle rate limits, missing entities and unavailable sources explicitly.

Authentication and API rules ↗

Keep decisions current

Retain each proof and connect eligible live claims to monitoring. Use stale-claim events to reopen affected checks when their evidence changes.

Monitoring and webhooks ↗

YOUR COMPANIES. YOUR REQUIRED FIELDS.

Put the API to the test.

Start with a company check, or share your countries, expected volume and representative cases for an enterprise evaluation.

Verify company information Discuss your integration View plans and credit usage

FREQUENTLY ASKED QUESTIONS

Claim Verification API: your questions answered

What is a claim verification API?

It compares submitted company claims with available company records and returns a verdict, a correction where needed, and supporting evidence. Use the Company Data API when you need to retrieve a company profile.

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.

Business verification API.Every claim, accounted for.

You already have an assertion.

You need the underlying record.

You need an approval decision.

Extend the review with company profiles.

The evidence changes the answer.

Map each outcome to an explicit next action.

Check the company behind the supplier.

Resolve identity before approval.

Check the facts inside the answer.

Prove the integration

Validate your coverage

Make retries predictable

Keep decisions current

Put the API to the test.

Business verification API.
Every claim, accounted for.