# Datadog — API Agent Score

> Score: 77/100 (Grade: B) | Domain: datadoghq.com | Rubric: 1.0.0 | Checked: July 24, 2026

Datadog scored 77/100 (B), classified "partially-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/datadoghq)
[All organizations](https://www.postman.com/ai/ai-ready-apis/llms.txt)

## Summary

- Overall: 77/100 (B)
- Classification: partially-ready

## Category Scores

- API Design: 76/100 (B)
- Developer Experience: 66/100 (C)
- Agent Discovery: 93/100 (A+)
- Agent Understanding: 78/100 (B)
- Agent Usability: 71/100 (B)

## Check Results

### API Design

- [pass] Auth declared & discoverable — Authentication required (global or on every operation). Investigated: spec 100%, docs 100%, wellknown 0%.
- [warn] Machine-readable, versioned contract — info.version="1.0" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 75%, docs 50%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 50%.
- [warn] Schema coverage & depth — 82% of operations have documented schemas (target 95%+). Investigated: spec 50%.
- [fail] Example coverage — 28% example coverage. Investigated: spec 0%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Self-service signup at https://www.datadoghq.com/free-datadog-trial/; free tier / sandbox documented. Investigated: docs 100%.
- [pass] Description completeness — 93% of operations + parameters have substantive descriptions. Investigated: spec 100%.
- [pass] Changelog published — Newest official SDK activity 0 day(s) ago. Investigated: sdk 100%, spec 0%, docs 0%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [fail] Code samples in docs — No detectable code samples across 20 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [pass] Docs reachable, not hard auth-gated — All 50 sampled pages are publicly accessible. Investigated: docs 100%.
- [pass] Registry & SDK presence — Indexed on Context7 (websites/datadoghq, 917366 snippets). Investigated: docs 100%, sdk 100%, cli 0%, mcp 0%, wellknown 0%.
- [warn] llms.txt present, valid & comprehensive — No /llms-full.txt found at the candidate origins. Investigated: docs 75%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — 15 distinct 4xx/5xx response codes documented. Investigated: docs 100%, spec 50%.
- [pass] Operation purpose clarity — 100% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — 3 of 50 pages have substantive content differences between markdown and HTML (avg 13% missing). Investigated: docs 70%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [fail] Docs structured data — Neither JSON-LD nor OpenGraph/meta tags detected across 3 assessed pages (3 JS-rendered). Investigated: docs 0%.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Rate-limit signaling — rate-limit behavior documented in the docs site at https://docs.datadoghq.com/api/latest/rate-limits/. Investigated: spec 100%, docs 100%.
- [pass] Pagination documented & consistent — Pagination params detected on 291 list endpoint(s). Investigated: spec 100%, docs 100%.
- [pass] Sandbox separation — Test credentials signaled (test-key prefixes) but no sandbox server declared in spec. Investigated: spec 100%, docs 100%.
- [fail] Idempotency documented — 0% of mutating operations document idempotency. Investigated: spec 0%, docs 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.

## Executive Summary

Datadoghq's API program shows strong discoverability foundations, but partners and their AI agents face meaningful friction in two areas: getting oriented quickly (no quickstart, sparse code samples, missing request/response examples) and operating with confidence (no agent instruction file, no structured doc metadata, no runnable collection with test scripts, and undocumented idempotency). Fixing example coverage and agent-readable context first will unlock both human partner onboarding and AI-assisted integration at scale; runnable collections and operational reliability documentation compound that value immediately after.