From 9e582c5c74921406b45b3ecb4b6866e2344790b0 Mon Sep 17 00:00:00 2001 From: Jordan Morgan Date: Wed, 17 Jun 2026 12:17:51 -0500 Subject: [PATCH] Add note about Superwall API key usage Adds a Note to the Agents settings doc explaining how SUPERWALL_API_KEY is provided and when to create an organization API key. Clarifies that Superwall Agents supply a managed org API key for new turns, and instructs external agents, custom tools, or local scripts to create an org API key under Settings > API Keys. Also warns against using the public `pk_` SDK key for server/API access. --- content/docs/agents/settings.mdx | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/content/docs/agents/settings.mdx b/content/docs/agents/settings.mdx index efbc86d..328ce7e 100644 --- a/content/docs/agents/settings.mdx +++ b/content/docs/agents/settings.mdx @@ -42,6 +42,15 @@ Use **Environment** for variables that tools on the hosted machine can read. Some integration variables are reserved. `SUPERWALL_API_KEY` comes from the organization selector. `GH_TOKEN`, `GITHUB_TOKEN`, and `SLACK_BOT_TOKEN` come from the GitHub and Slack connection flows. + + **Need a Superwall API key?** In Superwall Agents, select your organization in + the chat header. Agents provides a managed organization API key to new turns, + so you usually do not add `SUPERWALL_API_KEY` here. For an external agent, + custom tool, or local script, create an organization API key in + [Settings > API Keys](/dashboard/dashboard-settings/overview-settings-access-controls#api-key-access). + Do not use the public `pk_` SDK key for server or API access. + + Do not paste secret values into chat. Store them in Environment so tools can use them without adding the secret to conversation history.