> For the complete documentation index, see [llms.txt](https://mimic-api.gitbook.io/mimic-api-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mimic-api.gitbook.io/mimic-api-docs/guides/getting-started/authentication.md).

# Authentication

Authenticate every request with your API key.

Every endpoint requires your API key in the `X-Api-Key` header:

```http
X-Api-Key: <your-api-key>
```

Your key scopes everything you can see. Read endpoints only ever return resources created under your own key — `GET /dca` lists your strategies, never anyone else's.

{% hint style="danger" %}
Your API key is a server-side credential. Never ship it in a browser, mobile app, or any client your users control.
{% endhint %}

## The public endpoints

Four reference-data endpoints need no key at all:

* `GET /chains`
* `GET /settlers`
* `GET /settlers/{chain}`
* `GET /tokens`

Useful for populating a chain or token picker before your user has authenticated with you.

## When authentication fails

A missing or invalid key returns `401`. A valid key that doesn't own the resource returns `403` — worth distinguishing in your error handling, because `403` usually means a bug in which key you're sending, not an expired one.


---

# 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://mimic-api.gitbook.io/mimic-api-docs/guides/getting-started/authentication.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.