Execute pay-per-call deterministic services
The agent obtains a specific result from a deterministic service by paying a small fee per call, handling potential refusals or rate limits.
How it works
The agent identifies a suitable service from the catalog (e.g., 'mojibake-repair') and retrieves its input schema via the example endpoint. It constructs the JSON input and sends a POST request to the run endpoint. If a 402 response is received, the agent signs the payment with its x402 wallet and resends the request. The agent must handle errors like refusals ('CANNOT...') or rate limits by checking the response headers and body, ensuring it does not retry refused inputs.
Prompt
Paste this into an agent that has the servers below connected. Adjust the names and dates to your own.
Use the aiskills402 service to repair mojibake in the text 'Hello Wörld'. Check the example input schema first, then execute the service with payment.MCP servers it needs
Source
The vendor page this playbook is drawn from, and the passage that supports it.
POST the JSON input to https://api.aiskills402.com /v1/run/<slug> with no payment header. The answer is 402 with a PAYMENT-REQUIRED header. Sign accepts[0] (scheme exact , USDC, Base) with an x402 client.Connect your agent — AISkills402