# Introduction

### Liquid Terminal API

The API implements a comprehensive multi-level rate limiting system to protect against abuse and ensure fair usage across all endpoints. The system uses Redis for distributed counting and provides granular control over request frequency.

### Rate Limit Configuration

#### Multi-Level Limits

The system implements three distinct rate limiting tiers:

| Tier         | Window        | Max Requests    | Purpose                                         |
| ------------ | ------------- | --------------- | ----------------------------------------------- |
| Burst Limit  | 1 second      | 20 requests     | Prevents sudden traffic spikes                  |
| Minute Limit | 60 seconds    | 1,200 requests  | Controls medium-term usage (20 req/sec average) |
| Hour Limit   | 3,600 seconds | 72,000 requests | Prevents long-term abuse (20 req/sec average)   |

Front end stack

* Next JS
* Tailwing
* TypeScript
* ShaDCN

Back end stack:

* NodeJs (Express)
* Typescript
* Postgres
* Prisma

API used:

* HyperLiquid
* HypurrScan
* DefiLlama


---

# 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://liquid-terminal.gitbook.io/liquid-terminal/liquid-api/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.