> For the complete documentation index, see [llms.txt](https://docs.lambda.markets/lambda-markets/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lambda.markets/lambda-markets/getting-started/authentication/api-keys.md).
# API Keys
{% hint style="warning" %}
To execute via Lambda 2.0 with basic + advanced order types, telegram trading or via our alert feeds — you’ll need to connect to your preferred centralised exchange via secure API keys.
{% endhint %}
Lambda 2.0 — securely integrate your CEX account
```
// Prior to enabling API integration, this documentation will be updated with extensive information to ensure absolute user security.
```
We will use a thoroughly tested + third party audited security layer for the **storage of user API keys** — we check to ensure that these keys are only ever enabled to be ‘trade only’ and never ‘withdraw or move funds’ — all routes have security guards + logs are monitored extremely closely.
### Important:
For those who’d like to dive deeper on how we plan to treat user API keys:
{% embed url="" %}
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.lambda.markets/lambda-markets/getting-started/authentication/api-keys.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.
