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

# Agentic Limits & Support Matrix

> What agentic payments supports, and every cap you can hit

## Networks & assets

Agentic payments move money through the same rails as the rest of the platform — anything your [wallets](/documentation/wallets) can send, an agent-drafted payment can send:

| Route                                                       | How                              | Notes                                                                                              |
| ----------------------------------------------------------- | -------------------------------- | -------------------------------------------------------------------------------------------------- |
| Same-family crypto (EVM → EVM, Solana → Solana)             | direct                           | the agent always prefers a direct route when a same-family funding wallet exists                   |
| Cross-family crypto (e.g. EVM funding → Solana destination) | auto account (convert & forward) | one auto account is reused across a recurring series; stablecoin conversion is 1:1                 |
| Crypto → bank (offramp)                                     | auto account                     | payout rails: `ach`, `fedwire`, `swift`; bank-rail constraints are validated at instruction accept |

Sandbox examples throughout these docs use `base-sepolia`, `ethereum-sepolia`, and `solana-devnet` with `USDC`.

## Mandate rule bounds

A mandate holds exactly **one rule**; authority is extended by additional mandates, never by editing (mandates are immutable once created).

| Dimension                         | Bound                                                                                                                                        |
| --------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
| `targets`                         | up to 32 per rule (`recipient` ids or raw `address`es, or `any`)                                                                             |
| `asset`                           | must be a sendable (deposit) asset — deployed on the rule's `network_id`, or on ≥1 network when the rule leaves it open; validated at create |
| `max_per_tx`                      | per-transaction amount cap, decimal string in the rule's `asset`                                                                             |
| `window`                          | `NONE` (lifetime) · `WEEKLY` (calendar week, Monday 00:00 UTC) · `MONTHLY` (calendar month, 1st 00:00 UTC)                                   |
| `max_amount_per_target_in_window` | cumulative amount cap over the window, **per target** — never pooled across targets                                                          |
| `max_count_per_target_in_window`  | fire-count cap over the window, per target                                                                                                   |
| `valid_from` / `valid_until`      | unix-second validity bounds; an expired mandate can no longer be approved                                                                    |

Every cap is enforced **at fire time** by the mandate gate — a schedule that outgrows its mandate fails with `mandate_denied` rather than firing.

## Conversation & drafting caps

| Surface                                                   | Cap                                                                           |
| --------------------------------------------------------- | ----------------------------------------------------------------------------- |
| Proposal drafting (`POST /payment-agents/{id}/proposals`) | 200 messages / 512 KB text per request                                        |
| Attachments                                               | PDF, PNG, JPEG, WebP, GIF · 8 MiB per document · 16 MiB per request (decoded) |
| Drafting budget                                           | 30 drafts/hour, 200/day per customer                                          |
| Insight chat (`POST /customers/{id}/insights/chat`)       | 40 messages / 4,000 chars per message / 64 KB per request                     |
| Insight chat budget                                       | 100 turns/hour, 500/day per customer                                          |

Budget overruns return `429` with a `Retry-After`-style problem body; input-cap violations return `400` before any model spend.

## Platform-wide limits that apply here too

* **API rate limits** — the standard per-key limits apply to every agentic endpoint; see [Rate limiting](/documentation/authentication/rate-limiting).
* **Idempotency** — every agentic `POST` requires `X-Idempotency-Key`, like the rest of the platform.
* **Sandbox amount cap** — sandbox caps transactions at **\$2 USD-equivalent** per transaction by default, agentic ones included. Drafts above the cap actuate but fail at fire time, exactly as an over-cap direct send would.

## Alpha scope

The published alpha covers **hosted** agents — Dakota manages the agent's signer key. Mandates themselves are not agent-only: the [direct create](/documentation/agentic-payments/direct-control#mandates) binds any of your signers. All endpoints are tagged *Alpha* in the [API reference](/api-reference/introduction) and covered by the standard API stability and breaking-change policy.