> For the complete documentation index, see [llms.txt](https://docs.deepwriter.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.deepwriter.com/api-access/getting-started.md).

# Getting Started

How to get a Deepwriter API Key

## Getting Your DeepWriter API Key

The Deepwriter API key is essential for using Deepwriter MCP functionalities. This key authenticates your requests to the Deepwriter API, allowing you to programmatically interact with your projects.

### Locating Your API Key

Your Deepwriter API key can be found in your dashboard settings. Here's how to access it:

1. Log in to your DeepWriter account at [DeepWriter.com](https://deepwriter.com)
2. Navigate to the **Settings** section
3. Look for the API key section (as shown in the screenshot below)

<figure><img src="https://250182852-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyTfmQKHvO0H1nr1to9Br%2Fuploads%2F0xnpHIXSUY1dgv75ByLI%2Fimage.png?alt=media&amp;token=c2162b25-df4e-4d5d-a424-42e43f2f987c" alt=""><figcaption></figcaption></figure>

### Important Notes About Your API Key

* The API key is only viewable at the time of creation
* Each time you generate a new key, it invalidates any previous keys
* Treat your API key as sensitive information and do not share it publicly

### Generating a New API Key

If you need to generate a new API key (for example, if your current key has been compromised or you can't find your original key):

1. Go to the Settings page
2. Locate the API key section
3. Click the "Generate New Key" button
4. **Important**: Immediately copy and securely store your new API key, as you won't be able to view it again after leaving the page


---

# 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.deepwriter.com/api-access/getting-started.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.
