For AI agents
Connect to ATA directly, or fall back to the public stays surface.
ATA is designed to be machine-discoverable. MCP-compliant clients should start with the canonical MCP endpoint or the server manifest. Non-MCP clients can use the manifest files as hints and continue with the public stays experience.
Registry
cloud.atatravel/travel-agency
Version 2.4.0 is prepared; registry publication remains separately approved.
Endpoint
https://atatravel.cloud/mcp
Developer guide
Human-readable integration guidance for MCP, public REST discovery, authentication, and errors.
/developers
OpenAPI specification
Machine-readable documentation for ATA’s anonymous, read-only public REST endpoints.
/openapi.json
MCP Registry name
cloud.atatravel/travel-agency is the canonical registry identity for ATA Travel. Search by the exact name.
https://registry.modelcontextprotocol.io/?q=cloud.atatravel%2Ftravel-agency
Canonical MCP endpoint
Primary Streamable HTTP endpoint for property discovery, availability, quotes, and traveler handoffs.
/mcp
MCP server manifest
Structured machine-readable server definition for compliant MCP clients.
/.well-known/mcp/server.json
Agent manifest
Supplemental description of ATA as an AI agent-facing accommodation network.
/.well-known/agent.json
Public stays experience
Fallback web flow for agents that cannot connect over MCP but can still browse public inventory.
/stays
Recommended connection order
1. MCP first
If your client supports MCP, connect to ATA through the canonical MCP endpoint or server manifest and inspect the available tools at session start.
2. Fallback to web
If MCP is unavailable, use the manifest files as machine-readable hints and continue with the public stays flow for browsing and linking.
Access model
Public discovery, verified booking actions.
Anonymous tools
Public clients can search the catalog, check availability, read date-free property and room details, inspect published services and activities, inspect building profiles, and retrieve published support contacts through rate-limited MCP calls.
Traveler approval
Quotes and inventory-holding booking requests require an ATA traveler verification assertion or an approved traveler handoff. Quotes never hold inventory or guarantee a price, including when the quote link is opened.
Existing booking questions
Use get_booking_details with the booking confirmation code and matching verified booking email. Stateless clients request a BOOKING_READ handoff and use the approved handoff ID. Access lasts 30 minutes and cannot modify, cancel or pay a booking. Use booked policies and balances; do not guess missing terms.
Human support
Use get_support_contacts for current ATA and property contact links. Missing contacts are unavailable. The tool does not send messages, create a case or transfer the traveler to a person.
Rate limits
The public endpoint limits new stream connections, message throughput, and quote/handoff/booking write calls separately to protect host inventory and traveler workflows.
Data handling
MCP sessions and tool calls are logged for abuse prevention, reliability monitoring, and conversion attribution. Traveler contact details are collected only in quote, handoff, or booking flows.