Pay

Set an agent's payment guardrails

Human owners and admins only. These are the numbers every payment decision is measured against: the per-payment cap, the daily limit, the recipient allowlist, whether a passkey is required at all, and whether the agent may hold a spending grant. An agent that could set them would be setting its own ceiling.

Omitted fields are left alone; null clears a cap, the allowlist or the grant TTL. A change that widens anything (raising or clearing a cap, turning pay or grant mode on, turning a passkey or approval requirement off, a longer grant TTL, or naming a recipient that is not already on the allowlist) needs X-Auth-Confirm with a re-auth token for purpose security.agent_pay_guardrails.widen (strong factor: a password is refused once a passkey or TOTP is enrolled). Tightening needs no step-up. Audited agent.pay_guardrails_updated.

No allowlist is not a wildcard: null and [] are enforced alike, so an agent with pay_require_passkey: false and no allowlist can pay no one unattended.

patch/v1/agents/{agent_id}/pay/settings

Request

  • Base URL: https://api.1claw.co
  • URL: https://api.1claw.co/v1/agents/{agent_id}/pay/settings
  • Auth: HTTP bearer

Path parameters

agent_idstring uuid required

Headers

X-Auth-Confirmstring

Required for a widening change; see above.

Request body

pay_enabledboolean
pay_max_usdstring nullable
pay_daily_limit_usdstring nullable
pay_payto_allowliststring[] nullable

Recipients an unattended agent may pay. Null is not a wildcard: it is enforced exactly like [], so for an unattended agent it means no one. An agent that requires a passkey or an approval can pay any recipient a person approves, payment by payment.

pay_require_passkeyboolean

Defaults true. Turning it off is what "unattended" means.

pay_require_approvalboolean
pay_grant_mode_enabledboolean
pay_grant_max_usdstring nullable
pay_grant_max_ttl_secsinteger nullable

Response

Updated guardrails

Changes

No recorded changes to this operation across all 1 revision of this API.