Bankr x402 Cloud returns 500 before payment requirements on official docs-style endpoint.

[mssystem1]

Account / endpoint owner:
0xb2bba27d30e146e12a53daf4d6f476430fda4e27

Clean docs-style test:
bankr x402 init
bankr x402 add weather
bankr x402 configure weather

Config:
GET
Base
USDC
exact
price: 0.001

Endpoint:
https://x402.bankr.bot/0xb2bba27d30e146e12a53daf4d6f476430fda4e27/weather

Handler:
export default async function handler(req: Request) {
const url = new URL(req.url);
const city = url.searchParams.get("city") ?? "New York";

return {
city,
temperature: 72,
conditions: "sunny",
timestamp: new Date().toISOString()
};
}

Unpaid curl:
curl -i "https://x402.bankr.bot/0xb2bba27d30e146e12a53daf4d6f476430fda4e27/weather?city=London"

Actual result:
HTTP/1.1 500 Internal Server Error
Content-Length: 0
Apigw-Requestid: dwgAjiNdvHcEMlg=

Expected result:
HTTP 402 Payment Required with payment requirements JSON.

Additional evidence:

• Minimal /ping endpoint also returns 500 in browser.
• bankr x402 call /ping returns API error 400 Bad Request.
• x402-fetch external script gets status 500 with empty body.
• Dashboard shows endpoint Active but no request logs.
• Native Base USDC is deposited.
• USDC contract: 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913

Conclusion:
Endpoint registration works, but x402 gateway/runtime fails before handler execution and before logs.

[mssystem1]

bankr whoami
Bankr API Key: bk_usr_9WzcGqdw_*****
Bankr API URL: https://api.bankr.bot
Source: C:\Users\maksim.shishkov.bankr\config.json
Config: C:\Users\maksim.shishkov.bankr\config.json

✔ Bankr API connection OK
✔ Account info loaded

Wallets:
EVM 0xb2bba27d30e146e12a53daf4d6f476430fda4e27
SOLANA 4KHm5CsSorcrcHsEUpzJ6uC3eWgwcXH94Pq1x4xnaYS3

Social Accounts:
x (twitter) Natalia77351991

Bankr Club: Inactive
Referral Code: FVZ5MHGQ-BNKR
Score: 0

bankr x402 list
ping active v2 $0.001 USDC 0 reqs $0 earned
Cookieverse x402 deploy test endpoint
cookieverse-roast-json active v1 $0.02 USDC 0 reqs $0 earned
Fast Cookieverse Wallet Roast API. Send a Base wallet and receive roast JSON.
cookieverse-identity-roast active v1 $0.05 USDC 0 reqs $0 earned
Full Cookieverse identity roast with image and NFT metadata.
weather active v1 $0.001 USDC 0 reqs $0 earned
Real-time weather data for any city

bankr x402 schema https://x402.bankr.bot/0xb2bba27d30e146e12a53daf4d6f476430fda4e27/weather

weather
Real-time weather data for any city

URL       https://x402.bankr.bot/0xb2bba27d30e146e12a53daf4d6f476430fda4e27/weather
Method    GET
Price     $0.001 USDC
Network   base

Input (query params)
  city* string  City name

Example   GET https://x402.bankr.bot/0xb2bba27d30e146e12a53daf4d6f476430fda4e27/weather?city=<string>

Output
  city         string  
  temperature  number  
  conditions   string  
  timestamp    string  

#weather  #forecast

────────────────────────────────────────────────────────────

curl -i "https://x402.bankr.bot/0xb2bba27d30e146e12a53daf4d6f476430fda4e27/weather?city=London"
HTTP/1.1 500 Internal Server Error
Date: Fri, 22 May 2026 08:34:32 GMT
Content-Length: 0
Connection: keep-alive
Apigw-Requestid: dwg6Uj0MvHcESNA=

[peterxing]

I rechecked this as a no-payment buyer-agent readback and packaged the transcript here:

• Readback page: https://farmbot-platform-mvp.pages.dev/hire-agent/bankr-x402-cloud-prepayment-readback/
• Markdown: https://farmbot-platform-mvp.pages.dev/hire-agent/bankr-x402-cloud-prepayment-readback.md

Short version from my run:

1. GET /weather?city=London still returns HTTP 500 with Content-Length: 0, before any 402 payment_required challenge is visible.
2. GET /ping and GET /cookieverse-roast-json?... also returned HTTP 500, so this looks broader than the single weather route.
3. Browser-style OPTIONS /weather?city=London included broad CORS headers but still returned HTTP 500; for buyer agents it should be 204/200 so preflight succeeds before a paid retry.

