Identity profile

Each agent has an identity profile: the consistent details it presents when a service asks who is signing up.

What it holds

The public-facing details a signup form needs — the kind of information you would type into a registration page. The agent can read its own profile, so the details it gives one service match the details it gives the next.

Why consistency matters

A profile that changes between signups looks like fraud to the services receiving it, and it makes accounts hard for you to reconcile later. One stable profile per agent avoids both problems.

What it is not

It is not your personal identity. It is not a legal identity, and it does not assert anything about a real person. It is the coherent set of details this agent uses.

Reading it

The agent reads its profile through MCP alongside its accounts. You see the same details in the agent's view in the dashboard.

Changing it

Treat changes as significant. Accounts already created on third-party services keep whatever details were used at signup — changing a profile afterwards does not reach back and update them, and a mismatch between the profile and an existing account can be worse than a stale profile.