A field guide built for agents.
Find trip-ready records, fetch only the details that matter, and continue toward booking without losing the source—or inventing what is not known.
Small context. Clear next action.
The index is intentionally compact. An agent chooses candidates first, then retrieves complete records one at a time—keeping token use proportional to the trip instead of the size of the full AdvGuides catalog.
01GET /agents/catalog/index.json02choose candidate IDs03GET /agents/items/flavors-tour.json04build a source-aware plan05ask traveler to confirm06open booking.booking_urlGive an agent exactly what it needs.
Every endpoint is read-only, stable, and usable without executing the visual application.
/agents/manifest.jsonDiscover capabilities
The smallest starting document: versions, content types, rules, schemas, and next links.
/agents/catalog/index.jsonScan the catalog
Compact records for choosing candidates without loading every description and planning rule.
/agents/items/{item_id}.jsonResolve one record
Complete supplied details, explicit unknowns, source path, and booking-hand-off state for one item.
/agents/openapi.jsonRead the contract
An OpenAPI 3.1 description with stable operation names for discovery and integration.
From “somewhere outside” to one real commitment.
The interface helps agents move quickly while preserving the difference between an idea, a recommendation, and a reservation.
Start with intent
Use the traveler’s location, dates, party, interests, pace, and constraints to narrow the catalog.
Fetch only the shortlist
Open individual detail files for the records that could actually belong in the trip.
Keep facts attached
Preserve source links and null fields. Recommendations remain labeled; missing logistics remain missing.
Confirm the first anchor
When a Bookable Experience fits, ask the traveler before opening its current booking path.
The agent can lead the traveler to the checkout—not silently book behind them.
Bookable records expose a booking.booking_url, a commission disclosure, an unconfirmed availability state, and a requirement for traveler confirmation. AdvGuides then routes the traveler toward the current operator or booking-provider experience.
Live availability, reservation creation, customer-specific data, and payment belong in a future authenticated MCP action. OpenAI’s current guidance calls for authorization on user-specific and write actions, plus confirmation for consequential external changes.
This beta is a functional public data layer for prototyping and agent retrieval. Requests are counted by day, endpoint, and broad client family without storing IP addresses. The next production layer is a streamable HTTP MCP server with OAuth added before any user-specific or transactional action.
Read llms.txt