AI COMPANY VERIFICATION WORKFLOW

From generated answer to monitored evidence record.

CompanyProof sits between an AI system and the point where a company fact is used. It resolves the company, verifies supported claims against official data, returns corrections and keeps eligible evidence connected for rechecks after publication.

COMPANYPROOF PIPELINEWORKFLOW OVERVIEW
AIGenerated answer
→
CPClaims + verdicts
→
✓Publish or correct
↻
Evidence remains connectedChanged or missing value → stale-claim webhook

THE VERIFICATION PIPELINE

Five steps, one controlled decision.

Your application sends natural language. CompanyProof returns structured evidence that software can act on.

STEP 01 / 05

Paste the text

Start with the company information exactly as your user or agent produced it. CompanyProof keeps the original wording beside the result.

INPUTNatural-language company answer
OUTPUTOriginal statement retained
FOLLOW THE SANDBOX EXAMPLE“CompanyProof Sandbox Limited is active and was incorporated in 2021.”

Begin with the original statement. The date is intentionally incorrect in this example.

MACHINE-READY VERDICTS

The response tells your system what to do next.

A verdict is not a confidence score. It is the result of comparing a specific published value with a specific company record and preserving the evidence behind that decision.

VERIFIEDPublish the claim
CORRECTEDRewrite with observed value
UNSUPPORTEDRemove or send to review
STALEUpdate a previously published claim
SANDBOX VERIFY RESPONSE201 CREATED
{
  "proof_id": "prf_01J62E8A",
  "company": {
    "name": "COMPANYPROOF SANDBOX LIMITED",
    "registration_number": "CP000001",
    "country": "GB"
  },
  "claims": [
    { "field": "status", "verdict": "verified" },
    { "field": "incorporation_date",
      "verdict": "corrected",
      "published": "2021-01-15",
      "observed": "2020-01-15" }
  ],
  "monitoring": "off"
}

COMPANY INTELLIGENCE INTERFACES

Use a deterministic verdict where it exists—and the profile layer where it does not.

The current claim-verification contract covers core company-identity fields. Company Profile REST and Adaptive Intelligence expose extended modules without implying that those claims are already deterministic verification fields.

CLAIM TYPEDATA MODULEEXAMPLES
Legal identityLight KYB

Name, status, legal form, registration number

Control and ownershipShareholders + hierarchy

Returned shareholder and hierarchy inputs; calculated UBO is not provided

ManagementOfficers + directors

Current appointments, roles and appointment dates

Corporate structureGroup structure

Parents, subsidiaries and ultimate parent

PerformanceFinancial statements

Revenue, EBITDA, assets, liabilities and filing periods

Current deterministic verification fields: registered name, registration number, company status, incorporation date, VAT or tax ID and legal form. Review the live contract →

TWO INTEGRATION PATTERNS

Control the answer before publication—or keep it correct afterwards.

01 · PRE-PUBLICATION

Verification gate

Call CompanyProof before a supported company-identity claim reaches a user or downstream system. Verified claims pass, contradicted claims are corrected and unsupported claims follow your review policy.

  • AI underwriting and credit decisions
  • KYB or onboarding summaries
  • Company research and intelligence agents
02 · POST-PUBLICATION

Continuous proof

Keep published facts tied to the source. When a monitored recheck changes or no longer returns the supporting value, CompanyProof identifies the affected claim and sends a signed webhook.

  • Customer and supplier monitoring
  • Published profiles and reports
  • Long-running autonomous agents

START WITH ONE WORKFLOW

Put a verification gate in front of your highest-risk supported company claim.

Start at US$99 / monthExplore the evidence ledger →

FREQUENTLY ASKED QUESTIONS

Company verification workflow FAQs

How does AI company fact verification work?

The workflow identifies the company, extracts or accepts individual claims, compares supported fields with available records and returns a verdict for each claim. Evidence is retained so the result can be reviewed later.

What company information should I provide for verification?

Provide a company name or identifier, the registration country and the text or claims to check. Accurate jurisdiction and registration details reduce the risk of selecting another entity with a similar name.

Can I paste a long company description?

The browser checker accepts up to 20,000 characters and selects material company facts. Guest questions can check up to five selected facts; paid accounts can check up to twenty. Remaining material is marked as not checked.

What happens when the company name or country is missing?

The text checker asks for the identifying details it needs. Clarification helps resolve the intended legal entity before verification; missing information should not be replaced with a guess.

Which fields does the deterministic verification API support?

The deterministic API covers registered name, registration number, company status, incorporation date, legal form and VAT or tax identifier. The browser text checker and extended company interfaces have separate capabilities.

Read the field contract
What do verified, contradicted and unsupported mean?

Verified means available evidence supports the claim. Contradicted means the evidence supports a different value. Unsupported means sufficient evidence was not returned; it does not establish that the claim is false.

Does a verified company status mean a supplier is safe to pay?

No. Company status establishes a recorded registration fact. Payment decisions also depend on the supplier relationship, invoice, bank details and your controls, which a company-status match does not verify.

How are incorrect company claims corrected?

Where a supported comparison identifies a different recorded value, the response includes the correction and its evidence. Your application can then update the answer or route the discrepancy for review.

Can CompanyProof monitor facts after verification?

Eligible verified claims can be monitored through the supported API workflow. A changed or missing supporting value can mark a claim stale and trigger a configured webhook. Saved browser text proofs are not automatically monitored.

How should I handle unsupported company claims in production?

Route them according to the importance of the decision: request more information, obtain another authorised source or require review. Keep the evidence gap visible rather than converting an unsupported result into an approval.