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

# Overview

Execute on-chain wallet actions via signed intents, without taking custody.

The Mimic API lets you execute on-chain wallet actions — transfers, swaps, bridges, lending, staking — and run automated strategies like DCA, stop-loss and rebalancing, **without ever taking custody of your users' funds**.

Nothing moves unless the wallet owner has signed an explicit authorization. The API computes EIP-712 typed data, your user signs it with their own key, and you submit the signature back. Mimic executes on their behalf, within the limits they signed.

## Where to start

| If you want to…                          | Go to                                                                            |
| ---------------------------------------- | -------------------------------------------------------------------------------- |
| Understand the model before writing code | [Signed intents](/mimic-api-docs/guides/getting-started/signed-intents.md)       |
| Make your first API call                 | [Authentication](/mimic-api-docs/guides/getting-started/authentication.md)       |
| See a complete action end to end         | [Your first action](/mimic-api-docs/guides/getting-started/your-first-action.md) |
| Integrate a specific action              | [Integrations](/mimic-api-docs/guides/integrations/dca.md)                       |
| Look up an endpoint                      | The **API Reference** section                                                    |

## Two kinds of action

Every action is created the same way. What differs is what happens afterwards:

* **One-time actions** — a transfer, a swap, a bridge, a contract call. Prepared, signed, executed once.
* **Strategies** — DCA, stop-loss, take-profit, rebalancing. Prepared and signed once, then executed repeatedly by Mimic on a schedule or trigger until they end or you stop them.

The creation flow is identical for both. Strategies add a lifecycle on top: a list endpoint, an execution history, and a stop procedure.


---

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