Setting the file. One moment.
Subchapter 57.1
references/common-credentials.mdMarkdown2 KBView on GitHub
Used by the LLM Observability reference files (llmobs-python.md / llmobs-nodejs.md). Use only the local tool named below — do not invent tool names.
CreateApiKey)DD_API_KEY is required for LLM Observability (dd-trace / ddtrace in agentless mode — see llmobs-python.md / llmobs-nodejs.md).
CreateApiKey(
name: string REQUIRED — display name for the API key (e.g. "<project-folder-name> - LLM Observability")
)On success it returns { apiKey, name }.
Ask the user to confirm before creating a new org-level API key on their behalf. If the call fails (e.g. insufficient scope), ask the user to create a key manually at https://app.datadoghq.com/organization-settings/api-keys and paste it in. Do not proceed until they confirm.
Never log or print the key value in your final report.
Scan the project root for env files in this order and use the first one found:
.env.local → .env.development.local → .env.development → .env
If none exist, choose which file to create based on framework:
.env.local.envUse the first non-empty DD_API_KEY (or DATADOG_API_KEY) found, in this order:
DD_SITE to the env file with printf 'DD_SITE=%s\nDD_API_KEY=%s\n' "${DD_SITE:-datadoghq.com}" "$DD_API_KEY" >> <env file>, so the value never appears in your output.CreateApiKey.Upsert DD_API_KEY=<key> into the file identified above (create it if needed). Preserve all existing lines — only add or replace the DD_API_KEY line.
If a .gitignore/global-ignore rule blocks you from writing directly to an env file, use shell redirection (echo "VAR=value" >> .env.local) instead of a file-write tool that respects ignore rules.