> For the complete documentation index, see [llms.txt](https://docs.toolhouse.ai/toolhouse/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.toolhouse.ai/toolhouse/developers/authentication.md).

# Authentication

In order to use the [Workers API](/toolhouse/developers/workers-api.md) you'll need to authenticate using a Toolhouse API key.

You can see the API key in the [API Keys section](https://toolhouse.app/settings/api-keys) or by navigating to your user menu and selecting **API Keys.**

The first API key is generated for you when you sign up for Toolhouse.

### Adding a new API key

1. Go to the [API Keys section](https://toolhouse.app/settings/api-keys) or by navigate to your user menu, then select **API Keys.**
2. In the **Generate new API key** section, type a name for your API Key. Give the key a recognizable name so you can reference it later
3. Click **Generate.**

### API key security

API Keys are encrypted both in transit and at rest in the Toolhouse platform.

{% hint style="info" %}
Toolhouse will never ask you to share API keys or other sensitive details.
{% endhint %}

### More ways to authenticate

By default, Toolhouse manages authentication for you. Customers on the Enterprise plan can implement custom authentication models based on their approved security policies. Talk to the Toolhouse team for more information.


---

# 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.toolhouse.ai/toolhouse/developers/authentication.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.