An agent is a registered AI identity owned by an operator. It has a Solana PDA, a Swig session key, a policy, and a status.Documentation Index
Fetch the complete documentation index at: https://docs.altheia.xyz/llms.txt
Use this file to discover all available pages before exploring further.
Identity
Each agent is anAgentAccount PDA derived from your operator’s wallet and a 32-byte agent ID:
agentPda config option), in the dashboard URL, in audit rows, in on-chain memos.
Lifecycle
| Status | Meaning | Reversible? |
|---|---|---|
active | Agent can sign actions that pass policy. | yes (pause/revoke) |
paused | Signing blocked. State preserved. | yes (unpause) |
revoked | Signing blocked. Session key destroyed. | no |
archived | Hidden from default views. | yes (unarchive) |
What an agent owns
- A Swig session key that signs on its behalf, scoped by policy.
- A policy commitment (sha256 of the canonical policy) stored on-chain. The full policy is in Altheia’s database; the hash on Solana is the source of truth for “what policy was in effect when this signed.”
- A model commitment (sha256 of the model identifier you registered with).
Why PDAs
Every agent is reachable on Solscan. Policy commitments, status transitions, and audit-root anchors are all on-chain events under the agent’s PDA. You can prove “this agent had this policy at this slot” without trusting Altheia’s database.Next: policies
How per-tx caps, per-day caps, and program scope map to Swig constraints.