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

# Wallets

Safe wallets, custodial EOAs, and which actions each supports.

Every action pulls funds from a `wallet` address. Mimic works with wallets you bring, and can also create them for you.

## Creating a Safe wallet

A Safe is a smart contract wallet owned by an address your user controls. Creation follows the same [signed-intent flow](/mimic-api-docs/guides/getting-started/signed-intents.md) as any other action:

```http
POST /wallets/safe/prepare
X-Api-Key: <your-api-key>
Content-Type: application/json

{
  "chain": "ethereum",
  "owner": "0x1234567890abcdef1234567890abcdef12345678"
}
```

Then submit the signature to `POST /wallets/safe/{id}/execute`, using the `id` that `prepare` returned. Track the deployment via `GET /wallets/safe/{id}`.

Two optional fields are worth knowing:

* **`expectedAddress`** — reuse an address already deployed on another chain, so one user has the same wallet address everywhere. If the wallet already exists for that `owner` and `chain`, creation is skipped.
* **`externalId`** — your own identifier for the wallet, so you can reference it by an id from your system rather than storing addresses.

## Creating a custodial EOA

```http
POST /wallets/eoa
X-Api-Key: <your-api-key>
Content-Type: application/json

{ "chain": "ethereum" }
```

Mimic generates and stores the keypair. This is the one endpoint that does not follow the signed-intent flow — there is no prepare step and nothing to sign, because there is no existing owner to authorize it. It takes an `Idempotency-Key` header instead, so a retried request cannot create a second wallet.

{% hint style="warning" %}
A custodial EOA means Mimic holds the key. That is a different trust model from the rest of the API — choose it deliberately.
{% endhint %}

## Which wallet for which action

| Action                         | Safe | EOA                                |
| ------------------------------ | ---- | ---------------------------------- |
| Transfers, swaps, bridges      | ✅    | ✅                                  |
| Lending, staking               | ✅    | ✅                                  |
| Contract calls                 | ✅    | ❌ unless using EIP-7702 delegation |
| Strategies (DCA, stop-loss, …) | ✅    | ✅                                  |

Contract calls are the exception: they execute arbitrary calldata from the wallet, which a plain EOA cannot do without delegating its code via EIP-7702.

## Balances

`GET /wallets/{wallet}/balances` returns what a wallet holds, on a given chain, with USD values.


---

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