> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mythex.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Secrets in chat

> When the agent needs an API key, fill the in-chat secrets card without pasting secrets into the prompt.

# Secrets in chat

Sometimes the agent needs a key (Stripe, OpenAI, email provider, etc.) to finish wiring your app.

## Secrets request card

When that happens, Mythex shows a **secrets request** card in chat:

<img src="https://mintcdn.com/mythex/uQE27QrCJJ-e4nfa/images/secrets-card.png?fit=max&auto=format&n=uQE27QrCJJ-e4nfa&q=85&s=d5cee6dacedbf5fef0979b6aa0a74d58" alt="Add secrets card in chat for RESEND_API_KEY" width="2880" height="1800" data-path="images/secrets-card.png" />

1. Enter the values in the card fields (not in the message box)
2. Confirm so they are stored as [project secrets](/features/env-and-secrets)
3. The agent continues with the keys available in the sandbox

This keeps secrets out of the chat transcript compared to pasting them into a prompt.

## Also available in settings

You can always add or edit secrets under **project settings → Secrets**, or use `/secrets` in chat.

## Tips

* Prefer server-side keys for privileged operations
* If a key ever appears in chat history, rotate it at the provider
* After changing secrets for a **published** app, publish again so the deploy picks them up

## Related

* [Environment variables and secrets](/features/env-and-secrets)
* [Project settings](/features/project-settings)
* [Integrate any API](/recipes/integrate-any-api)