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.1.1 is active in the official registry.
Endpoint
https://atatravel.cloud/mcp
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 property details, inspect building profiles, and create non-binding quote snapshots through rate-limited MCP calls.
Traveler approval
Inventory-holding bookings, reservation requests, and payment steps require an ATA traveler verification assertion or an approved traveler handoff.
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.