> For the complete documentation index, see [llms.txt](https://docs.frontrun.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.frontrun.pro/trading/powered-by-turnkey.md).

# Powered by Turnkey

Frontrun uses Turnkey—the same wallet infrastructure used by Axiom—to create wallets by default.

#### Frontrun never has access to your private keys.

By default, wallets created in Frontrun are powered by [Turnkey](https://www.turnkey.com/). Private keys are generated, stored, and used for signing through Turnkey’s secure infrastructure. Frontrun cannot access your keys or move funds on your behalf.

This model enables instant trades and fast execution without changing the wallet or custody model traders are already familiar with.

If you’ve used Axiom, the underlying wallet model is the same.

{% hint style="info" %}
Learn more about Turnkey → <https://docs.turnkey.com/>
{% endhint %}


---

# 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://docs.frontrun.pro/trading/powered-by-turnkey.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.