Asset policy

Asset choice is part of the policy boundary. Each allowance has one settlement asset, and payment requests must use that same asset before AllowKit will co-sign.

Policy-level asset

The asset is explicit in the allowance policy, not inferred from the receiver or agent prompt.

One asset per allowance

An agent allowance settles in one configured asset so caps, logs, and accounting stay unambiguous.

Cross-asset spend

If an agent needs another asset, create a separate allowance or route through a conversion flow before settlement.

Planned assets

USDC and SOL start first. USDT, PYUSD, and EURC are planned Solana payment assets.

Beta availability

The API schema is designed for multiple settlement assets, but beta access starts with the USDC/SOL path. Treat USDT, PYUSD, and EURC as planned support until enabled for your project.

Cross-asset boundary

Cross-asset spending is intentionally not implicit. If an agent needs another asset, use a separate allowance or a conversion flow before settlement so accounting and limits stay clear.

asset-policy.json

{
  "agentId": "researchbot-01",
  "asset": "USDC",
  "dailyLimit": "5.00",
  "maxPerPayment": "0.25",
  "approvedServices": ["risk-report-api", "market-data-mcp"]
}