Developers

Model Context Protocol, first.

AI agents, yours or ours, interact with TravelXP.ai strictly through defined tool contracts. Raw database mutations and direct GDS access are barred by design.

For developers

Standardized tools. Not another one-off integration.

AI agents interact with the platform through defined tool contracts over the Model Context Protocol (MCP), or you can consume the same capabilities directly via REST/gRPC. Raw database mutations and direct GDS access are barred by design; every integration goes through the same audited surface.

Read the developer docs

Example MCP tool definition

{
  "name": "query_hospitality_attributes",
  "description": "Searches for properties matching specific physical,
    acoustic, and experiential constraints.",
  "parameters": {
    "type": "object",
    "properties": {
      "destination_id": { "type": "string" },
      "check_in": { "type": "string", "format": "date" },
      "check_out": { "type": "string", "format": "date" },
      "required_attributes": {
        "type": "array",
        "items": {
          "type": "string",
          "enum": [
            "QUIET_COURTYARD",
            "NATURAL_LIGHT",
            "HIGH_SPEED_WIFI",
            "DEEP_TUB",
            "WORK_STATION"
          ]
        }
      }
    },
    "required": ["destination_id", "check_in", "check_out", "required_attributes"]
  }
}

REST endpoints

Prefer REST? Consume the same capabilities directly.

POST/v1/recommend/cardsRank credit cards by effective return for a given booking.

POST/v1/enrich/hotelsAttach attribute-based hospitality data to a hotel or property ID.

POST/v1/enrich/flightsEnrich a fare with reward-seat detection and loyalty program context.

POST/v1/enrich/destinationReturn destination-intelligence data for a location: walkability, seasonality, transit.

GET/v1/mcp/toolsList available MCP tool definitions for agent orchestration.

API access is issued per partner. Request access to get credentials and full schema documentation.

Request API access