> For the complete documentation index, see [llms.txt](https://docs.aspanfi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aspanfi.com/welcome/why-aspan.md).

# Why Aspan

Teams operating agents need to manage two related jobs: paying for services and deciding what to do with funds between payments. Separate wallets, provider balances, and yield positions can make that work difficult to coordinate.

ASPAN is being designed to bring these decisions into one programmable account. The owner sets the rules; agents operate within them.

### Who the account is for

The first customer hypothesis is a team that already holds stablecoins, runs multiple agents, and has recurring compute, data, or API costs. The account is intended to give the team one view of agent budgets, payment commitments, liquid reserves, and investment positions.

Design-partner work still needs to establish which teams face this problem frequently and will pay to solve it.

### Coordinate spending and investment

* **Control spending:** assign budgets, permitted recipients, per-payment limits, and approval requirements.
* **Make liquidity explicit:** distinguish funds available now from committed funds and investments that need time to exit.
* **Manage eligible balances:** compare approved strategies against the owner's risk limits and expected use of the money.
* **Explain actions:** show why a payment, allocation, adjustment, or withdrawal occurred and what it cost.

For example, a higher displayed APY may not justify moving funds if the next payment is close or switching costs consume the expected gain. ASPAN's proposed AI management should evaluate those tradeoffs together.

### Yield is a choice within the account

The account is intended to work with supported stablecoins before a user selects an investment. Native ASPAN DeFi and planned ASPAN Vaults are parallel options, with different underlying risks and withdrawal conditions. A user can authorize payments without authorizing either strategy.

ASPAN's own strategy must meet the same allocation criteria as an external strategy. The product does not assume that an agent operator should take BNB-linked protocol exposure to access payment tools.

### What success should look like

The combination of payments and yield management is a product hypothesis, not a claim of a unique feature set. Pilots should measure successful payments, timely availability of funds, manual interventions, total costs, net investment results, and repeat use.

AI decisions should be compared with a simple baseline, such as fixed liquid reserves and periodic rebalancing, under the same asset universe and risk constraints. Better outcomes remain to be demonstrated.

Start with [ASPAN Account](https://docs.aspanfi.com/agent-payments/operating-balance), or check [Product Status & Roadmap](https://docs.aspanfi.com/agent-payments/product-status-and-roadmap) before interpreting a prototype as an available service.
