FAQ
Below you'll find answers to the most common questions about how the API works, its use cases, supported features, and integration details.
How does the Glider API work?
You send a request with a smart contract address and chain ID. The API returns:
A set of detected risks
Overall trust score (0 to 100)
Proxy and verification metadata
Which blockchains are supported?
The Glider API supports smart contract analysis on multiple chains. See the full list here.
What is the Glider Trust Score?
It’s a numerical value from 0 to 100 representing the trust level of a contract:
100 = No detectable risks
Lower score = More or higher-severity risks
Any contract that hasn’t been verified has a 0 base score.
Each risk subtracts a fixed number of points based on severity (info, low, medium, high).
What kinds of risks does the API detect?
The API detects 15+ risks. See the full list here
Is proxy detection supported?
Yes. If a contract is a proxy, the API scans the underlying implementation and returns both proxy_address and implementation_address .
What does is_verified mean?
This flag tells you whether the smart contract is verified (i.e., the code is publicly visible on-chain). If false, the contract has no accessible source code and is considered untrustworthy.
How do I get access?
Contact the Hexens team to request your token.
Last updated