← ClaudeAtlas

x402-erc7710listed

Design and implement demos combining x402 HTTP payments with ERC-7710 smart contract delegations and ERC-7715 wallet permission requests for subscriptions, bounded agent budgets, recurring spend, pay-per-use APIs, and agentic commerce.
internet-court/internet-court-skill · ★ 5,854 · AI & Automation · score 78
Install: claude install-skill internet-court/internet-court-skill
# x402 + ERC-7710 Use this skill when a user wants a payment or subscription demo where an agent pays for HTTP resources through x402 and spends only within a bounded delegated permission. ## Core Model - x402 is the per-request payment rail. A protected resource can respond with HTTP `402 Payment Required`, payment requirements, and a retry path where the client submits a signed payment payload. A facilitator can verify and settle the payment before the server returns the resource. - ERC-7710 is the capability redemption interface. It standardizes how a delegation manager validates permission context and executes delegated actions on behalf of a delegator. - ERC-7715 is the wallet permission request layer that can be used to obtain scoped permissions for ERC-7710-style delegation. Use x402 for "pay now for this HTTP request." Use ERC-7710/7715 for "this agent may keep paying under these constraints." ## Discovery-First Boundary When the user has only asked to use or inspect a paid HTTP service, stay in discovery mode: 1. Identify the relevant endpoint or resource. 2. Confirm whether it returns `402 Payment Required`. 3. Summarize the advertised x402 requirements: network, token, amount, payee, route, and `extra.assetTransferMethod` when present. 4. State that no paid request has been made. 5. Ask whether the user wants to set up bounded payment authority. Do not draft a subscription, mandate, cadence, schedule, spend cap, expiration, or wallet permission until the us