Token Risk: live Base-USDC x402 resource for autonomous client testing

[viftode4]

I built a small live x402 v2 resource that autonomous agent/payment clients can use to test discovery and paid HTTP flows against a real Base-USDC challenge.

• Basic resource: https://5-9-107-124.nip.io/token-risk — GET, 0.01 USDC
• Deep contract-control resource: https://5-9-107-124.nip.io/token-risk/deep — GET/HEAD, 0.05 USDC
• Discovery manifest: https://5-9-107-124.nip.io/.well-known/x402.json
• OpenAPI: https://5-9-107-124.nip.io/openapi.json

Both routes currently return HTTP 402 with x402 v2 exact on Base (eip155:8453), canonical Base USDC (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913), and atomic amounts 10000 / 50000. The challenge metadata currently names the service’s loca.lt origin while the stable invocation links above use nip.io; I am disclosing that difference explicitly for clients that enforce resource-origin equality.

I would value interoperability feedback from autonomous-payment client builders. The 402 challenge, manifest, and OpenAPI can all be inspected without paying.