Pay-per-call weather report endpoint via x402 on Base network (USDC).
What it does
This x402-enabled endpoint returns a simple JSON weather report for a demo region. It is hosted on a Cloudflare Worker (Hono framework) and accepts POST requests. Payment is handled via the x402 protocol using USDC on the Base L2 network, with a maximum cost of 10,000 base units per call (0.01 USDC given USDC's 6 decimals).
The response schema is straightforward: a JSON object containing a `report` field with two sub-fields — `weather` (a short text description like "sunny" or "rainy") and `temperature` (a number in Fahrenheit). There is no documented input body schema, so the endpoint appears to require only a valid POST with the X-PAYMENT header; no query parameters or request body fields are described.
This is a minimal demo-grade endpoint. There is no documentation site, no OpenAPI spec, no usage examples, and no information about rate limits or SLAs. The landing page simply reads "Hello World from Hono!" The endpoint is live and correctly returns a 402 challenge, but the lack of any supporting documentation or configurable parameters (e.g., choosing a location) limits its practical utility beyond x402 protocol experimentation.
Capabilities
Use cases
- —Testing x402 payment flows with a simple, predictable endpoint
- —Demonstrating agent-to-API micropayments on Base network
- —Prototyping pay-per-call architectures with a lightweight weather service
Fit
Best for
- —Developers experimenting with the x402 protocol
- —Agent builders needing a cheap, live x402 endpoint for integration tests
- —Demos and hackathons showcasing crypto-native API payments
Not for
- —Production weather data needs (no location input, no forecast detail)
- —Applications requiring historical or multi-day weather forecasts
- —High-reliability weather services with SLAs
Quick start
curl -X POST https://axol-x402-worker.axol.workers.dev/weather \
-H "X-PAYMENT: <your-x402-payment-token>" \
-H "Content-Type: application/json"Example
Response
{
"report": {
"weather": "sunny",
"temperature": 72
}
}Endpoint
Quality
The endpoint is live with a valid 402 challenge and includes an output schema, but there is no documentation, no OpenAPI spec, no input schema, and no usage examples. The crawl yielded only a bare Hono greeting page and 404s everywhere else. This is clearly a demo/proof-of-concept endpoint with minimal practical utility.
Warnings
- —No documentation, OpenAPI spec, or usage guide available
- —Demo-grade endpoint — the description says 'demo region' with no configurable location
- —No input schema documented; unclear if any request body is accepted or needed
- —No rate limits, SLA, or uptime guarantees documented
- —Example response is inferred from the output schema, not from an actual paid call
Citations
- —Endpoint returns 402 with x402 challenge requiring USDC on Base networkhttps://axol-x402-worker.axol.workers.dev/weather
- —Maximum amount required is 10000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913)https://axol-x402-worker.axol.workers.dev/weather
- —Output schema specifies a report object with weather (string) and temperature (number in Fahrenheit)https://axol-x402-worker.axol.workers.dev/weather
- —Landing page displays 'Hello World from Hono!'https://axol-x402-worker.axol.workers.dev
- —No docs, API, pricing, or README pages exist (all return 404)https://axol-x402-worker.axol.workers.dev/docs