> For the complete documentation index, see [llms.txt](https://docs.trustlesswork.com/trustless-work/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trustlesswork.com/trustless-work/v2-en/introduction/developer-resources/request-api-key.md).

# Request API Key

### Get your v2 API key

Use an API key to authenticate requests to the Trustless Work Core API.

{% hint style="warning" %}
The self-service API key request flow is not available yet.
{% endhint %}

### Request access

To start building with **v2**, request your API key directly from our team on Telegram.

<a href="https://t.me/TrustlessWork" class="button primary" data-icon="paper-plane">Contact @TrustlessWork on Telegram</a>

When you receive your key, send it with each authenticated API request:

```http
x-api-key: <id>.<secret>
```

Keep your API key private. Do not expose it in client-side applications or public repositories.


---

# 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.trustlesswork.com/trustless-work/v2-en/introduction/developer-resources/request-api-key.md?ask=<question>&goal=<endgoal>
```

`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.
