Policies

—

Payment policies

Simulate a payment against deterministic rules before your agent settles it. Decisions are read-only and written to the audit trail.

How to use this page & what the results mean
How to use this page
  1. Edit the Payment JSON with the transaction you want to test. Keep required fields such as agentId, endpoint, amount, chain and token. Amounts use the token’s smallest unit (for USDC, 50 USDC = 50000000).
  2. Edit the Rules JSON as an ordered list. Each rule has a field, operator, comparison value, action and optional reason; the first matching rule wins.
  3. Click Simulate decision. This checks the JSON and returns whether the payment is allowed, denied, requires approval or should be throttled.
  4. Use the returned rule ID and reason when wiring the same contract into your Agent SDK. Simulation is read-only and does not execute a payment.
What the results mean
  • allow continues, deny blocks, require_approval pauses for a human, and throttle signals a rate limit.
  • Rules are evaluated top to bottom; no match defaults to allow.
  • This page does not mutate funds or payment state.

Start safely: use the example JSON already shown, change one value at a time, and run Simulate decision before copying a rule into production. Invalid JSON is reported below the button.

Payment
smallest token unit
Rules
first match wins
Connect a Collector to run a simulation.