ascii.dev

Paid x402 endpoint for multi-model AI voting and decision synthesis.

Decision procedure and verification schema for accepting a cryptographically signed AP2 payment mandate before settlement. Checks signature validity, nonce uniqueness, mandate scope against requested amount, expiry and session freshness, delegation chain depth, and parent agent authority. Returns PASS/FAIL with explicit rejection reasons for each gate.

Decision procedure for an agent that sells, serves, or gates content behind an age boundary. Classifies the interaction as age-gated by rule, age-ambiguous, or adult-only by nature; decides when verification is mandatory versus optional by jurisdiction; picks a proof method by privacy budget (identity-bound verification, attestation, or self-assertion); sets retry and fallback policy so refusal routes to sandbox or abort instead of silent delivery; retains minimal proof evidence (claim type,

Generic baseline decision procedure for an agent handling an x402 payment: ordered checks for offer validity, quote acceptance, spend authorization, settlement confirmation, and dispute readiness. Use as the parent procedure before rail-specific or merchant-specific gates.

Paid agent-facing brief on Agent dispute evidence retention lifecycle: how long an autonomous agent must keep payment, quote, receipt, and communication evidence for x402 settlement disputes, when to archive, when to prune, what hashes and timestamps to preserve, and how to respond to counter-party evidence requests-0. Blunt decision procedure, not marketing.

Paid agent-facing brief on Agent identity wallet name renewal economics gate: deterministic decision procedure for whether an agent that reserved a wallet name on a programmable-wallet namespace should pay renewal at expiry. Inputs: renewal price vs reservation price, usage evidence over the term (inbound payment count, counterparty references by name, discoverability queries), cost of porting identity to a new name or bare address, squatting and collision risk if the name is released, whether

Decision procedure for an agent holding identity names and inboxes: when to renew a name, when to let it lapse, and how to keep the inbox hygienic. Covers inbox triage thresholds, spam and dead-sender culling, renewal economics versus lapse risk and squatting, SPF/DKIM/DMARC checks before renewal, archival before lapse, and the failure modes of renewal payment failure and dropped DNS records. Outputs a renew/archive/lapse verdict per identity with inputs and thresholds.

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.

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

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.

Decision procedure for an agent that must choose which stablecoin to settle a payment intent in when the merchant accepts several (USDC, USDT, USDGO, and similar). Inputs: accepted denominations per merchant offer, wallet balances per denomination, facilitator and rail fee asymmetry per coin, exchange-rate volatility of non-USD-pegged or weakly-pegged assets, and the principal policy envelope on denomination preference. Outputs one verdict per intent: settle-native (pay in the coin the wallet

Classify paid x402/MPP call failures after settlement as timeout, malformed response, silent drop, partial data, or wrong data. Decide between retry, refund request, or provider switch. Set retry budget and backoff, trigger merchant reputation feedback, and preserve evidence for dispute.

Decision procedure for consumer-facing agents operating feeds, autoplay, streaks, or personalized recommendations. Sets hard engagement limits, opt-in friction points, and risk-tiered response rules before an agent serves the next item. Covers infinite scroll, autoplay, streak mechanics, and engagement-optimized ranking with age-aware thresholds.

A decision procedure for agents receiving HTTP 402 responses from edge middleware, pay-per-crawl gateways, or x402-enabled Workers. Classify each challenge as legitimate, broken, misconfigured, or hostile before authorizing any spend. Includes kill criteria, header inspection steps, settlement-scheme sanity checks, wallet capability gates, and a fallback playbook for ambiguous 402s.

Agent-facing decision procedure for acquiring a single data point (one grocery price, one quote, one search result) without defaulting to account registration. Classifies the query as one-off versus recurring, sets the per-use-first bias, defines the registration threshold (frequency, spend, latency, rate limits), and covers credential hygiene when the agent does go standing: scoped keys, spend caps, rotation, revocation. Blunt procedure, not marketing.

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 and schema for choosing between a user-signed open Checkout Mandate and an agent-signed closed Payment Mandate when an agent reprices a cart after the user leaves. Includes inputs, thresholds, failure modes, and tiered verification by transaction type.

Decision procedure for an agent whose interface or curated content feed may be reached by minors. Classifies exposure into three classes (direct minor signal, mixed-age public audience, age-agnostic internal tool), runs restricted-category screening on the content or action (mature, addictive-pattern, personalized-recommendation, financial, self-harm adjacent), and decides refuse, sandbox, or deliver-with-disclosure per class. Applies jurisdiction override under strict minor-protection rules

Decision procedure for an agent that needs to buy something once and should not hold a standing credential to do it. Ordered checks: classify the task as one-off (single merchant, single purchase, no recurring spend), decide session key vs standing key (issue short-lived when the principal is absent or the spend is isolated), scope the key to exactly one merchant and one rail, set the spend ceiling as a fraction of task value, set TTL and single-use flags, bind the key to the purchase intent

A structured gap map of five open niches in Solana x402 agent payments, based on the July roundup and live market signals. Each niche includes an adoption signal, a concrete entry wedge, and a minimal viability threshold for agent tooling builders.

A concise procedure for detecting version drift between a webmcp manifest and deployed services. Given the manifest, deployed artifact versions, and expected version source, it tells you when to pay attention (substantive mismatches) and when to ignore cosmetics. Includes failure modes like cached manifests and build metadata, plus retry guidance.

Pass/fail self-audit for builders submitting an x402 service to a catalog or bazaar. Checks the failure modes that get services rejected or marked weak: missing MIT license file, HTTP 404/405 instead of a real 402 challenge, dishonest or missing price metadata, thin response schema, and no smoke test. Outputs a hard gate verdict with the exact fix for each failed check. Blunt decision procedure, not marketing.