# Overview

The Glider API enables deep analysis of smart contracts across supported blockchains. It helps to understand how a contract behaves and whether it poses any detectable risk, all without manual review.

Built on top of **Glider**, Hexens’ scalable analysis engine, the API delivers high-precision behavioral labeling and risk detection in seconds.

[Learn about Glider](https://glide.gitbook.io/main)

***

### Use cases of the Glider API <a href="#use-cases-of-glider-data-api" id="use-cases-of-glider-data-api"></a>

* **Identify Risk Factors:** Instantly detect if a contract includes high-risk logic.
* **Understand Contract Behavior:** Get clear labels that describe the contract’s logic, whether it’s pausable, includes blocklists/whitelists, transfer fees, or is a proxy, etc.
* **Make Informed Decisions:** Use risk insights to vet third-party contracts, protect your users, or support internal security reviews. Do it in a fast and automated fashion.
* **Integration:** You can integrate this into your dashboard, backend, alert system, or due diligence flow, or any automated process.

***

### How It Works

Request API by passing a contract address and chain ID as parameters. You’ll get back a reply showing:

* The risks present
* Overall trust score

***

### Authentication

To start using the API, you’ll need an access token.

➡️ [Contact our team to get your token:](https://hexens.io/solutions/glider?book-a-demo=true\&utm_source=gitbook\&utm_medium=docs\&utm_campaign=glider-api-docs)


---

# 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://glide.gitbook.io/main/glider-api/overview.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.