> 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/readme.md).

# Overview

Every Mimic API endpoint.

## How the endpoints are organized

Every action follows the same two calls. `POST /{action}/prepare` registers the action, returns its `id` and computes the EIP-712 data to sign; `POST /{action}/{id}/execute` submits the signature. Recurring strategies add a lifecycle on top — a list endpoint, an execution history, and a stop procedure — but create exactly the same way.

If you are integrating for the first time, start with [Signed intents](/mimic-api-docs/guides/getting-started/signed-intents.md) in the Guides section rather than reading endpoint-by-endpoint.

## Conventions

* Amounts are decimal strings in human units, never base-unit integers
* Timestamps are Unix milliseconds
* Slippage is basis points (`50` = 0.50%)
* The native asset is addressed as `0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE`


---

# 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/readme.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.