“This company is active.”
- Company
- Example Limited
- Verified value
- Active
- Source
- Illustrative registry
- Proof record
demo_proof_001
Original evidence preserved
Get API keyEVIDENCE MONITORING
Third-party monitoring for
verified company facts.
CompanyProof rechecks selected, previously verified company identity claims every 24 hours. If the available source no longer supports a saved value, it preserves the earlier evidence, marks that claim for review and can notify your application through a signed webhook.
This is claim-level company evidence monitoring—not employee surveillance, cyber-posture scoring or a complete third-party risk decision.
Dissolved
Review this findingThe source no longer supports the saved status. The original evidence is retained and this claim pauses for review.
03 / NEXT ACTIONReview the affected claim
claim.staleSigned webhook to configured destinationsFROM SAVED ANSWER TO REVIEW
Keep the evidence connected.
A monitoring signal should reopen the exact claim that changed—not silently rewrite a prior decision or replace the wider controls in your third-party programme.
Choose verified facts.
Open a saved evidence record and select Monitor changes. Only supported, initially verified fields with a source record are eligible.
Open saved evidence →Recheck the source.
Rechecks are scheduled every 24 hours and use your claim allowance. Registry publication and collection times vary; daily checks do not mean daily source updates.
Review source coverage →Route the exception.
Compare the original and later values in one proof history. A possible change pauses that claim for review; an unavailable lookup keeps the last evidence and retries.
Explore signed webhooks →IMPLEMENTATION RUNBOOK
From source recheck to reviewer decision.
Define each evidence state before integration. Automation can preserve and route the observation; your policy still decides who reviews it, which corroboration is required and whether the business relationship changes.
| Observed state | Evidence to retain | Safe automation | Reviewer decision |
|---|---|---|---|
| Same supported value | Claim ID, source record, observed value and check time | Append claim.reverified and schedule the next check | No exception; retain the evidence history |
| Possible source change | Prior value and proof beside the later source observation | Pause the claim and send the signed claim.stale event | Confirm the entity, source and impact; create a new proof before monitoring resumes |
| Lookup unavailable | Last successful evidence plus the failed attempt and retry time | Retry without inventing a verdict or sending a change webhook | Escalate a persistent gap under the organisation's review policy |
| Webhook delivery fails | Event ID, timestamp, destination response and retry history | Retry delivery and process the event idempotently | Investigate the endpoint; do not duplicate the downstream action |
PORTFOLIO PLANNER
Size the checks.
Plan the review queue.
Monitoring cost and operational load depend on the number of counterparties and facts you keep under watch. Use your own portfolio and assumptions; the example does not predict an observed change rate.
Illustrative planning inputs—not observed CompanyProof rates. A recheck is not a guarantee that a registry published new data during that period.
2,250 rechecks over a 30-day planning month. Each monitored claim recheck uses one claim credit.
Routine rechecks72
Review possible changes1
Retry unavailable lookups2
| Outcome | Illustrative count | Operational next step |
|---|---|---|
| Same value | 72 | Record the recheck and schedule the next one. |
| Possible change | 1 | Pause the claim and assign review. |
| Lookup unavailable | 2 | Keep the last evidence and retry. |
DEFINED SCOPE
Monitor facts.
Keep decisions with your team.
Automatic monitoring currently covers these six structured fields when verified against an available source. It does not re-run an entire due-diligence answer, scan a third party's security posture or make a business decision.
Ownership, directors and financial analysis require a new verification. A changed claim must be reviewed and verified in a new proof record before monitoring resumes.
Supported field definitions →- 01Registered name
- 02Registration number
- 03Company status
- 04Incorporation date
- 05VAT number
- 06Legal form
CHOOSE THE RIGHT MONITOR
Three different jobs.
Three different evidence sets.
A saved identity fact may have changed.
Recheck an eligible registered name, number, status, incorporation date, VAT number or legal form. Keep the prior and later values linked.
CompanyProof evidence monitoringYou need a broader change feed.
Use the separate company-event catalogue for available ownership, appointment, financial and contact-detail indicators. Confirm each event's source and delivery contract.
Explore company change events →You need a complete risk programme.
Combine company evidence with the security, sanctions, financial, operational, performance and relationship controls required by your policy.
Plan supplier due diligence →ENTERPRISE EVALUATION
Six questions before you buy monitoring.
Current search results often promise “continuous” or “real-time” visibility without showing how a signal becomes reviewable evidence. Ask for the operating detail.
- 01
What exact fields are monitored?
Require a field catalogue and test unsupported claims. A broad label such as “vendor risk” is not a data contract.
- 02
What does the cadence actually mean?
Separate recheck frequency, source publication timing and collection latency. A daily check is not a real-time source update.
- 03
How are missing values handled?
An unavailable lookup should not be called a confirmed change. Keep the last successful evidence and expose the retry state.
- 04
Can a reviewer reproduce the alert?
Retain the prior value, later observation, source record, retrieval times and claim identifier in one history.
- 05
How does delivery fail safely?
Verify webhook signatures, process deliveries idempotently and define ownership for paused claims and retries.
- 06
What volume reaches the allowance?
Include every monitored claim recheck alongside new verifications. Model the steady-state portfolio before selecting a plan.
START WITH THE PROOF YOU ALREADY HAVE
Choose what stays under watch.
Monitoring requires an eligible paid plan. You can turn off scheduled checks without deleting your evidence. For a larger portfolio, bring the countries, fields and expected recheck volume to an enterprise review.