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.
Web domains
The verified domains an identity sends and receives on — auto-provisioned, brought-your-own, or purchased through Vetta.
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 aname and a description so the agent knows who it is being. Crucially, its communication endpoints are specific addresses and numbers, not booleans:
billing@acme.comis a different identity fromsupport@acme.com.+1 415 555 0142belongs to one identity, not “the org”.
- 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.compersona handled by a triage agent and a refunds agent.
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
Next: personas
The identity object — its fields, the endpoints it owns, and attaching it to agents.