The aggregation layer unifies access to our entire bridge network through an API and UI. When developers submit requests through our API or SDK, the system broadcasts these intents to integrated bridges. Our quote aggregator collects and compares responses, automatically selecting optimal routes based on cost, speed, and reliability. In the Metalayer Beta, reducing cost for users is the top priority.

​
Architecture

Aggregation Layer

​
UI

The UI for the aggregation layer provides a user-friendly interface for end-users to interact with the Metalayer’s bridge network. It allows users to:
  • Explore available routes: Users can browse through various bridging routes, each with detailed information on costs, speeds, and reliability metrics.
  • Select preferred routes: Users can choose routes based on their specific needs, such as prioritizing lower costs or faster transaction times.
  • Track transaction progress: Users can monitor the status of their cross-chain transactions in real-time, with access to detailed logs and notifications for any issues or updates.
  • Personalize settings: Users can adjust their preferences for route selection, including setting specific thresholds for acceptable cost and speed.
Developers have the ability to fully whitelabel the UI for their own usage, as well as for applications within their ecosystem. This ensures a seamless integration and consistent user experience across different platforms. The UI is designed to be intuitive, providing a seamless experience for both novice and experienced users.

​
Routing API

The Routing API is a powerful tool that enables developers to programmatically access the aggregation layer’s functionalities. Key features include:
  • Submit intents: Developers can submit cross-chain intents through the API, specifying parameters such as source and destination chains, asset types, and desired outcomes.
  • Retrieve quotes: The API provides real-time quotes from integrated bridges, allowing developers to compare options based on cost, speed, and reliability.
  • Execute transactions: Once a route is selected, the API facilitates the execution of the transaction, ensuring secure and efficient cross-chain transfers.
  • Receive notifications: Developers can set up webhooks or callbacks to receive updates on transaction status, ensuring they are informed of any changes or issues.
The Routing API is designed to be flexible and scalable, supporting a wide range of use cases and integration scenarios.