Skip to main content
Available now. The provisioning and communication tooling — domains, inboxes, numbers, connections, and the vault API — is live, gated by the policy layer. The inbound wake (a stored inbound message starting a session) is coming soon.
An identity is a named, described persona an agent acts as in the world. It is the difference between an anonymous script and a real participant that can hold an inbox, answer a text, authorize a third-party app, and use a secret it can never read. An identity bundles what a persona needs to act in the world:

Web domains

The verified domains an identity sends and receives on — auto-provisioned, brought-your-own, or purchased through Vetta.

Email

Real inboxes on a verified domain. Send and receive as a specific address.

Phone

Provisioned numbers with carrier-registered (A2P) messaging. Send and receive SMS.

Connections

Third-party apps the identity has authorized over OAuth (“Passport”).

Credential vault

A write-only secret store. Values are injected at the network boundary — the agent never sees them.

Agent wallet

Coming soon · Phase 5. A spend-limited wallet so the persona can pay for things in the world, gated by policy.

Identities are concrete, and many-to-many

An identity has a name and a description so the agent knows who it is being. Crucially, its communication endpoints are specific addresses and numbers, not booleans:
  • billing@acme.com is a different identity from support@acme.com.
  • +1 415 555 0142 belongs to one identity, not “the org”.
The relationship between agents and identities is many-to-many:
  • One agent can hold multiple identities — e.g. an inbound support persona and an outbound sales persona — and choose which to act as per task.
  • One identity can be shared by multiple agents — e.g. a billing@acme.com persona handled by a triage agent and a refunds agent.
See Personas for the identity object itself and how it attaches to agents.

Create an identity

Attach it to an agent

An agent references identities and picks one to act as. Manage the product at the agent level and the actor at the session level.
The harness: "pi" field selects the harness — the agent loop; the completion window (immediate · priority · loose) is the only latency knob. Neither affects which identity an agent acts as — that is chosen per session.

How the pieces fit

Everything an identity can do is enforced at the tool-call boundary by policies, which resolve before any external request is made.

Next: personas

The identity object — its fields, the endpoints it owns, and attaching it to agents.