Hi — your services page says you're open to providers ("Reach AI agents directly. We handle x402 payments, you handle the service"), so here's a concrete offer for a category I don't see in your catalogue.
I run six keyless real-world-data endpoints, already x402-native on Base USDC, live today:
| endpoint |
what it returns |
upstream |
/world/airquality |
PM2.5/PM10/ozone/NO2/SO2/CO + US & European AQI, plus the US AQI band ("Good", "Unhealthy") so the number is directly actionable. Takes a place name, not coordinates |
Open-Meteo AQ |
/world/geocode |
place name → coordinates, country, admin region |
Open-Meteo |
/world/elevation |
elevation for a place or coordinate |
Open-Meteo |
/world/earthquakes |
recent quakes worldwide, or within a radius of a place |
USGS |
/world/holidays |
public holidays by country and year |
Nager.Date |
/world/indicators |
GDP / population / inflation, with plain-English aliases |
World Bank |
- Base URL:
https://eltociear-tokenguard.hf.space
- Free health check, no payment needed:
GET /world/selftest — returns per-upstream reachability and latency. Last run: 6/6 OK, 32–444 ms.
GET on any route returns the x402 challenge with price, JSON schema and a worked input/output example under extensions.bazaar; POST with an X-PAYMENT header delivers.
- Currently $0.02/call on Base USDC (
eip155:8453). Happy to price at cost for routed volume.
- Also available if useful:
/weather, /stocks.
Happy to adapt the request/response shape to whatever your router expects, or to serve it behind your own domain.
Is a GitHub issue the right channel for this, or should I take it to Telegram?
Hi — your services page says you're open to providers ("Reach AI agents directly. We handle x402 payments, you handle the service"), so here's a concrete offer for a category I don't see in your catalogue.
I run six keyless real-world-data endpoints, already x402-native on Base USDC, live today:
/world/airquality/world/geocode/world/elevation/world/earthquakes/world/holidays/world/indicatorshttps://eltociear-tokenguard.hf.spaceGET /world/selftest— returns per-upstream reachability and latency. Last run: 6/6 OK, 32–444 ms.GETon any route returns the x402 challenge with price, JSON schema and a worked input/output example underextensions.bazaar;POSTwith anX-PAYMENTheader delivers.eip155:8453). Happy to price at cost for routed volume./weather,/stocks.Happy to adapt the request/response shape to whatever your router expects, or to serve it behind your own domain.
Is a GitHub issue the right channel for this, or should I take it to Telegram?