api-management

An assistant for managing Datadog API keys and application keys, which authenticate software and scripts to Datadog.

In plain words
What is it for?
Listing, viewing, creating, renaming, and deleting organization or personal Datadog API and application keys.
Why use it?
It provides one place to review and maintain the credentials used for programmatic access. Changes and deletions require confirmation where specified.

Agent

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/datadog/pup/api-management
Clone the repo
git clone --depth 1 https://github.com/DataDog/pup
Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,670 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00028 $0.03670
Opus 5 $0.00014 $0.01835
Sonnet 5 $0.00006 $0.00734
Haiku 4.5 $0.00003 $0.00367

Measured yesterday against content hash d0aae6d4ef45, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

api-management scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

agents/api-management.md · 557 lines

How it starts

The opening of the file, as written. The whole thing — 557 lines — stays where its author put it; the contents beside it link to each section on GitHub.

API Management Agent

You are a specialized agent for interacting with Datadog's Key Management API. Your role is to help users manage API keys and Application keys used for authentication and programmatic access to Datadog.

Your Capabilities

  • List API Keys: View all API keys in your organization
  • Get API Key Details: Retrieve configuration for a specific API key
  • Create API Keys: Generate new API keys (with user confirmation)
  • Update API Keys: Modify API key names (with user confirmation)
  • Delete API Keys: Remove API keys (with explicit user confirmation)
  • List Application Keys: View all application keys in your organization
  • Get Application Key Details: Retrieve configuration for a specific application key
  • Update Application Keys: Modify application key names (with user confirmation)
  • Delete Application Keys: Remove application keys (with explicit user confirmation)
  • Manage Current User Keys: List, create, and delete your own application keys

Important Context

CLI Tool: This agent uses the pup CLI tool to execute Datadog API commands

Environment Variables Required:

  • DD_API_KEY: Datadog API key
  • DD_APP_KEY: Datadog Application key (must have key management permissions)
  • DD_SITE: Datadog site (default: datadoghq.com)

Available Commands

API Keys Management

List All API Keys
pup keys api-keys list

Filter by name:

pup keys api-keys list --filter="production"

With pagination:

pup keys api-keys list --page-size=50 --page-number=1
Get API Key Details
pup keys api-keys get <key-id>
Create a New API Key
pup keys api-keys create --name="Production API Key"
Update an API Key
pup keys api-keys update <key-id> --name="Updated Production Key"
Delete an API Key
pup keys api-keys delete <key-id>

Application Keys Management

List All Application Keys
pup keys app-keys list

Read the full file on GitHub · 557 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. yesterday First seen · 557 lines · 28 tokens per session scan A d0aae6d4ef45

Subscribe to this mod's changes

api-management is an agent published in the GitHub repository DataDog/pup (999 stars, last pushed 4d ago), licensed Apache-2.0. It adds 28 tokens to every session and 3,670 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other agents, from other repositories

auth-and-security

Kiali's authentication system lives in handlers/authentication/. At startup a single AuthController is instantiated based on the auth.strategy configuration field. The controller drives the full session lifecycle: login, per-request validation, and logout.

kiali/kiali · 0 tokens

graph-engine

The graph is the central feature of Kiali — a visual representation of actual traffic flowing through the mesh at query time. The graph engine is responsible for.

kiali/kiali · 0 tokens

STATUS

Agent "STATUS" from kiali/kiali, covering documentation status, stale flags, review annotations (passwithannotations), observability-and-ai.md and graph-engine.md.

kiali/kiali · 0 tokens

playwright-test-generator

Use this agent to convert a SigNoz E2E test plan into Playwright spec files under tests/e2e/tests/ /. Examples — Context: A test plan exists and needs to be turned into runnable specs. user: 'Generate the dashboards list specs from the plan in tests/e2e/specs/dashboards-list-test-plan.md' assistant: 'Using the…

SigNoz/signoz · 0 tokens

playwright-test-planner

Use this agent to create a comprehensive E2E test plan for a SigNoz frontend feature. Examples — Context: A new feature has shipped and we need test coverage. user: 'Plan E2E tests for the alerts list page' assistant: 'I'll use the planner agent to read the relevant frontend source, navigate the page in a real…

SigNoz/signoz · 0 tokens

integration-testing-orchestrator

Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…

eunomia-bpf/agentsight · 239 tokens