Install only what you need
Each connector exposes its own tools through MCP. The host reports which connectors are installed and enabled, and Relay respects that configuration on every request. Installing Shopping does not install Flights or grant access to another connector.
A journey continues into another connector only when that connector is connected and authorized. See the integration guide for the installation contract.
Keep the choice in context
Results carry the information needed to make a decision: the option, provider, price basis, availability, freshness and next step. Missing information remains unknown. A starting price, selected offer and confirmed booking have different meanings.
Preserve the issued selection and returned context when comparing or continuing. Refresh expired results before relying on a price or availability.
Hand the next step to the assistant
Relay prepares the selected option and relevant context for the assistant to continue using its own tools. The user also has the option to open the provider destination directly.
Provider policy observations are advisory information. The assistant controls browser continuation under its own security and user-approval rules. Relay's connector credentials and API permissions apply to requests made through Relay.
The connector reference explains the returned handoff fields and supported capabilities. A prepared handoff remains distinct from a provider-confirmed transaction.
Connect a journey
Carry relevant destinations, dates, airports and party size into the next connected service. The host decides when to continue and shares only the information needed for that request.
A journey proposal does not search or book by itself. The target connector runs only after the host invokes it. See Carry a journey forward.
Keep access and data scoped
Keep Relay credentials on the host's server and out of prompts, public pages and logs. Use opaque session identifiers and preserve the ownership of returned selections.
Search and handoff preparation do not require provider passwords, payment-card details or the user's full conversation history. See the Privacy Policy and integration guide for data handling and recovery requirements.