Connect the assistant to travel tools
Internal tools retrieve hotels, attractions and interesting places from the travel database. DeepSeek, accessed through OpenRouter, powers the assistant; ElevenLabs provides the voice experience.
The assistant needed to answer travel questions inside an existing client app, using our travel database and app knowledge. It also needed to work in both text and voice, respect access permissions and use only the user context explicitly provided by the application.
Internal tools retrieve hotels, attractions and interesting places from the travel database. DeepSeek, accessed through OpenRouter, powers the assistant; ElevenLabs provides the voice experience.
The app supplies the user data that the assistant may use. The agent does not independently retrieve user data. This keeps that boundary in the application’s control.
OpenAI moderation checks messages, while usage limits and access permissions control use of the assistant. These controls were part of the production implementation alongside the conversational experience.
The assistant is live in the client’s production app. Users can choose text or voice to ask travel-related questions, supported by database tools and the context the application explicitly provides.
Client identity and application details are kept private. The visual above is a simplified architecture illustration.
WHAT I TAKE FORWARD“The conversation is only one part of a production assistant.”