What problem does it solve?
When an AI agent hits an HTTP 402 Payment Required paywall mid-task, it needs a safe way to pay for the content without being able to decide who gets paid, how much, or how often. This Skill enforces every payment decision in code from an operator-owned policy file, so neither the model nor prompt-injected content can authorize or raise spending.
Core Features & Use Cases
- Policy-gated x402 payments: Validate recipient, network, asset, scheme, origin, and per-payment ceiling in Python before any signing occurs.
- Human-approved session budgets: A human creates budget-bounded payment sessions at a TTY; the agent can only spend within an approved session and can never mint new budget.
- Hardened fetching and proof isolation: HTTPS-only requests with SSRF protections, no redirects, pinned IPs, idempotent retries, and signed proofs that never reach model context.
- Use Case: Your coding agent hits a 402 while calling a paid API. With a pre-approved $1 session and a $0.05 per-payment cap, the agent pays the merchant, receives response metadata and a content hash, and stops spending when the budget runs out.
Quick Start
Ask the agent to pay for the x402-protected URL using the configured payment session, for example: pay for this API endpoint that returned a 402 error.