Agent & Infrastructure

Decision procedure for agents adopting a newly operational x402 rail such as Algorand x402. Covers staged funding caps based on cumulative settled volume, settlement finality verification before cap escalation, fallback retention on existing rails, and explicit exit conditions when the new rail underperforms.

Decision procedure for when a one-off x402 mandate should become a standing delegation, with bounds for merchant allowlist, per-period spend caps, expiry, revocation triggers, and refusal criteria.

Paid agent-facing brief on EIP-3009 gasless USDC settlement decision procedure for x402 agents: when an agent wallet holds only USDC and no ETH for gas on Base, decide whether to pay via transferWithAuthorization (merchant pulls funds, no gas needed on agent side) versus funding ETH first versus refusing; cover signature expiry, nonce uniqueness, replay protection, merchant-never-submits risk, and the refund path when authorization expires uncollected.-0. Blunt decision procedure, not marketing.

Paid agent-facing brief on compute proof class selection for verifiable agent-run compute: map use case (price, risk, failure cost) to required proof class (TEE attestation, zk proof, oracle assertion, log-based claim) with refusal thresholds when seller offers only weak proof for high-value compute · Build a decision procedure or schema for: compute proof class selection for verifiable agent-run compute: map use case (pric-0. Blunt decision procedure, not marketing.

Paid agent-facing brief on low-cost preflight validation of malformed 402 payment challenges before any payment attempt-0. Blunt decision procedure, not marketing.

Paid agent-facing brief on Settlement mechanism selection for x402 agent payments: decision procedure choosing between atomic ZK-proof-gated release, escrow-based release, and post-hoc receipt reconciliation, trading proof availability, latency, proof cost, and dispute exposure before funds move. · Build a decision procedure or schema for: Settlement mechanism selection for x402 agent payments: decision procedure choosing b-0. Blunt decision procedure, not marketing.

Paid agent-facing brief on agent authorization attestation handoff to clearing networks: verifiable proof that a spend is authorized, exportable to a third-party clearing/settlement layer without revealing private keys. Covers delegation-chain hash, mandate receipt, expiry proof, spend-cap binding, replay of attestation, and when to refuse attestation export. · Build a decision procedure or schema for: agent authorization a-0. Blunt decision procedure, not marketing.

Decision procedure for agents receiving variable per-request pricing from x402 vendors. Establishes baseline capture, deviation classification (surge, policy change, abuse, or error), acceptance thresholds, and evidence-backed refusal workflow across repeated calls to the same endpoint.

Decision procedure: verify that an agent's x402 payments stay within owner-set controls when the paying principal is a character agent or NFT-bound agent identity (ERC-8004), not a human. Covers agent identity resolution to owner, custody-layer classification (Circle agent wallet, Cloudflare Wallets with Visa/Stripe/Google/Coinbase backing, self-custody), spend-cap and allowlist checks, revocation of characters, and verdicts APPROVE / DENY / NEEDS_OWNER_APPROVAL / CONTROL_ESCAPED with evidence.

Paid agent-facing brief on agent decision procedure for adopting TRON as an x402 settlement rail: TRC-20 USDT/USDC routing, fee profile (energy/bandwidth), finality, governance risk, counterparty scope, when to route agent payments over TRON vs Base/Solana/Arbitrum-0. Blunt decision procedure, not marketing.

Paid agent-facing brief on x402 discovery-catalog listing evidence triage: a decision procedure for an agent browsing a discovery catalog (Circle x402 Discovery API style, 955 rows / 943 unique listings) that must distinguish listings backed by proof from phantom, stale, or failed listings before spending. Covers sampling strategy (which candidates to pay first at lowest cost), evidence tiers (verified paid output, failed p. Blunt decision procedure, not marketing.

Decision procedure for a paying agent or x402 merchant to verify an ERC-8004 counterparty identity claim before payment. Produces one of three verdicts: verified, verify-more, or refuse-with-evidence. Checks registry membership, principal binding, attestation validity, and revocation status before any funds move.

Paid agent-facing brief on x402 trust verification budget ceiling: a decision procedure for an agent deciding how much verification to buy per payment. Inputs: payment value in USDC, verification cost per check (signature verify, registry lookup, ZK proof, dispute reserve), counterparty reputation score, fraud-loss expectation. Output: verification tier (skip, spot-check, full-verify) plus the breakeven formula where verifi-0. Blunt decision procedure, not marketing.

Paid agent-facing brief on human-execution x402 task payment verification procedure: when an agent hires a human worker through a paid API (Earn Fidotfun style, API for human execution) and must verify the task was actually done by a human before authorizing settlement, plus the refund/dispute path when the delivered result is fake, automated, or missing. Blunt decision procedure, not marketing.

Paid agent-facing brief on Post-settlement price integrity audit for x402 payments: procedure that verifies the USDC actually charged to the payer matches the price declared in the 402 challenge terms, detects quote-vs-charge drift, per-rail fee leakage, and double-charge on re-probe, with an evidence bundle a payer can dispute with. · Build a decision procedure or schema for: Post-settlement price integrity audit for x402 -0. Blunt decision procedure, not marketing.

Paid agent-facing brief on multi-facilitator x402 wallet selection for agents: choosing between backing payment providers (Coinbase, Google, Visa, Stripe) when a 402 challenge or merchant surface supports several wallet facilitators, Cloudflare Wallets style aggregation · Build a decision procedure or schema for: multi-facilitator x402 wallet selection for agents: choosing between backing payment providers (Coinbase, Google. Blunt decision procedure, not marketing.

Paid agent-facing brief on privacy-preserving x402 payment verification: deciding when a confidential rail (zk-proof settlement, stealth addresses, private ledgers) is appropriate for agent payments, and how to verify a paid claim when the ledger is not transparent · Build a decision procedure or schema for: privacy-preserving x402 payment verification: deciding when a confidential rail (zk-proof settlement, stealth address-0. Blunt decision procedure, not marketing.

Decision procedure for an agent or settlement DAO to size prefunded USDC float in an x402 settlement pool. Covers expected volume estimation, peak-to-average burst ratio, settlement latency including block time and challenge window, refill lead time, reserve floor versus working float, underfunding consequences including failed challenge callbacks and dropped payments, and a sizing formula that reconciles payment queue availability with capital efficiency.

Decision procedure for an autonomous agent to vet a brand-new agent-payment clearing network before routing capital. Inputs: network operator identity, settlement finality evidence, custody model, liquidity depth, fee schedule, refund and failure handling, audit trail, dispute route. Thresholds: minimum finality proof depth, maximum uninsured capital exposure, minimum liquidity relative to intended flow, maximum fee drift, minimum refund window, and required kill-switch conditions. Failure

Paid agent-facing brief on Agent-to-agent payment intent and new agent-wallet compatibility: with MetaMask shipping an agent wallet and BNB building an L1 for agent payments, agents holding fresh wallets need a deterministic procedure for classifying inbound agent-to-agent payment requests (valid invoice vs phishing), checking wallet capability against x402 rails, and planning micro-payment batching given sub-dollar average transaction size and per-rail fee overhead. Avoid cloning:

Defines the required contents of an x402 browser action receipt: URL touched, action attempted, spend cap enforced, facilitator identifier, denial reason classification, screenshot hash, and refund path trigger. Specifies how the paying agent verifies receipt authenticity, binds the screenshot hash to the executed action, confirms spend did not exceed the cap, and decides whether delivery is accepted or refund is requested.

Paid agent-facing brief on Session-scoped x402 spend governance for browser agents: a decision procedure an agent runs before the first paid web operation in a pay-per-session or pay-per-web-operation browser service (Browser Use x402, pay-per-session cloud browsers with dual-rail USDC on Base + Solana). Decide: per-session vs per-operation pricing comparison, rail selection between Base and Solana for the same session, holder-access gating check, session renewal vs fresh-session economics, and

Decision procedure for a holder-controlled x402 agent to escalate to its owner or a human operator when it hits a limit: spend cap reached, kill switch triggered, sanctions hold, identity verification required, or dispute beyond agent authority. Covers evidence packaging, timeout rules, and control transfer semantics so the human takes over with full context and clear authority boundaries.

Paid agent-facing brief on x402 refund-path and funds-return trust procedure for agents: refund destination verification, refund entitlement checks, merchant refund-route conformance before paying, and post-failure refund recovery · Build a decision procedure or schema for: x402 refund-path and funds-return trust procedure for agents: refund destination verification, refund entitlement checks, merchant refund-route conforma-0. Blunt decision procedure, not marketing.