x402 Agent Wallet Tools: Receipt Gate Policy
Build receipt-bound execution policy for x402 payment responses and receipt URLs. receipt-gate-policy first: a $0.001 x402 receipt gate route for agent payment enforcement, followed by wallet signing safety, EIP-712, ERC20 allowance, Permit2, transaction simulation, spend guard, and private-key boundary tools. Start buyer evaluation at https://x402-wallet.558686.xyz/x402/buyer-use-cases or machine JSON https://x402-wallet.558686.xyz/x402/buyer-use-cases.json; checkout contract JSON is https://x402-wallet.558686.xyz/x402/checkout.json. Route payment activation JSON is https://x402-wallet.558686.xyz/x402/route/receipt-gate-policy/payment-activation.json. Browsers can inspect the quote, but payment requires a buyer-owned runtime that signs and retries the same request with X-PAYMENT. Buyers c
Start with a quote-only recipe. Payment signing stays in your project.
const response = await fetch("https://x402-wallet.558686.xyz/v1/tools/receipt-gate-policy", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"replace": "with provider-approved input"
}),
});
console.log(response.status);
console.log(Object.fromEntries(response.headers));
console.log((await response.text()).slice(0, 1000));
// A valid 402 is a quote, not a completed paid call.Review the provider input schema before running this non-read-only method. No payment code is included.
- Exact route checked
not safely testable · potentially-mutating-method:POST
- Origin unavailable
ERR_SSL_PACKET_LENGTH_TOO_LONG
- Observed in 402-index
Discovered through self-registered.
- Registry record checked
Registry health: healthy.
EVIDENCE
Each record has an exact-route quote outcome. Unresolved templates and potentially mutating methods are labeled instead of being invoked without provider-specific test input. A quote is still separate from a settled paid call.