Set your policy

Coming with the beta. Setting the policy from the Mini App arrives with the beta. The policy itself is enforced on Solana devnet today. See what works today.

What happens to a request

Outcome	When	What happens
Goes through	Inside your caps and budgets, to an active payee or an allowed market	Your registered device authorizes the request and the chain checks it
Refused	Over a cap or budget, to an address that isn’t an active payee, or after the policy expired	Recorded onchain with the reason. Nothing moves

When a payment is refused for being over the cap, the owner can still pay it directly from their own wallet.

What you set

Limit	What it controls
Payment cap	The largest single payment to a vendor. A payee can also have its own lower cap
Payment budget	The most that can go out in payments per day, week, or 30 days
Trade cap and budget	The largest single trade, and the trading volume allowed per window
Allowed markets	Which assets the agent may trade, and whether it may buy, sell, or both
Service budget and purse cap	How much the agent may spend on paid services per window, and the most its purse can hold at once
Payee activation delay	How long a new payee waits before it can be paid
Expiry	When the policy stops working, so it has to be renewed on purpose

Budgets reset on UTC boundaries: daily at midnight, weekly on Monday, or every 30 days.

Example policy

A nine-person studio with a 40,000 USDC treasury might set:

Payments: up to

500 a payment and

2,000 a week, only to payees on the allowlist.

Trading: up to

250 a trade and

1,000 a day, in two allowed markets.

Services: up to $20 a day for the agent’s research and translation tools.

New payees: payable 24 hours after the owner adds them.

Get started

Using Pact

Trust and safety

Reference

What happens to a request

What you set

Example policy

Changing the policy

​What happens to a request

​What you set

​Example policy

​Changing the policy

What happens to a request

What you set

Example policy

Changing the policy