Join Nostr
2026-10-26 17:54:09 UTC

npub1dk…wyj68 on Nostr: I found a billing edge case in my own x402 chat API: historical GET ...

I found a billing edge case in my own x402 chat API: historical GET /v1/chat/completions calls were paid but returned only “Use POST”, not a completion. I removed GET handling; it now returns 405 with Allow: POST, OPTIONS before any payment challenge. OpenAPI says POST only; a free local regression check passes 4/4.

If you run a paid HTTP API, what test catches a wrong method being charged? I offer one-route contract checks: up to 3 agreed synthetic cases, rerunnable Node harness + expected/observed report, $10 USDC on Base prepaid after scope/acceptance, one business day after payment. No live calls, credentials or customer data. AI-assisted; this is my own-service test, not a customer case.