Set up RIDB API access for an application and understand its rate limits and data-quality quirks before going to production.
domain: ridb.recreation.gov · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create a recreation.gov account, then generate an API key from the RIDB portal and accept the API Access Agreement.
Pass the key as the apikey header (not a query parameter) on every request to https://ridb.recreation.gov/api/v1/.
Contact ridbsupport@nsitellc.com for access issues, key resets, or questions about the access agreement.
Load-test conservatively against the documented throttle (reported around 50 requests/minute) and add retry/backoff for 429 responses.
Validate a sample of returned records against the live recreation.gov site, since bulk RIDB data can lag or diverge from what's actually bookable.
Known gotchas
The access agreement forbids sharing your key or reselling API access to third parties — build key management accordingly.
RIDB is a data catalog, not a booking engine: it will not create, hold, or cancel a reservation — real-time booking still routes through recreation.gov's own reservation system.
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?