Skip to main content
POST
Verify
A fact might be in the graph but stale. verify re-derives it from the current observation set and reports before vs after, so your agent knows whether to trust it before acting.

Request

Body

string
required
Entity UUID, email, domain, LinkedIn URL, or name.
string
required
The claim to re-check — e.g. "title", "stage", "email", "pipeline_stage".

Response

If no fresh evidence supports the claim, after.freshness stays suspect or expired and note tells you to record a new observation or re-enrich.

Ambiguous focus

Same shape as other endpoints:

When to call it

  • Before any high-stakes write back to a CRM (“is the stage really closed_won?”)
  • Before sending a personalised email (“is the title still VP Sales?”)
  • When a claim’s freshness is suspect or expired in the response of /v2/context or /v2/accounts/:id
If you act on every fact without verifying, you’re trusting the graph’s last-observation timestamp. For most workflows that’s fine. For ones that matter, verify first.