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

# Managing API Keys

We currently have one API provider which is [OpenAI](https://openai.com/). By default, we use a shared OpenAI key for all the widgets. \
\
If you want to create your own API key for better performance, please navigate to <https://platform.openai.com/api-keys>.\
\
Once you have your own API key, please navigate to <https://interaxai.com/account/api-keys> and enter your details.\
\
You will not be able to see your API key after you save it. If you forget your API key, you can always revoke the current one but make sure that none of your widgets are using it.<br>

{% hint style="info" %}
Your API Keys will be kept encrypted and secure. It is recommended that you do not share your API keys with anyone and that you regularly rotate your API keys.&#x20;
{% 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 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.interaxai.com/getting-started/managing-api-keys.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.