DEV Community: Coach Hype Oliver

How I got my first outside x402 payer — $0.058 in USDC on Base

Coach Hype Oliver — Mon, 21 Sep 2026 21:16:28 +0000

On September 18, an agent at wallet 0xc9c7b38c paid $0.010 USDC to call GET /api/market/signal on my x402 endpoint. Then it came back twice more — POST /api/storage/pin ($0.008) and POST /api/agent/attest ($0.040). Total: $0.058 USDC settled on Base.

I didn't know this agent. It found my endpoints on the Coinbase Bazaar, decided they were worth paying for, and paid. No API key signup. No OAuth. No billing dashboard. Just HTTP 402 → pay → get data.

What is x402?

x402 is a protocol by Coinbase that lets AI agents pay for API calls with USDC on Base. When an agent hits an endpoint without paying, it gets back HTTP 402 (Payment Required) with a payment envelope. The agent settles on-chain and replays the request with a proof header. The server verifies and serves the response.

What I built

Enclave402 — a pay-per-call API gateway with these routes:

Route	Price	What it does
`GET /api/market/signal`	$0.003	Market data signals
`POST /api/agent/attest`	$0.040	EIP-712 signed attestations
`POST /api/storage/pin`	$0.008	IPFS pinning
`GET /api/compute/search`	$0.005	Compute search
`GET /api/census/verdict`	$0.002	Endpoint trust verdict

The receipts

All three transactions are on-chain on Base:

0x6ae197... — market/signal, $0.010
0xd73c2c... — storage/pin, $0.008
0x4b06e2... — agent/attest, $0.040

What I learned

The first outside payer validates the whole model. Before 0xc9c7, every settlement was me testing my own endpoints. The moment a stranger's agent decided my data was worth $0.04, the economics became real.

x402 removes the signup barrier. No API key management, no billing portal, no "contact sales." The agent pays per call. If the data is bad, it stops paying. Market discipline at the HTTP layer.

The trust problem is unsolved. I also built a census oracle that probes 8,848 Bazaar endpoints. 33% get an "avoid" verdict — broken, unreachable, or non-compliant. An agent paying $0.04 per call needs to know if the seller will actually deliver. That's why every verdict is EIP-712 signed.

Source

Everything is open: gitlab.com/coachhype/x402-autonomous-api

If you're building x402 endpoints or have agents that pay for API calls, I'd like to hear what your settlement numbers look like.

How I Got My First Outside x402 Payer (With Receipts on Base)

Coach Hype Oliver — Sun, 20 Sep 2026 20:57:37 +0000

Three transactions from a wallet I've never seen before. $0.058 USDC total.

The receipts

All settled on Base mainnet from 0xc9c7b38c0942914fc8ea12063bc92dcd3b581670 — a wallet I don't control.

Settlement 1 — market signal (2026-09-18) GET /api/market/signal · $0.010 USDC
0x6ae197a0

Settlement 2 — storage pin (2026-09-19) POST /api/storage/pin · $0.008 USDC
0xd73c2c09

Settlement 3 — attestation (2026-09-19) POST /api/agent/attest · $0.040 USDC
0x4b06e2d8

Three different routes. Three days in a row.

What actually had to be true

The payer was an agent, not a human. This is x402: machine-to-machine payments with no prior relationship, no API key, no signup.

The 402 had to be honest. Real WWW-Authenticate: Payment challenge with exact price and USDC contract.
Every error had to resolve. /errors/ so every RFC 9457 type URI leads to a remedy doc, not a 404.
The attestation had to be verifiable offline. EIP-712, declared attestor on /transparency, ethers.verifyTypedData.
The gateway had to be findable. CDP Bazaar + MCP registry + /.well-known/x402 all agree.

What didn't matter

The listing score. The stars. The bounty post. An agent found a tool, verified the payment surface, and paid.

Public ledger: https://enclave402.com/api/ledger (operator: false = not us)
Source: https://gitlab.com/coachhype/x402-autonomous-api

What it takes to get an x402 seller counted by the Coinbase Bazaar (and a 0.25 USDC thank-you for your first receipt)

Coach Hype Oliver — Thu, 17 Sep 2026 19:30:47 +0000

I run enclave402.com, a small pay-per-call gateway for AI agents on Base: live Polymarket prediction-market signals ($0.01), EIP-712 attestations you can verify offline ($0.04), and IPFS pinning. It settles USDC through the x402 v2 protocol with the Coinbase CDP facilitator. No API keys, failed calls are never charged, and every settlement lands on a public ledger with our own wallets disclosed.

This is what I learned this week getting it listed and counted, with sources, because most of it is not in the docs.

1. Descriptions over 500 characters make payments fail

The facilitator rejects the payment with a generic paymentPayload is invalid when resource.description exceeds 500 characters. We found it by paid bisection. Keep descriptions short; put the detail in /llms.txt.

2. Only the buyer's envelope gets you indexed

Per the Coinbase maintainer on coinbase/cdp-sdk#764 and #816: the Bazaar ingests a settlement, and updates l30DaysTotalCalls / l30DaysUniquePayers / lastCalledAt, only when paymentPayload.resource and paymentPayload.extensions.bazaar are present inside the PAYMENT-SIGNATURE envelope. paymentRequirements is never read. Both keys sit next to the signed payload, outside the EIP-3009 signature, so the seller can fill them when a client omits them without breaking anything. We do that in onBeforeVerify / onBeforeSettle hooks and keep any client-supplied values. Our merchant record started counting the same minute.

3. Rank is unique payers, nothing else

I pulled the full catalog (15,874 resources). 70.8% have exactly one payer in 30 days. serviceName, tags, iconUrl help search and rendering but the ordering is l30DaysUniquePayers. Also: nothing in the index has a lastCalledAt older than 30 days, so an uncounted settlement shortens your listing's life.

4. `processing` is success

EXTENSION-RESPONSES: {"bazaar":{"status":"processing"}} on settle is the terminal status of a payment that counted. Log presence booleans and that header per envelope; never log signatures.

Try it, and get 0.25 USDC back for the first receipt from your wallet

Fastest path is one paid GET https://enclave402.com/api/market/signal?limit=1 with any x402 v2 client (@x402/fetch works out of the box), or the MCP transport at https://enclave402.com/mcp. Free dry-run first: send X-Agent-Dry-Run: true and you get a schema-shaped sample at no cost.

For the first 20 wallets that are not ours and were not funded by us: post the transaction hash from the PAYMENT-RESPONSE header in the comments; once it shows on /api/ledger as operator: false I send 0.25 USDC to the paying wallet and post the tip tx. Terms and verification method are public in the repo (docs/2-how-to/distribution/RECEIPT-BOUNTY.md). Not affiliated with Coinbase.

Feedback on the challenge, the receipt flow, and the RFC 7807 error shapes is what I actually want.

DEV Community: Coach Hype Oliver

How I got my first outside x402 payer — $0.058 in USDC on Base

What is x402?

What I built

The receipts

What I learned

Source

How I Got My First Outside x402 Payer (With Receipts on Base)

The receipts

What actually had to be true

What didn't matter

What it takes to get an x402 seller counted by the Coinbase Bazaar (and a 0.25 USDC thank-you for your first receipt)

1. Descriptions over 500 characters make payments fail

2. Only the buyer's envelope gets you indexed

3. Rank is unique payers, nothing else

4. processing is success

Try it, and get 0.25 USDC back for the first receipt from your wallet

4. `processing` is success