Building a Multi-Agent Travel Planner with Storacha

Authored by the Protocol Labs Dev Guild team that created TripMate.

Trip planning is often a mess — tabs open everywhere, dates clashing in chats, and itineraries buried in emails. We built TripMate to fix that. It’s a multi-agent AI travel planner that works like your personal assistant, handling everything from finding flights to organizing plans and even getting feedback from friends and family. It’s built on top of Storacha, which gives it a decentralized edge.

Glance at our Tripmate Demo Video to have a comprehensive outlook.

Smart Agents at Work

TripMate uses three smart agents that communicate behind the scenes to simplify your travel planning:

• Planner Agent: Lives on Telegram. It chats with you, remembers your preferences, and utilises the STORAGE_UPLOAD action from ElizaOS-Plugin to upload your trip data on Storacha besides conveying it to Finder Agent.
• Finder Agent: Handles live search. It finds flights, hotels, and trains based on your request using various travel APIs. Redirects the searched insights to Planner Agent.
• Share Agent: Retrieves your uploaded trip data from Storacha by utilising STORAGE_RETRIEVE action of ElizaOS-Plugin, summarises it gracefully and helps you share your plan with others and collect feedback. Send your itinerary to friends and get suggestions easily.

Building with Storacha

At the core of our system is Storacha, which we use to store all travel data with security and durability. Built on Filecoin and IPFS, Storacha ensures that all data is content-addressed and immutable. This means your data can’t be changed without your knowledge, and it’s always available — no need to rely on a central server– ensuring data integrity.

Process & Purpose

We used the ElizaOS plugin to connect with Storacha. Using the w3 CLI tool, creating an account, and integrating the plugin to handle our trip data came with its own set of challenges. When we saw the “Storage Client is initialized” message, it felt like a major win. We then managed to upload and retrieve data while ensuring everything remained modular and efficient. Ultimately, our TripMate project became the first to use the console.network space on Storacha via the ElizaOS Plugin.

Once connected, we used Storacha to:

• Store user trip data with content IDs (CIDs)
• Fetch past plans based on those CIDs
• Keep everything tamper-proof and persistent (and fire-proof too 😀)

Implementation Highlights

The integration utilizes the Storacha plugin, a middleware solution that bridges Tripmate’s core systems with the Storacha decentralized storage network. This plugin is designed to facilitate:

Data Transfer and Storage: The plugin enables seamless data transfer to the Storacha network, leveraging the capabilities of IPFS and Filecoin for decentralized storage. While the plugin itself does not handle encryption, it is designed to integrate with the Storacha client library (web3-storage/w3up-client), which is in the process of being integrated with the Lit Protocol for encryption support.

Trustless Verification and Auditing: Each data write operation is recorded on the Storacha network using Content Identifiers (CIDs), ensuring a transparent and traceable audit trail for all stored content. This data can be retrieved via a trustless gateway, providing secure and verifiable access without relying on a centralized authority.

Decentralized Data Management: The plugin supports data management, allowing for easy sharing and retrieval of data across multiple agents using content identifiers (CIDs).

Building for a Better Travel Experience

This setup gave us exactly what we needed — fast data access, reliability, and a solid foundation to scale as more users join. At the end of the day, our goal is to build something people would actually enjoy using. TripMate handles the mess of travel planning, saves the data, provides insightful plans, and yes — roasts one’s indecisiveness along the way. Thanks to Storacha and the amazing team behind it, TripMate is durable, secure, and ready to take off.