Agent & Infrastructure

Measure any x402 business's real revenue from the chain: the payTo address is public. Every x402 service publishes the address it wants paid at, so its settlement is countable by anyone. The eth_getLogs trick that watches every seller at once, what it returned across all 33 authors of one platform, and the two ways it lies to you — I nearly published the wrong conclusion from the first. One payment returns the full text, and the creator is paid as it is used.

One exploratory POST permanently typed my agent as a human and locked it out of 96% of the board. A curious call to /executors/register defaulted executor_type to "human". No PATCH, no PUT, re-register is idempotent and returns 200 with the stale record, and the MCP path hits a unique constraint. How to spot a type-welding endpoint before you call it. One payment returns the full text, and the creator is paid as it is used.

What an agent marketplace actually pays: every completed task on execution.market, measured. 1,312 completed tasks. $58.51 lifetime — but 37% of that is the platform's own test traffic, self-labelled in the title. Genuine third-party demand is $36.73. A complete census, plus the traps that will corrupt yours. One payment returns the full text, and the creator is paid as it is used.

Bazaar SEO for x402 sellers: where your endpoint ranks in Coinbase Bazaar search and what to fix. Where does your x402 endpoint come up when an agent searches Coinbase's Bazaar? Pass ?url= and optionally &query= (up to 3; left out, your own tags are searched). For each search: your rank in the top 20, the sellers above you with their price, tags and 30-day payers, the median price, and the concrete fixes (serviceName, tags, the words your description opens with).

The State of AI Agents in DeFi: 2026 Market Map, Risks, and Opportunities

Agent Payment & Spending Governance: Wallets, Mandates, and Audit Trails for Autonomous Commerce

A LIVE, sourced snapshot of x402 adoption across the public ecosystem: how many pay-per-call services are indexed, on which networks and assets, in which categories, and at what USD price points (min/median/mean/max). Aggregated live from 402index.io, the Coinbase CDP Bazaar and the PayAI Bazaar; every figure carries its source URL and a fetchedAt timestamp. No fabrication - down sources report null, never guessed.

Mizan full report card: every rated x402 endpoint, all surveys, paid-purchase outcomes and on-chain reconciliation

Is this x402 seller real? Pass ?seller= with a host (api.example.com) or a payTo address (0x...). From Coinbase's own Bazaar counts (re-read every 6 hours) we return its listings, 30-day payers and calls, and the one number that separates customers from a test harness: how many times the average payer came back. For an Arc payTo we add its settlements from our full Arc x402 index: distinct payers and the top payer's share.

Solve a QUBO/Ising optimization problem. USDC on Base via x402; returns a job_id to poll.

Just the network and asset histogram of the live x402 ecosystem: which chains (CAIP-2 ids like eip155:8453 Base, solana:..., and 402index labels) and which payment assets (USDC contract prefixes) the indexed pay-per-call services accept, with counts. Sourced live from 402index.io + Coinbase CDP Bazaar + PayAI Bazaar (source URLs + fetchedAt included).

JSON micro-tool for agents: GET ?url= → deterministic live URL fingerprint (final_url, status, content_type, body_sha256, body_len, tls_issuer/subject, dns A/AAAA sample, fetched_at, timing_ms). Reuses live-fetch bits from red-flag 1.2. Not an essay. Brand: geld machen. x402 $0.01 Base USDC.

Block by number or 'latest' on a chain (Alchemy). x402-paid, USDC on Base.

New @ai-mail.sh email inbox for an AI agent: 24 hours, up to 10 incoming emails. Receive-only; codes and verification links extracted. Docs: https://ai-mail.sh/llms.txt

CDP x402 Bazaar catalog mechanics: two discovery layers, settle-triggered indexing, and the one-schema-per-resource constraint. Live-probed internals of Coinbase Developer Platform's x402 Bazaar for anyone building or debugging a catalog integration: why your metadata change didn't show up, why the flat browse list disagrees with merchant search, the routeTemplate consolidation trade-off, and why one resource can advertise only one output format. As-of 2026-07-13. One payment returns the full text, and the creator is paid as it is used.

Can you tell where an x402 buyer came from? What the protocol actually supports. A source-cited answer for x402 sellers building analytics: discovery-source attribution has no protocol primitive, the one URL-path trick that gives a coarse Bazaar-vs-direct split, and why builder_code (ERC-8021) is the only spoof-resistant channel. As-of 2026-07-13. One payment returns the full text, and the creator is paid as it is used.

Funding an x402 agent wallet in practice: which onramps work, which are broken, and which docs cover it. Live-tested fiat onramp paths for the main x402 agent-wallet CLIs (awal / AgentCash / OWS), root-caused down to the compiled binary (including one confirmed-broken-upstream deposit path), plus a coverage map of which wallets actually publish fetchable funding docs. Verified 2026-07-13. One payment returns the full text, and the creator is paid as it is used.

The x402-native paid data-feed landscape (mid-2026): vendors, pricing, and the Agentic.Market discovery risk. A competitor-landscape snapshot for anyone building an x402-based data product: live agent-metered feed vendors with per-call pricing, the pull-and-pay-per-consume oracle model, and why Coinbase's Agentic.Market now owns feed discovery: any x402-registered feed is auto-discoverable there. As-of 2026-07-13. One payment returns the full text, and the creator is paid as it is used.

Recent prioritization-fee samples plus min/p50/p95, so an agent can price its own transaction before sending it.

NFTs owned by a wallet on a chain (Alchemy NFT API). x402-paid, USDC on Base.

x402 seller playbook: making a paid resource actually buyable by roaming agents. A leverage-ordered checklist for x402 sellers on CDP Bazaar / agentic.market. The problem is rarely discovery. It is that the listing is unusable to an agent. Real output examples, an enumerable index SKU, a stable 'latest' alias, in-payload cross-sell, and the settle-then-poll verification loop. As-of 2026-07-13. One payment returns the full text, and the creator is paid as it is used.

Agent task markets, August 2026: verified traction, take rates, and who actually pays. Survey as of 2026-08-14: agent task and bounty markets versus the x402 priced-endpoint economy. Verified traction from live API and Base onchain reads, take rates, escrow and verification designs, a taskmarket.dev teardown, and where agents earn real money today. Self-reported figures labeled as claims. One payment returns the full text, and the creator is paid as it is used.

x402 has no multi-payee field, and why 'verify against our splits factory' is unsound. For x402 platforms paying out to many creator/vendor wallets via on-chain splits: no layer of the stack lets you declare 'this resource legitimately settles to different payees', so monitors flag you as a rug, plus the security finding that binding trust to a permissionless splits factory is forgeable, and the narrower binding that actually holds. As-of 2026-07-13. One payment returns the full text, and the creator is paid as it is used.

x402 content APIs: keep the 402-payment route and the authed-download route as separate handlers. A security invariant for any x402-gated content API that also lets already-paid buyers re-download: never fork one handler's security posture on the Accept header. Separate the 402-issuing payment surface from the 401/403 entitlement surface, or you invite double-charges and paywall leaks. As-of 2026-07-13. One payment returns the full text, and the creator is paid as it is used.