diff --git a/content/guides/authentication.mdx b/content/guides/authentication.mdx
index 6310e56..0eb607a 100644
--- a/content/guides/authentication.mdx
+++ b/content/guides/authentication.mdx
@@ -11,10 +11,12 @@ Create and manage API keys in the [CALL-E dashboard](https://dashboard.heycall-e
 Production API keys use the `iams_live_` prefix.
 Pass the complete dashboard value directly to the SDK; no client-side token exchange is required.
 
-Store the key in your backend secret manager or runtime environment:
+Store the key in your backend secret manager or runtime environment. Replace
+`<YOUR_CALLE_API_KEY>` below with the complete key from the dashboard; the
+placeholder is not a working credential:
 
 ```bash
-export CALLE_API_KEY="iams_live_example"
+export CALLE_API_KEY="<YOUR_CALLE_API_KEY>"
 ```
 
 Do not commit API keys, print them in logs, send them to browser code, or store them in mobile apps. The CALL-E SDKs are server SDKs for trusted backend services and workers.
diff --git a/content/guides/quickstart.mdx b/content/guides/quickstart.mdx
index 1888732..c5fdcb5 100644
--- a/content/guides/quickstart.mdx
+++ b/content/guides/quickstart.mdx
@@ -24,10 +24,12 @@ pnpm add @call-e/calle
 pip install calle-ai
 ```
 
-Set your API key before running the examples:
+Set your API key before running the examples. Replace `<YOUR_CALLE_API_KEY>`
+with the complete key from the dashboard; the placeholder is not a working
+credential:
 
 ```bash
-export CALLE_API_KEY="iams_live_example"
+export CALLE_API_KEY="<YOUR_CALLE_API_KEY>"
 ```
 
 You can view your API keys in the [CALL-E dashboard](https://dashboard.heycall-e.com/account/api-keys).