# Glossary

## ApiKey

When you call the RelationONE Api, you need to add `ApiKey` in the http Header.

The ApiKey is used to authenticate the application making the request.

The following ApiKey sample is for testing purposes only(NOT for the production environment): 581c6c4fa0b54912b00088aa563342a4.

If you need to use an ApiKey for production, please refer to this form:

{% embed url="<https://docs.google.com/forms/d/1B38ferfackqnLuPUlWr5Pc2bvrK8C1M3TI5wwiw4Kxo>" %}

## Rate Limits

The request frequency

## addressAuthToken

Some Api need to add the `I-Authorization: ${addressAuthToken}` in the http header to identify the user identity.

You can get it from the following Api:

{% content-ref url="/pages/WDuQvvuvh4bhYMyrinOB" %}
[Signature](/relation-one-api/api/signature.md)
{% endcontent-ref %}

## unifiedAuthToken

Some Api need to add the `Authorization: ${unifiedAuthToken}` in the http header to identify the user identity.

You can get it from the following API:

{% content-ref url="/pages/EtBm2PRS1n30Bshu60Go" %}
[Auth](/relation-one-api/api/auth.md)
{% 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://relationlabs.gitbook.io/relation-one-api/guide/glossary.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.