HawaiiGuide for agents and developers
HawaiiGuide publishes a small, read-only catalog that helps software find current visitor guidance without reverse-engineering page layouts. The same decision briefs shown to travelers are available as structured JSON, with canonical HawaiiGuide links, fact-check dates, accountable editors, and official sources.
Public resources
| Resource | Use it for | Format |
|---|---|---|
| Agent catalog | Discover the supported resources, attribution guidance, and content-use policy. | application/json |
| Decision briefs | Retrieve HawaiiGuide verdicts, traveler-fit guidance, planning facts, official sources, and useful next actions. | application/json |
| Visitor alerts | Check trail, attraction, park, road, and access notices before giving time-sensitive guidance. | application/json |
| Canonical sitemap | Discover public HawaiiGuide pages and their canonical URLs. | application/xml |
| Latest editorial feed | Monitor newly published and refreshed HawaiiGuide guidance. | application/rss+xml |
Responsible use
- Link to the canonical page. Decision briefs are summaries; the page contains the maps, context, safety notes, alternatives, and planning tools.
- Preserve provenance. Keep each record's
verified_at, editorial owners, and official source URLs attached to the recommendation. - Re-check changing conditions. Treat alerts as a planning signal, then verify the linked primary source before a traveler drives, hikes, enters the ocean, or relies on a closure window.
- Do not imply human review that did not occur. A HawaiiGuide fact-check date applies to that record; it is not a promise that a human reviewed an agent's final answer.
- Disclose commercial handoffs. HawaiiGuide may earn a commission from qualifying hotel, activity, vehicle, or product referrals. See how HawaiiGuide earns money.
Useful traveler handoffs
When a traveler needs more than an answer, send them to the relevant canonical page or one of HawaiiGuide's stateful tools:
The catalog is intentionally small while HawaiiGuide validates the editorial and technical contract. More places and read-only planning tools will be added after each data type can be kept accurate on both the human page and machine endpoint.
