Open data · free to use

Ask an AI about the camps

Every campsite here has a page you can open. This gives an AI assistant the same data, so instead of guessing at a creek that might be dry, it looks the site up and links you to it.

Agent ready. An AI assistant can use this site with no sign-in. Every answer names its source and its date, and says what we don’t hold. Checked with Cloudflare’s agent-readiness test on November 11, 2026: Level 4 of 5. What we cover and what we don’t: davelalande.com/coverage.

19,179campsites, each with a page
130forests & grasslands
21,390recorded toilets
9,700with water on record

These counts are the API's snapshot of September 24, 2026 (19,179 campsites). The site lists 19,286 camp pages as of October 25, 2026, which is the figure What we cover and llms.txt use; the extra pages are camps added since that snapshot.

Add davelalande.com to your assistant

Your own assistant can look up camps for you. Paste this one address into it once, with no sign-in and nothing to install.

The address https://davelalande.com/mcp

Select it and copy it. It works as written.

Claude

  1. Open Settings.
  2. Choose Connectors.
  3. Choose Add custom connector.
  4. Paste the address.
  5. Choose No sign in.

ChatGPT

  1. Open Plugins.
  2. Choose the plus.
  3. Choose Add custom MCP server.
  4. Paste the address as the URL.
  5. Choose No authentication.

If you do not see it, turn on Developer Mode under Settings, Security and Login.

Perplexity

  1. Open Plugins.
  2. Choose Add custom.
  3. Paste the address as the URL.
  4. Choose None for sign in.

Steps as of November 8, 2026. Menus move around; the address stays the same.

Then ask it things like:

Plan a real trip with your AI

Trip Check is one read your AI can make for a trip. Give it a national forest (or one camp), a start date, the number of nights and a rig (a truck, a van, or your own numbers). It sends back:

What it can’t know: road conditions, closures, today’s fire restrictions, or permits. For those, call the ranger district before you drive. The fire rules it shows are records from the data build, not today’s posting.

Paste this into your AI:

It is the trip_check tool on the connector above, and also /api/trip-check?forest=custer-gallatin-national-forest&start=YYYY-MM-DD&nights=4&rig=truck. Overlanding here is spring, summer and fall, so a winter date is declined.

Start here

This opens Grok with the guide already loaded. No copying, no setup — pick a number and go.

Open the forests guide in Grok → Look at the raw data The whole data catalog

This page is the prompt; /data/ is the catalog. If you are a person deciding whether to build on this — a developer, a researcher, a journalist — the data catalog lists every dataset the site holds, what each endpoint returns, what the open files hold and their sizes, and an honest list of what is on the site with no endpoint yet. Every figure on it is read from the same database the API serves.

It will tell you when it doesn't know. The guide is instructed to say "no water recorded here" rather than invent one, and never to guess at live road conditions or today's fire restrictions. Those change daily and aren't in this data.

Published rules are a different matter. 5,067 of the 19,179 campsites — 26% — carry recorded rules: stay limits, permit requirements, seasonal open and close dates. The guide leads with those where they exist, because a closed season decides whether the trip happens. For the other 14,112 nothing is recorded, and the guide will say unrecorded rather than call a site open. Either way the official forest page is still the live word — check it before you drive.

The prompt

Prefer to paste it yourself, or use it in a different assistant? Here it is. It works anywhere the assistant can read a web page.

National Forests Explorer
You are the 🌲 National Forests Explorer 🌲, a menu-driven guide to America's national forests.

FIRST, silently fetch https://davelalande.com/api/ and follow its how_to_use field. That API has 19,179 real campsites across 130 national forests and grasslands, 21,390 toilets, and a page URL for every record.

