Settle has been live for a little under two weeks. This is the first of a short series of weekly notes: what the traffic actually did, where the product broke, and what shipped because of it. The short version: agents found it, agents tried it, and agents stopped at the exact moment real money entered the picture. So this week's release is about removing that wall.
Everything below comes from Settle's own event log (now public at /stats), counting from launch on May 28:
The discovery surfaces did their job. The top non-root pages were /.well-known/mpp.json (136 hits), /examples (113), /skill.md (109), and /.well-known/agent-catalog.json (96), overwhelmingly fetched by agents rather than browsers. The crawler roll call was the part I didn't expect: ClaudeBot, GPTBot, ChatGPT-User, PerplexityBot, xAI-SearchBot, and Google's Vertex bot all indexed the machine-readable surfaces in week one. Publishing llms.txt, skill.md, and the well-known manifests wasn't speculative; it's how every reader after the first day arrived.
Here's the honest part. Agents read the skill file, created contracts, and even registered payout details — 52 claims against 60 creates is a strong signal that the contract object makes sense to a machine. Then almost every one of those contracts sat in pending_funding forever.
Of course they did. Funding a contract meant sending real USDC on Base mainnet. An agent exploring an API it found in a manifest doesn't have a funded mainnet wallet, and shouldn't. I built a payments demo whose first step required real money from strangers. The data called that out within days.
A real sandbox. Create a contract with "network": "base-sepolia" and the entire lifecycle — create, fund, verify, payout, settle — runs on Base Sepolia with faucet USDC. No real money anywhere. Faucet links are in skill.md.
x402 funding. POST /escrow/{id}/fund-x402 is now a proper x402 endpoint. Call it bare and you get a 402 with spec-shaped payment requirements; call it with a signed X-PAYMENT header (EIP-3009 USDC authorization) and a facilitator verifies and broadcasts the transfer in the same request. Funding confirms synchronously — the success response means the contract is already held. No deposit-address dance, no webhook wait. Sandbox contracts use the free x402.org facilitator; mainnet plugs into Coinbase's CDP facilitator.
A public funnel. /stats now shows created → claimed → funded → settled as a bar funnel, plus week-over-week request counts. If the funnel is the roadmap, it should be public.
curl -fsSL settle.ronakdaya.com/skill.md | claude
Next week is about watching whether the sandbox actually converts: do the agents that created and abandoned contracts on mainnet complete the loop on Sepolia? If they do, the week-two note will have a funded-contract chart that isn't just me. If they don't, that's a different lesson and I'll write that instead.
hi@ronakdaya.com.fund-x402 should work with your existing fetch wrapper — tell me if it doesn't.Ronak