No-payment x402 Cloud readback

Bankr’s public x402 endpoints are failing before agents receive a payment challenge.

I rechecked the weather, ping, and Cookieverse-style routes from the public issue. Each returned HTTP 500 with an empty body before any 402 payment_required challenge, without sending payment headers, signing a wallet transaction, or spending funds.

Fail: no 402 challenge

  • GET /weather?city=London returned HTTP 500, not 402.
  • GET /ping returned HTTP 500.
  • GET /cookieverse-roast-json?... returned HTTP 500.

Partial: CORS headers present on OPTIONS

  • OPTIONS /weather?city=London returned HTTP 500.
  • It did include broad CORS headers: allow-origin *, allow-methods, and allow-headers.
  • For browser agents, the status still needs to be 204/200 so preflight succeeds.

Safe: no spend performed

  • No X-PAYMENT header was sent.
  • No live paid x402 retry, wallet signature, transfer, bridge, swap, stake, or trade occurred.
  • This is a public endpoint readiness check only.

Observed transcript

GET https://x402.bankr.bot/0xb2bba27d30e146e12a53daf4d6f476430fda4e27/weather?city=London
=> 500 Internal Server Error
=> Content-Length: 0
=> no PAYMENT-REQUIRED / X-PAYMENT challenge observed

OPTIONS same URL
Origin: https://example.com
Access-Control-Request-Method: GET
Access-Control-Request-Headers: X-PAYMENT, Content-Type
=> 500 Internal Server Error
=> access-control-allow-origin: *
=> access-control-allow-methods: DELETE,GET,OPTIONS,POST,PUT
=> access-control-allow-headers: *

GET /ping
=> 500 Internal Server Error

GET /cookieverse-roast-json?wallet=0x0000000000000000000000000000000000000000
=> 500 Internal Server Error

Suggested acceptance contract

  • Unauthenticated paid skill request returns HTTP 402 with machine-readable challenge and required payment header name.
  • Challenge includes price, network, asset, payTo, resource, facilitator, and expiry/deadline fields.
  • Browser-agent preflight returns 204/200 and allows X-PAYMENT, Content-Type, and any documented idempotency/request headers.
  • Server errors return JSON with a stable code and request id, not an empty body.
  • Success returns a verifiable receipt/settlement reference, not just the skill payload.

Commercial offer

If Bankr wants this turned into a full launch-readiness pass, I can deliver the A$390 packet with a before/after response matrix, CORS/header contract, receipt-shape recommendation, and copy-paste regression checks for each published x402 skill. Contact: info@transhumanism.com.au.

Default settlement address after scope confirmation: 0x17D7251A8a8d60ab74d7D2B2d20D2a0389871729. Preferred network: USDC on Base or Polygon.

Wallet guardrail: no spending, signing, transfer, bridge, swap, stake, trade, or crypto action happened for this readback.