Skip to main content
An Agentic ID is one identifier that stands for one person or one company. Start from a work email, a profile URL, a name with a company, or a company domain: the same entity gets the same ID each time. Use the ID as the key for everything else. Enrich, find, facts, the ledger and feedback all take it.

Format

The ID is random. It is never derived from an email, a name or any other data, so it reveals nothing about who it stands for. Treat it as an opaque string.

Person or company

Every ID has a kind: person or company. When you resolve, the kind is inferred: a request with email, linkedin_url or name is a person, anything else is a company. Set kind to decide it yourself. The resolve answer says what an ID stands for in subject: its kind and, for a company, the domain it was resolved from. A person is never described there.

What resolves to an ID

Send any of these in identifiers on Resolve: Send every identifier you have in one request. They are checked together.

What you get back

outcome tells you what happened: Two fields say how the match was made:
string
Which identifier matched, for example work_email or domain.
number
How sure Agentic ID is that the identifier points at this ID, from 0 to 1. It is not a measure of how verified the ID’s facts are. For that, see Verification levels.
Agentic ID does not guess. Weak or ambiguous input comes back as review, conflict or unresolvable, never as a confident ID. A company answer may carry related: other company IDs that may belong with this one, such as a regional site or a brand. Related companies are linked for review. They are never merged automatically.

Stability

  • An ID is stable for life. Changing a job title, an email or a domain does not change the ID.
  • A merge keeps the old ID working. When two IDs turn out to be the same entity, one survives and the other forwards to it. Requests with the old ID still work.
  • Every change is recorded. Creation, links, merges and splits each add an entry to the ID’s ledger.

IDs your workspace holds

Your workspace holds an ID once it has resolved it or been delivered it. ids_held on GET /v1/workspace is the count. Holding an ID matters in three places:
  • Facts and the ledger are shown only for IDs your workspace holds. Any other ID returns 404 id.not_held.
  • Feedback is accepted only for IDs your workspace holds.
  • Resolving an ID your workspace already holds is not charged while your workspace contributes. See Credits.