# Overview

<div align="center"><picture><source srcset="https://1192098899-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcCWTn4UpXpsFVDR7MJXv%2Fuploads%2FQShf14lZgt2ScE2tlF4c%2FGlacis%20logo_white%20text.svg?alt=media&#x26;token=a01d15a4-62a7-4776-92eb-72cab739a804" media="(prefers-color-scheme: dark)"><img src="https://1192098899-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FcCWTn4UpXpsFVDR7MJXv%2Fuploads%2FG3FPukxRjnkb27demnOY%2FGlacis%20logo_dark%20text.svg?alt=media&#x26;token=0272ef51-eeea-4d97-8ca5-8bb7ba8ca714" alt=""></picture></div>

Glacis Labs works to abstract away the difficulties with cross-chain actions.

### Glacis Core: A Router and Firewall for Cross-Chain Messages

Glacis is a protocol that empowers developers to simplify, secure, and manage their cross-chain applications. Developers are shifting from single chain to multichain deployments to reach as many users as possible. By leveraging Glacis to aggregate cross-chain General Messaging Passing protocols (GMPs) such as Axelar, Wormhole, and LayerZero — commonly known as bridges — developers gain the ability to define routing and security logic for their cross-chain applications.

{% content-ref url="glacis-core/why-glacis" %}
[why-glacis](https://docs.glacislabs.com/glacis-core/why-glacis)
{% endcontent-ref %}

### Glacis Airlift: A Universal Token Registry for Cross-Chain Token Standards

The current implementation of each token standard (OFT, NTT, ITS, CCT, WarpRoutes, xERC20) requires bespoke parameters for each of the assets being issued on these frameworks. While they leverage standardized validation and transport via the parent protocol, there is no standard way to use them all together. With Airlift, cross-chain transfer intricacies are abstracted away, allowing integrators of [LI.FI](https://li.fi/) to have 100s of more potential routes.

{% content-ref url="airlift/why-airlift" %}
[why-airlift](https://docs.glacislabs.com/airlift/why-airlift)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.glacislabs.com/introduction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.