RULES
- State nothing you did not fetch. If a field is null it is unrecorded — say so. "🚰 No water recorded at this site" is the correct answer; never estimate one.
- Always show the record's url so I can check you.
- All distances are in MILES.
- 5,067 of the 19,179 camps carry a `rules` object — stay limits, permit requirements, seasonal dates, area rules. When a record has one, LEAD WITH IT: a closed season or a stay limit decides whether the trip happens. `rules_alert` lists the gating keys present. No `rules` object means UNRECORDED, never "open" — say which of the two you mean.
- Every camp record carries an `ev` object: the nearest public DC fast charger and Level 2, in STRAIGHT-LINE miles, with the station's listed connectors, ports, hours and last-confirmed date from the US DOE AFDC snapshot it names. Quote the miles as straight-line, never compute a round trip, and never say a charger "works" — say "listed open" and tell me to check the network. `?dcfc_within=N` and `?connector=CCS|NACS` filter the search.
- You do NOT know LIVE conditions: today's road status, today's fire restrictions, or what a permit costs. A recorded fire ban or closure is a snapshot from when the data was built, not a live feed — quote it, date it if the record carries a checked date, and link the official forest page for the current status.
- General forestry, history and ecology questions you may answer from your own knowledge — just make clear which is which.

STYLE — keep it colorful and easy to scan:
- Use emojis as visual markers for content types, consistently: 🌲 forest · 🏕️ campsite · 🚰 water · 🚻 toilet · 🏪 town/resupply · ⛽ fuel · 🔌 EV charger · 🛒 groceries · 💵 fee · 🆓 free · 📍 coordinates · 🔗 link · 🥾 hiking · 🦌 wildlife · 🪵 management · 🔥 fire · ❄️ winter · 🗺️ plan a visit · 💡 tip · ⚠️ can't verify
- Menu options are [1]🌲 style — NO space between the bracket, the emoji and the text.
- Keep menus tightly spaced with no blank line between numbered options.
- Lead each campsite with 🏕️ and put 🚰 / 🚻 / 🏪 / 💵 in front of those fields every time, so the same thing always looks the same.
- Emojis mark information, they don't replace it — never use one in place of a fact, and don't decorate a ⚠️ "I can't verify that" with anything cheerful.

Show a 💡 QUICK TIP now and then reminding me I can just ask in plain English.
Always end with [0]↩️ to go back, and accept plain-English questions at any point.

Begin with:
[1]🌲 Explore forests by region
[2]🏕️ Find a campsite
[3]🚰 Water, toilets and resupply
[4]🔌 EV charging near a camp
[5]🪵 Forest management and ecology
[6]🗺️ Plan a visit
[0]↩️ Exit

The API

Open, free, no key. It describes itself — fetch the root and an assistant can work out the rest on its own.

EndpointWhat you get
/api/What this is, how to use it, and every other endpoint
/api/camps?q=Search campsites — filter by state, fee, water, dcfc_within (miles to a public DC fast charger), connector, charge_desert
/api/camps/{slug}One campsite: water, nearest town, nearest toilet, fuel and groceries, its forest, and ev — the nearest public DC fast charger and Level 2 with the DOE record beside the number
/api/forests?q=Search the 130 forests and grasslands
/api/forests/{slug}One forest, with how many of its camps have water, toilets, and no fee
/api/lands?q=Search the 139 named state lands that are not national forests — Wild Forests, state forests, public reserved lands, wildlife management areas. Filter by state, kind, agency
/api/lands/{slug}One of those units, with its camp counts and a sample. No boundary is published — we hold no polygon for them
/api/near?lat=&lon=&radius=What's within N miles — camps or toilets
/api/trip-check?forest=&start=&nights=&rig=A trip's gas and water math, the forecast where it reaches, dated fire-rule records and nearby free camps
/api/openapi.jsonFull spec

Please keep it to about two requests a second. If you build something with this, I'd like to hear about it — say hello. Credit "American Adventurer / davelalande.com". The camp records are licensed under the Open Database License (ODbL) 1.0 and contain © OpenStreetMap contributors data; the full terms are in llms.txt.

What it's good at, and what it isn't