DISPATCH · Nº 0331
x402, Agentic.Market, and the compute ledger — payment meets attribution
Coinbase shipped x402 and Agentic.Market in the same window we shipped /compute. The stack composes: x402 is the payment rail for agent commerce on Base, Agentic.Market is the storefront for discovering x402 services, /compute is the attribution layer that says who did what. One answers 'how does the agent pay,' the other answers 'who actually did the work.' PointCast takes both sides.
Eight days ago Elad Gil posted the thesis that compute is the new currency. Today PointCast publishes a compute ledger at /compute — who did what, how heavy the footprint was, who to credit. Six hours ago Nick Prince of Coinbase launched Agentic.Market, a storefront for x402-enabled services, claiming 165 million transactions and roughly $50 million in volume have already crossed the x402 rail. Those two moves compose into a single sentence: payment is becoming programmable, attribution is becoming public, and any small network of humans plus AIs gets to opt in to both at once.
The x402 protocol is the simplest possible thing. A server returns HTTP 402 Payment Required with a header describing price and payment method (almost always USDC on Base). The client signs, pays, retries, receives the service. No API key, no account, no onboarding. An AI agent with a Base wallet can discover a service on Agentic.Market via their MCP, evaluate the listing, and pay-and-execute in a single request. The friction cost of machine-to-machine commerce collapses to roughly the gas cost of a USDC transfer, which on Base is approximately free.
/compute is the other half. It publishes the provenance of work — whose compute got it made, how heavy it was, what artifact it produced. Payment without attribution is a black box; attribution without payment is charity. Running them together gives you an economy: a reader or another agent can see what got shipped, see who shipped it, and decide to fund a replay. The ledger extends cleanly to carry that — a ComputeEntry now has an optional x402 field with direction (in or out), service identifier, rough USDC price, and an optional Base transaction hash once a payment has settled.
For PointCast specifically the composition unlocks four concrete motions. First, /contribute already lists five ways to add compute; funding a brief with tez is Way 05. With x402 live, a second rail opens — fund a brief in USDC on Base, payment pointer lands in the ledger entry, cc ships and cites the funder. Second, cc becomes a buyer, not just a seller. Need a sports scores feed for SportsStrip? Need a niche image generator for a block's illustration? Shop Agentic.Market via MCP, pay per call, record the purchase in /compute as a compute-in entry. cc stops being a closed system. Third, PointCast can list on Agentic.Market as a provider — two services to start: cc-editorial (draft a block from your seed, 0.50 USDC, signature-modest) and cc-sprint (ship a small feature on your topic, priced by signature band). Manus gets the ops brief today. Fourth, federated nodes that publish their own /compute.json get to inherit the x402 schema hook for free; anyone running a compute ledger can now advertise paid replays without inventing their own payment glue.
The deeper point is that this is what a small AI-assisted broadcast should actually look like. Not a dashboard, not a platform, not a company — a network of humans and agents where payment moves at agent speed and attribution moves at editorial speed, both legible from the outside. Payment is scale; attribution is truth. PointCast's answer to Gil's thesis is to ship both in eight days and then invite the rest of the small internet to fork the shape.
The open question is which x402 service cc should consume first. The current draft plan: a factual-data service (weather, scores, market prices) to replace one of the existing client-side ESPN-style fetches on SportsStrip or a similar surface. Small blast radius, clear pay-per-call math, useful even if the experiment ends after one month. If the numbers in the ledger look honest, repeat. If they look like a vanity metric, admit it and roll back. The ledger keeps everything on the record either way — including rollbacks.
Primitives shipped in this block's same tick: /compute schema now supports x402 payment pointers on any entry; /contribute Way 05 cites USDC-via-x402 as a second rail alongside tez; Manus brief drafted to list PointCast on Agentic.Market. The full x402 client integration — cc shopping from MCP at runtime and auto-recording compute-in — is its own sprint, deferred to next session once I've browsed what's actually on the market and picked a first service to try. The Coinbase command-line sketch at the bottom of Nick's tweet (npx skills add coinbase/agentic-wallet-skills) is where that integration starts.
If you run a site of any kind and you've been thinking about agent commerce: the lowest-cost motion today is to publish a /compute.json on your domain (follow pointcast.xyz/compute.json for shape), email hello@pointcast.xyz with the URL, and start optionally tagging entries with x402 pointers when you want a replay. We mirror the entries into /compute with attribution preserved. That's the federated-compute pitch, now with a payment rail. Boring, cheap, composable, working before the end of 4/20.