> ## Documentation Index
> Fetch the complete documentation index at: https://docs-agentic-id.icustomer.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Agentic ID

> One stable identifier for a person or a company, whichever identifier you start from.

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

```text theme={null}
ic-4kQ9xT2mB7nLp0Zr8VwYc3
```

| Part | Value |
| - | - |
| Prefix | `ic-` |
| Body | 22 characters, letters and digits (`0-9`, `A-Z`, `a-z`) |
| Case | Case-sensitive. Store it exactly as returned |

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`.

| Kind | Stands for | Created from |
| - | - | - |
| `person` | One person in their working life | A work email, a profile URL, or a name with a company |
| `company` | One company | A live company domain |

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](https://docs-agentic-id.icustomer.ai/products/resolve.md):

| Field | Resolves | Notes |
| - | - | - |
| `email` | A person | A work email |
| `linkedin_url` | A person | A profile URL |
| `name` | A person | Needs `company_name` or `company_domain` with it. A name alone is not enough |
| `company_domain` | A company | The domain must be live for a new company ID to be created |
| `company_name` | | A hint that goes with `name` or `company_domain`. It does not resolve by itself |

Send every identifier you have in one request. They are checked together.

## What you get back

`outcome` tells you what happened:

| `outcome` | Meaning | `id` |
| - | - | - |
| `known` | Agentic ID already had an ID for this | Returned |
| `new` | An ID was created | Returned |
| `review` | A possible match, not sure enough to link. Nothing was linked | Not returned |
| `conflict` | The identifiers point at more than one ID. Held for review, nothing merged | Not returned |
| `unresolvable` | Not enough to go on. `reason` says what was missing | Not returned |

Two fields say how the match was made:

**matched\_on** `string`

Which identifier matched, for example `work_email` or `domain`.

**confidence** `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](https://docs-agentic-id.icustomer.ai/concepts/verification.md).

Agentic ID does not guess. Weak or ambiguous input comes back as `review`, `conflict` or `unresolvable`, never as a confident ID.

### Related companies

A company answer may carry `related`: other company IDs that may belong with this one, such as a regional site or a brand.

| `reason` | Meaning |
| - | - |
| `same_name_other_domain` | A known company has the same name on another domain |
| `redirects_to` | The domain redirects to a company Agentic ID knows |

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](https://docs-agentic-id.icustomer.ai/concepts/ledger.md).

## 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](https://docs-agentic-id.icustomer.ai/concepts/verification.md) and the [ledger](https://docs-agentic-id.icustomer.ai/concepts/ledger.md) are shown only for IDs your workspace holds. Any other ID returns `404 id.not_held`.
* [Feedback](https://docs-agentic-id.icustomer.ai/products/feedback.md) is accepted only for IDs your workspace holds.
* Resolving an ID your workspace already holds is not charged while your workspace contributes. See [Credits](https://docs-agentic-id.icustomer.ai/credits.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.