Use Cases
PIXA is useful anywhere an AI agent needs to pay, route, or request approval without holding raw keys.Agentic API access
An agent discovers an x402-gated API and pays for access from the PIXA wallet. This is the most direct use case:- research APIs
- data APIs
- LLM or inference APIs
- paid tool endpoints
Cross-chain service payments
The user funds Algorand, but the target service may sit on another chain. PIXA Hub handles the difference between the home wallet and the destination rail.Real-world checkout
On-ramp and later card or merchant flows let the same control surface pay for real services. That means the agent can move from API commerce into broader digital commerce.Team-managed agent budgets
A company may want several agents, each with limits. PIXA can support:- one budget per agent
- per-call spending caps
- daily caps
- session revocation
Human-approved sensitive actions
Some actions should still ask the user. Examples:- large transfers
- new merchant approval
- new chain activation
- session extension
- key or rekey changes
Future AC2 flows
When AC2 lands fully, those approval moments become more structured:- identity is explicit
- approval is signed
- delegation is time-bound
- the user can revoke authority later