# Getting Started

## API Overview

| Item               | Value                    |
| ------------------ | ------------------------ |
| **Base URL**       | `https://api.odinbot.io` |
| **API key header** | `x-api-key`              |

All request and response bodies are JSON unless stated otherwise.

## Getting your API key

1. Sign in to OdinBot and open **Settings**.

<figure><img src="/files/Z2LsRiybAOFq9BMexklY" alt="" width="563"><figcaption></figcaption></figure>

2. Click **Manage API keys**.

<figure><img src="/files/LRU35Sp3n3GuFkaufrtT" alt="" width="563"><figcaption></figcaption></figure>

3. In the pop-up, choose **+ Create a new API key**.

<figure><img src="/files/IZ8mF7Qj6uULRZl9q3OB" alt="" width="563"><figcaption></figcaption></figure>

4. Copy the key that appears and store it in a safe place.

<figure><img src="/files/V3f0UuIxLsHjNiEpF9HK" alt="" width="563"><figcaption></figcaption></figure>

## How to revoke access to your API key

1. From OdinBot's interface open **Settings**.

<figure><img src="/files/Z2LsRiybAOFq9BMexklY" alt="" width="563"><figcaption></figcaption></figure>

2. Click **Manage API keys**.

<figure><img src="/files/LRU35Sp3n3GuFkaufrtT" alt="" width="563"><figcaption></figcaption></figure>

3. In the pop-up, locate the **API key** for which you wish to revoke access, click the **Actions** dropdown button, and then click the **Revoke all access and delete** option.

<figure><img src="/files/UcoqgoRaXDmldJWWCcHw" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="warning" %}
Once the key is removed, any calls made using it will return a **401 Unauthorized error**.
{% endhint %}


---

# 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://docs.odinbot.io/api-documentation/getting-started.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.