Identify planted flaws in x402 listings, such as catalog facts or buyer client errors, to ensure payment integrity before execution.
The agent analyzes x402 payment listings to detect flaws that models typically miss, such as incorrect catalog information or buyer client details. It checks the seller's offer, the signed header, and the receipt on Base. The agent should verify that the listing details match the actual payment state and flag any discrepancies in the HTTP 402 response or USDC authorization.
- Category: Finance and payments
- Effect: Read-only
- MCP servers: AISkills402 MCP (https://koskamo.com/explore/aiskills402-mcp)
- Source: Blog: measured notes on agent skills and x402 — AISkills402 (https://aiskills402.com/blog)
- Source quote: "Unaided, Sonnet named 10 of 16 planted flaws in x402 listings and Haiku 6. Most misses were facts about the catalog and the buyer client."
- Playbook page: https://koskamo.com/explore/use-cases/review-x402-payment-listings-for-flaws
Prompt: Review the following x402 listing for flaws. Check for errors in the catalog, buyer client details, seller's offer, signed header, and Base receipt. Identify any planted flaws or inconsistencies that might cause payment failure.