> For the complete documentation index, see [llms.txt](https://docs.dexlab.space/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dexlab.space/developer-hub/token-and-swap-apis/api-key-issuance-guide.md).

# API Key Issuance Guide

Issuing an API key increases the default RPS (Requests Per Second) limit. When requesting an API key, please provide your estimated call volume, and we will determine an appropriate rate limit accordingly.

However, in general cases, the API provides sufficient speed and limits (2 RPS) even without an API key.<br>

Please submit the form via [`Dexlab API Key Request`](https://forms.gle/pnuAjVNsM8Mm6LSg7)

Provide details about your intended use and expected request limits.

After review, we will issue the API key to the requested email as soon as possible.

{% hint style="info" %}
For the Pro API, the x-api-key header must always be included in every request.
{% endhint %}

**Headers**

* Open API: `https://open-api.dexlab.space/`
  * *There is a rate limit of 2 RPS. If you need more, get a free API key.*
* Pro API( API key required ): `https://pro-api.dexlab.space/`
  * *The rate limit is increased and free.*

| Name         | Value              |
| ------------ | ------------------ |
| Content-Type | `application/json` |
| x-api-key    | `your api key`     |

*The Pro API functions the same as the standard API, except for differences in the header and endpoint.*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dexlab.space/developer-hub/token-and-swap-apis/api-key-issuance-guide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.