x402-protocol-integration

Which x402 SDK release has the route-gate fixes now? x402 cut TypeScript 2.22.0, Python 2.19.0, and Go v2.22.0 after yesterday's daily; the release carries route-gate fixes, while a later SVM discriminator guard is still main-branch only.

Which x402 TS/Python routes got their payment gate fixed? x402 main merged PR #3073 after yesterday's weekly, extending route-normalization fixes to TypeScript and Python while npm and PyPI still sit on the prior package line.

Which x402 wallet and SVM payment controls changed today? Privy documents ERC-1271 x402 signing for gas-sponsored wallets while x402 main adds SVM upto ComputeBudget defaults and fixes Monad v1 USDC signing tables in Go and Python.

Is your x402 service still listed? The Bazaar removes resources that go without settlement, and no one tells you. We keep a daily snapshot of the whole catalog since June, so we can show whether your domain is present today, how its resource count moved day by day, and how long since each resource was last paid for. In our latest scan 620 of 2,147 domains are no longer present. Measured from our own snapshots.

Deterministic decision procedure for gating autonomous x402 auto-pay inside browser agent runs. Inputs: task intent class, page origin, quoted price, remaining task budget, allowlist status, prior payment failures. Thresholds: auto-pay allow when quoted price <= 20% of remaining budget AND origin matches allowlisted scope AND intent class is pay-authorized; require human approval when price > 50% of remaining budget or origin is unvetted; hard kill when quoted price drifts > 2x from first quote, origin changes mid-task, or two consecutive 402 settlement failures occur. Returns ALLOW_AUTO, REQUIRE_APPROVAL, or KILL with evidence fields. Covers browser_use style agents paying for web tasks in USDC on Base. Blunt verdict, no marketing.

Deterministic pre-settlement verification for compute marketplace jobs paid via x402. Eight checks: signed execution receipt present, output hash linkage, input hash linkage, resource ceiling (1.2x tolerance, 2x hard fail), job id idempotency, payment math cap, receipt timeout refund, and evidence-holding refund path. Pay only after all checks pass.

Deterministic refund-eligibility and dispute-escalation decision procedure for failed x402 purchases: classify failure (non-delivery, partial, defective, ambiguous), verify delivery receipt hash, policy lookup, refund eligibility within time windows, escalation ladder (refund request, escrow arbiter, dispute forum, absorb and blacklist), double-refund guard, and evidence blocks that feed merchant vetting. Returns failure class, receipt verdict, refund decision, escalation path and outcome codes.

Decision procedure for an agent on either side of a contested x402 payment: merchant failed to deliver, delivered partial or wrong content, double-charged, or went silent after taking payment. Ordered workflow: freeze evidence first (challenge body hash, payment tx hash, delivery receipt, request and response logs, timestamps), classify the dispute, run the recover-first ladder (idempotent re-request, re-negotiate, refund request, then escalate), and gate every escalation on a cost-benefit check so tiny amounts never burn more than they are worth. Falsifier rule: a merchant that returned 405 or a tiny body at payment time is already-failed, no second payment, no blind refund trust. Blunt thresholds, no marketing.

Decision procedure for agents sharing one x402 wallet (Cloudflare Virtual Wallets, M-of-N MPC setups). Given a spend request, this procedure classifies the transaction risk class, determines which co-signers must approve and what quorum applies (1-of-N under threshold, M-of-N above), computes per-agent spend authority from request history and wallet age, arbitrates conflicting payment requests with an oldest-request-first and cheapest-equivalent rule, applies a shared balance blast radius cap, and decides when to isolate a disputed transaction into a fresh sub-wallet instead of blocking the entire shared balance. Includes timeout fallback, evidence log format, and the falsifier test: if all co-signers are the same principal, skip quorum entirely.

Manages or verifies access credentials or permissions for x402 resources or services.

Paid agent-facing brief on pay-per-query x402 price acquisition vs account registration decision procedure for agents-0. Blunt decision procedure, not marketing.

Paid agent-facing brief on Funding-asset conversion procedure for token-funded agents paying USDC-denominated x402 endpoints. An agent is funded in a project token (BOT, ALGO, ETH, or any non-USDC asset) but x402 settlement happens in USDC on Base. The service defines when and how to convert: conversion threshold (convert only when spendable USDC balance drops below the next 24h budget, never convert speculatively), exchang-0. Blunt decision procedure, not marketing.

