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

# Data and privacy

> What the API does with the data you send: purpose, masking, workspace scoping and the ledger.

This page describes what the API does. It is not legal advice.

## Purpose

Every data call carries a `purpose`: why you are asking.

Values: `b2b_outbound`, `ad_audience`, `own_customer_enrichment`, `fraud_check`. When you omit `purpose`, it is `b2b_outbound`.

Each workspace has a list of allowed purposes. `GET /v1/workspace` returns it as `allowed_purposes`. A call with a purpose that is not on the list is refused with `403 purpose.not_allowed`. The error carries the `purpose` you sent and the `allowed` list.

## Work identifiers

Agentic ID works on work identities and companies: work emails, LinkedIn profile URLs, a name with a company, and company domains.

* Validate refuses malformed, disposable and personal addresses before any check. They come back with the verdict `rejected` and are not charged.
* The [MCP server](https://docs-agentic-id.icustomer.ai/mcp-server.md) and the [CLI](https://docs-agentic-id.icustomer.ai/cli.md) hold back personal email addresses and phone numbers on your machine. They are not sent.

## Masked contact values

Contact values are returned masked by the API today.

| Value | Example |
| - | - |
| Email | `a******@acme.example` |
| Phone | Only the last four digits are shown |
| LinkedIn profile URL | Only the start of the profile name is shown |

Names, titles and company data are not masked.

## Workspace scoping

Every credential belongs to one workspace. An API key acts as its workspace. A signed-in account acts as its own workspace.

| What | Scope |
| - | - |
| Facts and ledger (`GET /v1/facts/{id}`, `GET /v1/ledger/{id}`) | Only for IDs your workspace holds. Any other ID returns `404 id.not_held`. |
| Feedback (`POST /v1/feedback`) | Only for IDs your workspace holds. It changes what your workspace is served and how much the value's source is trusted. It is not shown to another workspace. |
| Credits and recent charges | Your workspace only. People in `recent_ids` are listed by ID. A company's name or domain is shown. |
| Idempotency keys | Your workspace only |

### Contributing

`GET /v1/workspace` returns `contributes`.

| Value | Meaning |
| - | - |
| `true` | Identifiers your workspace sends help every workspace resolve the same entity |
| `false` | They stay private to your workspace |

## What the ledger records

Each Agentic ID has a ledger: an ordered list of entries about what happened to the ID, such as when it was created, linked, merged or split.

| Field | Meaning |
| - | - |
| `seq` | Position in the ID's ledger |
| `kind` | What happened |
| `at` | When |
| `hash`, `prev_hash` | Each entry is linked to the one before by its hash |
| `detail` | The details of the entry |

`GET /v1/ledger/{id}` re-checks the chain on every read and returns `verified`. See [The ledger](https://docs-agentic-id.icustomer.ai/concepts/ledger.md).

## What a request leaves behind

* Every response carries a `request_id`, also sent as the `X-Request-Id` header.
* `GET /v1/credits` lists the latest grants and charges and the IDs delivered to your workspace.
* API keys are shown once when created. See [API keys](https://docs-agentic-id.icustomer.ai/api-keys.md).

## Erasure and access requests

The public API and the CLI have no endpoint or command for erasure, access or opt-out requests today.

## On your machine

The [Claude Code plugin](https://docs-agentic-id.icustomer.ai/claude-code-plugin.md) keeps a usage log at `~/.agentic-id/usage.jsonl`. It holds the time, session ID, tool, outcome, error code, request ID and credits. It does not hold tool inputs or results. You can delete it at any time.


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