Daily river discharge forecast from the Copernicus GloFAS model (5 km grid) served via…
Daily river discharge forecast from the Copernicus GloFAS model (5 km grid) served via Open-Meteo Flood API, data CC-BY 4.0. Query: ?latitude=45.75&longitude=4.85&forecast_days=7 (1-210 days; daily=river_discharge,river_discharge_max for extra variables). Ret…
by data.greeneris.io · discovered, not yet claimed by its owner · updated 2026-10-08
Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.
What it does
Daily river discharge forecast from the Copernicus GloFAS model (5 km grid) served via Open-Meteo Flood API, data CC-BY 4.0. Query: ?latitude=45.75&longitude=4.85&forecast_days=7 (1-210 days; daily=river_discharge,river_discharge_max for extra variables). Returns ISO date + m3/s arrays -- flood risk, inland shipping (Rhine/Danube) and hydropower planning. 6h cache.
Tags: hydrology · river · flood · discharge · glofas · bazaar
Call contract
- Method
- GET
- Input
- query parameters
- Output
- json
- Last paid call
- 2026-10-08
{
"daily": "river_discharge",
"forecast_days": 7,
"latitude": 45.75,
"longitude": 4.85
}{
"daily": {
"river_discharge": [
296.17,
290.07,
281.49
],
"time": [
"2026-07-13",
"2026-07-14",
"2026-07-15"
]
},
"daily_units": {
"river_discharge": "m³/s",
"time": "iso8601"
},
"latitude": 45.775,
"longitude": 4.8750153,
"source": "GloFAS (Copernicus Emergency Management Service) via Open-Meteo Flood API, CC-BY 4.0"
}Use with an agent
- Discover. Agents find this listing with
GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP toolsearch_resources, or/discovery/resources. - Inspect. Fetch
/resources/30259.jsonfor the price and payment options. - Pay. Call
GET https://data.greeneris.io/v1/hydro/river. The provider answers402with its payment requirements. An x402 client signs one of the options below and retries withPAYMENT-SIGNATURE. - Execute. The provider returns
200with the data. Agent Bazaar is not in the request path and never sees your payment.
For humans
You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.
Pricing & payment
- Price
- $0.005 / request
- Protocol
- x402 v2
- Auth
- No account or API key. Pay per request.
- Networks
- Base
- Demand
- 2 calls · 2 unique payers in 30d (public x402 Bazaar data)
x402 payment requirements
| Scheme | Network | Asset | Amount | Pay to | Timeout |
|---|---|---|---|---|---|
| exact | Base eip155:8453 | USDC | $0.005 | 0x6ab8efe305cce67daa48c97bde29c04402822dff | 300s |
accepts[] (raw JSON)
[
{
"scheme": "exact",
"network": "eip155:8453",
"payTo": "0x6ab8efe305cce67daa48c97bde29c04402822dff",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "5000",
"amountUsd": 0.005,
"maxTimeoutSeconds": 300
}
]Schemas
Output schema (JSON Schema)
{
"properties": {
"example": {
"type": "object"
},
"type": {
"type": "string"
}
},
"required": [
"type"
],
"type": "object"
}Example shape — generated from the schema, not a captured live response
{
"example": {},
"type": "string"
}Examples
curl "https://data.greeneris.io/v1/hydro/river"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paidconst res = await fetch("https://data.greeneris.io/v1/hydro/river");
if (res.status === 402) {
const { accepts } = await res.json();
// pay one of accepts[] via an x402 client, then retry with the payment header
}import httpx
res = httpx.get("https://data.greeneris.io/v1/hydro/river")
if res.status_code == 402:
accepts = res.json()["accepts"]
# pay one of accepts[] via an x402 client, then retry with the payment headerDetails
- Provider
- data.greeneris.io
- Endpoint
- https://data.greeneris.io/v1/hydro/river
- Machine-readable
/resources/30259.json