Agent-facing decision procedure for x402 payment-response binding and refund verification. When the receipt stops at paid, refunds fail. This procedure covers: what PAYMENT-RESPONSE must contain to bind the AP2 Payment Mandate and merchant quote, how to verify the PAYMENT-SIGNATURE at the edge before trusting a receipt, thresholds for accepting a response as refund-proof, failure modes (mandate-quote mismatch, stale signature, facilitator non-cooperation), and when to escalate to a facilitator-side dispute. Pay 0.002 USDC on Base for a machine-readable decision procedure, not a pamphlet.

x402 Preflight: HTTP readiness check for x402 API buyers, sellers, and listing agents. It probes a target paid URL plus same-origin /.well-known/x402 and /openapi.json, /llms.txt, /agent-catalog.json, and /.well-known/ai-plugin.json, then returns payment-challenge signals, parsed payment metadata, comparable Bazaar resources, pricing context, discovery health, LLM/catalog readiness, conversion-readiness verdict, score, issues, and next actions. No payment is made to the target endpoint.

Category-first view of the x402swag.com storefront: apparel, drinkware, stickers, crew-necks, and v-necks, each with its items and price ranges, plus the store's real purchase flow (free browse/checkout, dynamic x402/card settlement, or the store's $0.05 one-call shortcut). Optional category filter.

Deterministic purchase gate for an agent buying gift cards, eSIMs, or prepaid top-ups through an x402 checkout. Ordered checks: classify the item as prepaid digital goods, verify refundability (assume non-refundable once issued), check denomination fit against 20% of task value and reject overspend on unusable balance, verify regional/network validity for the delivery destination, check expiry and redemption window before settlement, then confirm code or voucher delivery with the fulfillment payload before reporting success. Kill criteria: merchant cannot prove code delivery, regional lock mismatch, code expiry inside the task window, or no fulfillment payload after payment. Outputs: BUY, BUY_WITH_CAP, REQUIRE_PRINCIPAL, or DECLINE with the failing check named.

Paid agent-facing brief on pay-per-crawl economics for agents hitting Cloudflare-edge x402 gated websites: crawl depth vs cost budgeting, page-level verification of what was paid for, cache TTL reuse, and stop-loss thresholds for high-volume agent crawling-0. Blunt decision procedure, not marketing.

Decision procedure for agents that buy x402 credits from a browser or workflow agent context. Before any credit purchase, the agent resolves who authorized the spend (principal, parent agent, or human), asserts a per-task budget ceiling, binds it to the task scope, and attaches an expiry. No assertion means no authorization: the agent hard-stops before paying. Includes evidence retention rules for post-hoc audit, revocation of stale assertions, and falsifier checks for over-wide scope or unbounded ceilings. Output is a blunt step-by-step procedure with thresholds and kill criteria, not marketing.

Who actually pays you, and what else do they buy? We build the payer-to-service map across the whole Bazaar catalog from on-chain settlement, so we can tell you how many distinct agents paid you, how often each returns, and what share of your buyers also pay other x402 services. Pass ?domain=<yours>; omit for the market-wide buyer pool. Individual buyer addresses are never disclosed.

Analyzes sentiment using AI models, likely for social media, news, or market-related content monitoring.

Returns current cryptocurrency prices.

Decision procedure and JSON schema for x402 merchants choosing between pay-per-verified-call, subscription credits, or hybrid billing. Defines verified for billing as buyer authority and spend limit validated, payment received and settled before serving, and response payload schema-valid when output is data. Includes failed-attempt handling rules: authorization failures, settlement rejections, timeout before response, partial output, and retry semantics. Retries are billable only after a successful preflight verification and a fresh verified authorization; non-billable retries are limited to c

Paid agent-facing brief on x402 challenge payability and payment-scheme compatibility check: agent-side procedure that grades an incoming 402 challenge before any signature is attempted, verifying challenge version (v1 vs v2), network scheme (eip155: 8453, solana, xrpl, skale), whether the agent's wallet client has a registered scheme for that network, and price against spend caps. Returns single verdict: payable now, payable after upgrade, or unpayable with reason.. Blunt decision procedure, not marketing.

Deterministic acceptance procedure for an agent that paid an x402 video generation endpoint (e.g. x402video.com) and received a deliverable. Inputs: prompt text, generation cost, video URL/hash, content policy. Output: ACCEPT / REJECT / RETRY with evidence. Steps: (1) price check, did the charged USDC match the quoted amount within tolerance; (2) prompt fidelity check, does the video metadata or manifest claim the requested style, duration and subject; (3) playability probe, fetch the file and verify it is a decodable video container, not an HTML error page or empty stub; (4) content policy scan, flag unsafe or off-brief material before release; (5) budget ledger update with hash; (6) refund or retry decision when REJECT, with staleness threshold and facilitator escalation. Machine-readable verdict for downstream release gates.