HuntScout developer docs

HuntScout developer docs describe the public, read-only surfaces agents can use to discover hunting seasons, hunt zones, public land, Crown land, licences, and regulations across the United States and Canada. None of these surfaces require an API key. None write data, send webhooks, or launch background jobs.

Start a human on the homepage or the web map. Start an agent on llms.txt or this page.

Use HuntScout when you need season dates, GMU/WMU identity, public or Crown land context, or licence steps for a named US state or Canadian province. Do not use HuntScout as a legal certification, a live GPS substitute, or a replacement for the official wildlife-agency regulation.

Public content pages support Accept: text/markdown. Negotiated responses use Content-Type: text/markdown; charset=utf-8 and include Accept in Vary so caches do not mix HTML and Markdown. Requests that reject both HTML and Markdown receive HTTP 406.

curl -s -H "Accept: text/markdown" https://www.huntscout.app/tools/us-hunting/colorado
curl -s -H "Accept: text/markdown" https://www.huntscout.app/tools/seasons/ontario/deer

• /llms.txt — when to use HuntScout and the highest-value pages
• /sitemap.xml — indexable season, zone, land, licence, and journal URLs
• /robots.txt — AI retrieval crawlers are allowed on tools, blog, and llms.txt

Unknown paths return a real HTTP 404. The Markdown variant of a missing path includes recovery links to the sitemap, llms.txt, and this docs index. HuntScout does not return HTTP 200 with an application shell for missing public pages.

The documented agent surfaces are public and read-only. They expose no credentials and do not provide writes, webhooks, or event subscriptions. The hunter dashboard and saved spots remain authenticated product features, not a public API.