> ## Documentation Index
> Fetch the complete documentation index at: https://celoref.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# About PIXA

> PIXA is the wallet and payment layer for AI agents, designed around Algorand funding, multichain routing, and human-controlled sessions.

# About PIXA

PIXA is a wallet and payment system for AI agents.

It solves a practical problem: agents can reason and act, but they still need a safe way to pay for APIs, services, swaps, and real-world checkout flows.

PIXA keeps the user in control while giving the agent enough authority to work:

* one Algorand-funded home wallet
* a hub that can route value to other chains
* hosted browser flows for approvals and on-ramp actions
* future session controls for spend limits, time windows, and revocation
* a path toward AC2-style human-in-the-loop authorization

## Why this exists

The current payment stack for agents is fragmented.

Users usually need to manage:

* multiple wallets
* multiple chains
* API keys
* manual approvals for anything sensitive
* one-off onboarding flows for each service

PIXA replaces that with one control plane:

1. fund the agent wallet on Algorand
2. let the agent discover or choose the service
3. route the payment through PIXA Hub or a hosted flow
4. keep the user informed and able to approve when needed

## Why decentralize at all

PIXA does not treat decentralization as a slogan. It treats it as a control problem.

The goal is not to hide the backend.
The goal is to reduce what the backend can do on its own.

That means:

* user-owned funds stay in a wallet the user can understand
* approvals can be moved into a browser or wallet flow
* session authority can be temporary and revocable
* the long-term architecture can shift from operator-backed execution toward more explicit on-chain policy

## Where AC2 fits

AC2 is the direction for higher-trust actions.

In PIXA, AC2 can become the layer that handles:

* identity between user and agent
* signing approvals
* session creation and revocation
* delegated authority for time-bound or spend-bound actions

That means PIXA can start simple today and still evolve toward stricter user control later.

## Built today

* Algorand wallet-based agent payments
* x402 payment support
* multichain routing through the PIXA Hub model
* on-ramp and off-ramp browser flows
* rekey-based session experiments
* published npm package for developers

## What comes next

* stronger session policy
* more explicit multichain settlement paths
* better auditability and proof-of-reserve style checks
* AC2-based approval flows for sensitive actions