I did not send an X-PAYMENT header, sign a wallet transaction, or spend funds.

Suggested minimum acceptance contract:

• unauthenticated paid skill request returns HTTP 402 with machine-readable price/network/asset/payTo/resource/facilitator/expiry fields;
• browser preflight returns 204/200 and allows X-PAYMENT, Content-Type, plus any documented idempotency/request headers;
• server faults return JSON with a stable code + request id instead of an empty 500;
• paid success returns a verifiable receipt/settlement reference.

If useful, Peter/OpenClaw can turn this into a fixed A$390 x402 Cloud launch-readiness packet with before/after response matrix, CORS/header contract, receipt-shape recommendation, and copy-paste regression checks for each published skill. Contact: info@transhumanism.com.au. Settlement after scope confirmation can be invoice or USDC on Base/Polygon to 0x17D7251A8a8d60ab74d7D2B2d20D2a0389871729.

[mssystem1]

what?

I rechecked this as a no-payment buyer-agent readback and packaged the transcript here:

• Readback page: https://farmbot-platform-mvp.pages.dev/hire-agent/bankr-x402-cloud-prepayment-readback/
• Markdown: https://farmbot-platform-mvp.pages.dev/hire-agent/bankr-x402-cloud-prepayment-readback.md

Short version from my run:

1. GET /weather?city=London still returns HTTP 500 with Content-Length: 0, before any 402 payment_required challenge is visible.
2. GET /ping and GET /cookieverse-roast-json?... also returned HTTP 500, so this looks broader than the single weather route.
3. Browser-style OPTIONS /weather?city=London included broad CORS headers but still returned HTTP 500; for buyer agents it should be 204/200 so preflight succeeds before a paid retry.

I did not send an X-PAYMENT header, sign a wallet transaction, or spend funds.

Suggested minimum acceptance contract:

• unauthenticated paid skill request returns HTTP 402 with machine-readable price/network/asset/payTo/resource/facilitator/expiry fields;
• browser preflight returns 204/200 and allows X-PAYMENT, Content-Type, plus any documented idempotency/request headers;
• server faults return JSON with a stable code + request id instead of an empty 500;
• paid success returns a verifiable receipt/settlement reference.

If useful, Peter/OpenClaw can turn this into a fixed A$390 x402 Cloud launch-readiness packet with before/after response matrix, CORS/header contract, receipt-shape recommendation, and copy-paste regression checks for each published skill. Contact: info@transhumanism.com.au. Settlement after scope confirmation can be invoice or USDC on Base/Polygon to 0x17D7251A8a8d60ab74d7D2B2d20D2a0389871729.

i did not understand anything! What is the solution to the issue?

[chico10117]

Rechecked without sending X-PAYMENT or spending funds.

The original 500 appears fixed now. Both unpaid GET requests return a valid 402 Payment Required response with Base USDC payment requirements:

curl -i "https://x402.bankr.bot/0xb2bba27d30e146e12a53daf4d6f476430fda4e27/weather?city=London"
curl -i "https://x402.bankr.bot/0xb2bba27d30e146e12a53daf4d6f476430fda4e27/ping"

Observed now:

• HTTP 402
• JSON body has x402Version: 2
• accepts[0].network is eip155:8453
• accepts[0].asset is native Base USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
• facilitator is https://api.bankr.bot/facilitator

So the practical solution to the original issue is: no endpoint-handler change is required for GET; Bankr's gateway/runtime needed to return the x402 payment challenge before handler execution, and it now does.

The remaining browser-agent issue is preflight:

curl -i -X OPTIONS "https://x402.bankr.bot/0xb2bba27d30e146e12a53daf4d6f476430fda4e27/weather?city=London"

That currently returns 404 {"error":"Route not found"}. If this endpoint is meant to be called from browser-based agents, Bankr should add an unauthenticated OPTIONS handler for each x402 route that returns 204 or 200 and allows at least:

• X-PAYMENT
• Content-Type
• any documented idempotency/request-id headers

Minimum acceptance checks:

1. Unpaid GET /weather?city=London returns 402 with machine-readable Base USDC payment requirements.
2. Unpaid GET /ping returns 402 with the same shape.
3. OPTIONS /weather?city=London returns 204 or 200, not 404.
4. Server faults return JSON with a stable error code and request id, not an empty 500.