Keys and configuration
Know which values belong in a browser bundle, on your server, or in your workspace connection screen.
On this page
Each Askdepth integration uses its own configuration. A browser write key, a connector signing secret, and an OAuth access token serve different purposes.
Browser SDK configuration
Obtain the public write key and full telemetry endpoint for your configured collector from your Askdepth administrator. Use the exact values for the intended environment. The SDK initializer requires both.
NEXT_PUBLIC_ASKDEPTH_WRITE_KEY=YOUR_PUBLIC_WRITE_KEY
NEXT_PUBLIC_ASKDEPTH_ENDPOINT=https://YOUR_COLLECTOR/v1/telemetryThe NEXT_PUBLIC_ names are an example for Next.js. Vite and other bundlers have their own public environment-variable conventions.
The write key is designed to be sent by a browser and appears in its requests. It is not an administrative API token. Do not substitute a connector signing secret, OAuth token, or server credential.
Audience Connector configuration
Keep your database connection string and connector HMAC secret on the server. They must never appear in browser code or public environment variables. Askdepth calls your connector's public HTTPS endpoints; the connector queries the database you control.
See request signing for the actual authentication contract and connector endpoints for payloads.
MCP configuration
Open your workspace's Settings → Integrations → Coding agents → MCP screen. Copy the generated workspace-specific URL and add command from there.
MCP uses browser sign-in and OAuth authorization. You do not paste a browser write key into your coding agent. A local MCP connection also does not require a hosted Claude routine or a GitHub repository connection.
See MCP authentication for scopes, expiry, and revocation.
Separate environments
Use configuration appropriate to development, staging, and production. Set the SDK's environment explicitly; it is metadata, not a substitute for access control or separate credentials.
In Next.js, public environment variables are embedded during the production build. Rebuild after changing them. Never print secret values as part of a diagnostic report.