Skip to content

Automatic Policies (x402)

Automatic policies let an agent pay x402‑protected APIs without prompting you every time. Policies are host‑scoped and apply limits you control.

What a policy covers

  • Scope: a single host (e.g., api.example.com).
  • Applies to: x402 payments signed by the selected agent to that host.
  • Decision: if the requested amount and frequency are within your limits, the payment is auto‑approved; otherwise a prompt appears.

Policy fields

  • Per‑transaction max: the maximum amount allowed for any single payment.
  • Daily amount limit: the total allowed per day for this host.
  • Daily count limit: the maximum number of payments allowed per day.
  • Monthly limit: the total allowed per calendar month for this host.
  • Minimum interval: a cooldown (in seconds) between auto‑approved payments.
  • Valid until: the date/time after which this policy stops applying.
  • Active: enable/disable without deleting.

Resets and time windows:

  • Daily counters reset once per day.
  • Monthly counters reset on the first day of each calendar month.
  • If a policy is expired or inactive, requests will require approval or a new policy.

Create a policy

You can create policies in two ways:

  1. From a Payment Request: when approving a pending request, choose “Always allow for this host” to create a recurring policy with sensible defaults. You can optionally override limits (per‑tx, daily, monthly) during approval.
  2. From AI Agents → select an agent → x402 Payment Policy → + Add Policy: specify the host and all limit fields.

Common denials and fixes

  • Per‑transaction limit exceeded → raise the per‑tx cap or approve once manually.
  • Daily or monthly limit exceeded → raise limits or wait for the next reset.
  • Payments too frequent → increase the minimum interval or approve once manually.
  • Policy expired/inactive → extend validity or re‑enable the policy.

Released under the MIT License.