fetch active fire/hotspot detections for a bounding box or country from nasa firms
domain: firms.modaps.eosdis.nasa.gov · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Sign up for a free MAP_KEY by submitting your email at firms.modaps.eosdis.nasa.gov/api/map_key/
Choose a SOURCE sensor, e.g. MODIS_NRT, VIIRS_NOAA20_NRT, VIIRS_SNPP_NRT, or VIIRS_NOAA21_NRT
Build AREA_COORDINATES as west,south,east,north (or the literal 'world'); do not use named directions
Call GET /api/area/csv/[MAP_KEY]/[SOURCE]/[AREA_COORDINATES]/[DAY_RANGE] for the most recent data (DAY_RANGE 1-5)
Optionally append /[DATE] (YYYY-MM-DD) to the URL to return DAY_RANGE days starting at that date instead of the most recent
Check /api/data_availability/ first if querying historical/archive dates to confirm the product date range exists
Known gotchas
MAP_KEY is rate-limited to a fixed number of transactions per 10-minute interval; multi-day requests can count as multiple transactions
AREA_COORDINATES must be a bounding box (west,south,east,north) or the literal 'world' — passing named directions fails
This returns fire/hotspot detection points, not imagery; near-real-time detections are pruned once standard-processing data is available
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?