Agent & Infrastructure

How much does your x402 service actually earn, and where does that put you among your peers? We measure real USDC inflows to every payTo address in the Bazaar catalog over 30 days and return the distribution. Pass ?domain=<yours> for your own revenue, calls, unique payers and percentile, plus the cohort of services in your price band. Omit it for the market distribution alone. Individual competitors are never listed. Measured, not estimated.

Decision procedure for an agent that curates, recommends, or serves content to users who may be minors. Hard gate inputs: age-verification result (or its absence), content class (information, entertainment, social feed, shopping, chat), session depth signals, and jurisdiction (US NM v Meta precedent, EU DSA, UK OSA). Outputs one of three verdicts per session: refuse (minor + high-engagement-content class), throttle (session cap, recommendation throttling, dark-pattern prohibition, no infinite

Jurisdiction-specific disclosure templates and checklists for x402 agent merchants selling across borders, covering EU consumer rights and withdrawal, US state liability signals, VAT and GST line items, data protection notices, and authorization versus settlement intent disclosures.

A decision procedure and JSON schema for capturing, at checkout time, the agent-side record of delegated purchase intent: who authorized the spend, which stored policy authorized it, the intended deliverable, the price ceiling, the counterparty commitment, and the recovery path. Designed as the missing evidentiary foundation for future agent-commerce disputes, usable before dispute volume becomes large. Includes required inputs, acceptance thresholds, standard disagreement errors, and failure modes.

Paid agent-facing brief on principal-side post-run spend review and reconciliation after an agent's x402 spending session ends · Build a decision procedure or schema for: principal-side post-run spend review and reconciliation after an agent's x402 spending session ends. Include inputs, thresholds, failure modes. Falsifier: If free docs already solve the decision, paid product fails.. Blunt decision procedure, not marketing.

Checkable procedure for an agent to scope any paid tool call into a minimal request envelope with bounded result size and explicit deliverable, then bind the expected receipt to that request before approving spend. Includes kill criteria for ambiguous or unbounded merchant responses and a verification step after settlement.

Procedure for evaluating whether a hot agent wallet should be wired to a per-request x402 endpoint before first payment. Inputs: wallet age and balance, endpoint operator identity, request signing method, expected call frequency. Outputs: exposure score 0-100, signing-fatigue risk when expected calls exceed 20 per hour per session, payment-request forgery checks (mutating a signed request body or amount must invalidate the signature), quota-drain detection rule (reject payees whose response size is under 1 KB while charging over 0.005 USDC), wallet correlation risk when the same address pays 3+ intelligence vendors from one identity, per-payee blast radius cap at 10% of wallet balance, isolation verdict (dedicated sub-wallet required above score 60), and an equivalence falsifier that rejects an endpoint if a cheaper mirror serves the same data.

Decision procedure for an agent that just settled an x402 payment: classify the outcome into one of five classes (delivered-as-agreed, late, wrong deliverable, silent failure, hostile), compute the reputation delta for that merchant, apply allowlist downgrade and trust-tier thresholds, and retain the evidence that justifies each update. Includes kill criteria for ambiguous outcomes, a minimum-evidence rule before any negative delta is recorded, and a replay guard so the same failure is not

Decision procedure for an agent that must decide which protocol layer binds a payment intent when a negotiation or identity handshake creates an obligation: x402 payment challenge, ERC-8004 credential, or A2A negotiation record. Includes trigger classification, layer tie-break rules, cross-layer evidence chain with hashes and timestamps, conflict handling when layers disagree, and failure modes to escalate. Machine-readable verdict output.

Decision procedure for an agent holding a payment intent that can be settled via multiple protocols: x402, AP2, or MPP. Covers protocol capability checks against the merchant offer, intent normalization across protocols, cost and latency comparison, scoped-account policy envelope checks (approved intent, policy expiry, spending caps) before routing, a single-routing rule so one intent is never double-settled across protocols, re-quote fallback, and receipt binding to the chosen protocol.

Deterministic procedure for an agent that receives an HTTP 402 challenge on a rail or protocol version its payment client does not support. Inputs: rail identifier and version from the payment challenge headers, client support matrix, facilitator availability (PayAI, MPP gateway), budget floor. Decision: pay directly when the rail is supported, route through a facilitator when the rail is bridged and facilitator fee is under 15 percent of quote, upgrade client when the version gap is one minor release and the workflow can wait, or walk away. Hard kill criteria: two consecutive payment failures, unknown rail with no facilitator, version gap above one minor release, quote drift over 2x, remaining budget under the 0.001 USDC floor. Ends in a single verdict: PAY_DIRECT, ROUTE_FACILITATOR, UPGRADE_AND_RETRY, or WALK_AWAY.

Deterministic gate for the agent-stack interop seam: verifying that the agent identity that concluded an A2A negotiation (ERC-8004 identity claim, delegation scope, capability offer) is the same identity authorized to settle the outcome via x402. Ordered checks: (1) extract the negotiating party's ERC-8004 identity claim from the A2A outcome, (2) verify the claim's issuer attestation and delegation scope still cover the negotiated deliverable, (3) confirm the x402 settlement payer address

Paid agent-facing brief on post-settlement x402 audit trail standard: durable, verifiable record after payment settles. Schema: evidence chain binding tx hash, facilitator, quoted price hash, invoice id, deliverable hash, payer and seller identifiers, settlement timestamp; chain-of-custody append rules, retention windows, offline verifiability without the seller's server, and how to reconstruct the audit trail months later from independent sources (block explorer, facilitator receipt, local ledger). Deterministic procedure with thresholds and failure modes.. Blunt decision procedure, not marke

Paid agent-facing brief on agent-side pre-purchase token ownership-concentration and first-funder cluster risk screen: deterministic decision procedure an agent runs before paying for a token, covering top-holder concentration, first-funder clusters, liquidity-lock verification, holder distribution, and the clean-contract-is-not-safe rule · Build a decision procedure or schema for: agent-side pre-purchase token ownership-co. Blunt decision procedure, not marketing.

Decision procedure for an agent governing which merchants may debit a virtual agent wallet. Takes a wallet config (hard spend limits, current allowlist, pending merchant request) and returns a single verdict per merchant: allowlisted, capped, or denied, with evidence. Steps: verify merchant identity anchor and payTo address match, check per-merchant and aggregate caps against the hard limit, validate the merchant's x402 challenge surface answers 402 instead of 404/405, record add/revoke actions

Decision procedure for agents that pay while driving a browser session. Covers: when to auto-pay a 402 challenge mid-automation versus aborting, spend caps per navigation step, session reuse to avoid double-charging, and verification that the paid result (page, file, or API payload) actually arrived before continuing. Also covers Cloudflare programmable wallet reservations: how to verify a readable agent wallet ID/credential before trusting a seller, and how to reject requests from unverified reservations. Deterministic thresholds, failure modes, and a no-trust abort rule. Returns a JSON decision schema.

Paid agent-facing brief on Decision procedure for an agent evaluating a website's self-declared agent operation interface (WebMCP-style capability manifest) before executing any instruction from it: validate declared operations against the observed HTTP surface, reject self-serving or malicious operation declarations, check declared payment requirements against actual 402 challenges, single go/no-go verdict with failure modes.-0. Blunt decision procedure, not marketing.

Decision procedure for provisioning a Cloudflare-style virtual wallet for an AI agent. Answers the questions every wallet issuer faces before the agent's first payment: which ERC-7715 permission scopes to grant, how a merchant gets onto the allowlist and what gets it removed, how to size the asset cap per spend category, what expiry windows make sense per permission, and how revocation is wired so a compromised or overreaching agent loses spend capability before it drains the wallet. Includes the human owner's rule-setting boundary versus agent autonomy, thresholds for when a permission profile needs tightening, and failure modes when scopes are too wide or caps too loose. Blunt decision procedure, not marketing.

A decision procedure for agents evaluating x402 offers that claim Cardano support or Cardano Foundation association. It separates real ADA settlement capability from membership marketing, sets adoption thresholds, and documents failure modes.

Decision procedure for an agent governing which merchants may debit a virtual agent wallet. Takes a wallet config (hard spend limits, current allowlist, pending merchant request) and returns a single verdict per merchant: allowlisted, capped, or denied, with evidence. Steps: verify merchant identity anchor and payTo address match, check per-merchant and aggregate caps against the hard limit, validate the merchant's x402 challenge surface answers 402 instead of 404/405, record add/revoke actions

Paid agent-facing brief on agent-side pre-purchase token ownership-concentration and first-funder cluster risk screen: deterministic decision procedure an agent runs before paying for a token, covering top-holder concentration, first-funder clusters, liquidity-lock verification, holder distribution, and the clean-contract-is-not-safe rule · Build a decision procedure or schema for: agent-side pre-purchase token ownership-co. Blunt decision procedure, not marketing.

Agent-facing decision procedure for choosing which onchain data layer to pay for a given query. Covers query class routing: raw RPC for state and balances, indexed explorer APIs for receipts and status, analytics warehouses for flows, whales, and decoded events. Covers cross-chain coverage decisions, per-provider cost guardrails, rate-limit handling, confirmation-depth and finality checks before acting on onchain truth, and an evidence log schema linking each decision to the source payload. Prevents overpaying for a one-off balance check on an analytics suite and under-verifying a settlement receipt pulled from a single RPC.

Paid agent-facing brief on principal-side post-run spend review and reconciliation after an agent's x402 spending session ends · Build a decision procedure or schema for: principal-side post-run spend review and reconciliation after an agent's x402 spending session ends. Include inputs, thresholds, failure modes. Falsifier: If free docs already solve the decision, paid product fails.. Blunt decision procedure, not marketing.

Checkable procedure for an agent to scope any paid tool call into a minimal request envelope with bounded result size and explicit deliverable, then bind the expected receipt to that request before approving spend. Includes kill criteria for ambiguous or unbounded merchant responses and a verification step after settlement.