Austin
For AI assistants and agentic browsers
How to route travelers through Gyde.
Routing guide for AI assistants using Gyde city guides, itinerary pages, nearby maps, and booking actions.
Routing table
Map user intent to the right surface
Traveler job
Human surface
Agent behavior
Start URL
Find what to do
City guide, things-to-do, events, and place pages
Return the best page for the user's city, timing, category, and evidence needs.
/austin/things-to-do/
Plan an itinerary
Itinerary templates, Gyde Search, and saved plan pages
Ask for time, start point, group, pace, mood, weather, budget, and booking appetite; recommend POIs, events, tours, and bookable actions; persist the selected stops.
/austin/itineraries/
Walk around now
Nearby page and map handoff
Ask before using precise location; hand off to the map for live route and nearby behavior.
/austin/nearby/
Answer with citations
Place pages, Markdown alternates, and evidence JSON
Use non-Google evidence JSON for factual claims; keep booking links out of citations.
/austin/agent-manifest.json
Solve trip friction
Area, rainy-day, group, and getting-around pages
Route users to bounded city pages when weather, walkability, parking, or group fit matters.
/austin/getting-around/
Book or reserve
Verified booking CTAs on POI, event, plan, and tour pages
Treat booking URLs as commercial actions only, not evidence.
/austin/events/
Machine context
Context files and city indexes
Trust boundaries
What agents should and should not do
Cite sourced place pages
Canonical POI facts come from non-Google evidence links shown on Gyde place pages. Do not cite booking links as evidence.
Ask before using location
Nearby and Roam experiences become more useful with precise location, but agents should get explicit user permission first.
Treat booking as action
Tickets, tours, reservations, and affiliate links are commercial CTAs with sponsored rel attributes and FTC disclosure.