> For the complete documentation index, see [llms.txt](https://docs.airops.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airops.com/your-workspace/settings/secrets.md).
# Secrets
Centrally store and manage credentials, API keys, and other secrets.
Whenever you want to reference an API key or a secret in the Studio, you can safely add them to your workspace and make them available in the Studio in a safe manner.
In order to add a new secret, navigate to Settings > Secrets and click on "Create Secret".
Once added, you will be able to select them in the building by using this syntax:
```
_secrets["my_secret_name"]
```
As an example, if you add a secret named "MY\_SECRET" then you can access it in the builder as:
```
_secrets["MY_SECRET"]
```
For LLM credentials and other third-party integrations, AirOps usually has some native authentications, so before adding a custom secret, ensure that it is not listed in "Settings > Integrations" or "Settings > API providers".
If the integration is already authenticated in **Settings > Integrations**, you can expose its credentials to workflows directly without duplicating them as a secret. See [Integration Authentications](/your-workspace/settings/authentications.md).
---
# 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.airops.com/your-workspace/settings/secrets.md?ask=&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.
