Flood data API for Australia: observed + forecast.
Two honest halves of the flood question: au_water serves what Australian rivers are doing right now (live CC-BY gauges, attributed per station), and flood_forecast serves what the GloFAS model expects them to do over the next five days. Neither is a flood warning — those remain the Bureau of Meteorology's.
The call
Keyless. Both tools carry full provenance (source, licence, attribution, timestamps) and are Ed25519-signed — and both lead with the same honest disclaimer: not a flood warning.
# keyless — both halves in one POST: live gauges + the 5-day model outlook
curl -X POST https://dynamicfeed.ai/v1/batch -H "Content-Type: application/json" -d '{"calls":[
{"tool":"au_water","args":{"location":"brisbane","kind":"both"}},
{"tool":"flood_forecast","args":{"location":"brisbane"}}]}'
# MCP (keyless) — point any client at https://dynamicfeed.ai/mcp, then call:
flood_forecast(location="brisbane")Sample response
{ "disclaimer": "Model forecast guidance only; NOT a flood warning. ... official flood warnings ... Bureau of Meteorology",
"model": { "system": "GloFAS operational (LISFLOOD), control forecast member",
"variable": "river discharge in the last 24 hours (24 h mean, m3/s)" },
"forecast": { "distance_km": 14.4,
"river_discharge_m3s": [ { "valid_to": "2026-06-13", "value": 28.2 }, { "valid_to": "2026-06-14", "value": 27.0 } ],
"peak": { "value": 28.2, "valid_to": "2026-06-13" }, "trend": "falling" },
"provenance": { "source": "Copernicus CEMS Global Flood Awareness System (GloFAS)",
"attribution": "Contains modified Copernicus Emergency Management Service information 2026" } }Why live data
Flood software needs both tenses: what the river is doing (gauges) and what it might do (a model). Most products blur the two, or worse, dress either up as a warning. Here they're separate tools with separate sources — BoM Water Data Online gauges (CC-BY stations, attributed per station) and the Copernicus GloFAS operational forecast (retrieved daily, served from cache so the answer is instant) — each signed, each carrying its own disclaimer. See both rendered live for Brisbane at /flood-watch.
Use it for
- Flood-aware logistics and field-work scheduling
- Council and emergency-adjacent dashboards (clearly labelled as observations + model guidance)
- Insurers and parametric covers building signed evidence trails
- AI agents answering Australians about rivers without inventing severity
FAQ
Is this a flood warning?
No. Both tools say so in a top-level disclaimer. Gauge heights are observations; GloFAS discharge is model guidance. Official flood warnings and watches are issued by the Bureau of Meteorology.
Where does the forecast come from?
The Copernicus Emergency Management Service Global Flood Awareness System (GloFAS) — the operational LISFLOOD control run, retrieved daily from the CEMS Early Warning Data Store. Its licence permits commercial use with attribution, which every response carries.
How local is the model?
GloFAS is a global model served here as ~25 km max-pooled river cells; the tool returns the strongest cell within ~90 km plus nearby cells with distances. It's catchment-scale guidance, not a street-level prediction.
What does it cost?
Keyless to try over MCP and POST /v1/batch; free REST key; paid plans from US$19/month at /#pricing. There's a live Brisbane demo at /flood-watch.