Datadoghqdatadoghq.com

ScoredJul 24, 2026, 05:44 AM

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.

API DesignA clean, typed, well-governed API contract agents can reason about2 pass2 warn1 fail76B
SignalPointsFindingsRationale
passAuth declared & discoverablevia spec25/25Authentication required (global or on every operation). Investigated: spec 100%, docs 100%, wellknown 0%.Agents can only authenticate when auth is declared, scoped, and discoverable.
warnMachine-readable, versioned contractvia spec18.8/25info.version="1.0" set but no versioning scheme (URL / header / media type) detected. Investigated: spec 75%, docs 50%.A current OpenAPI version with a declared versioning scheme lets agents reason about the contract.
passSecurity & governance hygienevia spec15/15No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 50%.No leaked secrets, no critical lint violations, no OWASP API Top-10 spec smells, and a published vulnerability-disclosure channel.
warnSchema coverage & depthvia spec12.5/2582% of operations have documented schemas (target 95%+). Investigated: spec 50%.Typed, complete request/response schemas are what make agent function-calling possible.
failExample coveragevia spec0/1028% example coverage. Investigated: spec 0%, docs 0%.Examples carry shape semantics schemas under-specify — for humans and agents alike.
Developer ExperienceThe context both developers and agents need to integrate fast — onboarding, code samples, complete descriptions and worked examples3 pass0 warn2 fail66C
SignalPointsFindingsRationale
passSelf-service developer portalvia docs29/29Self-service signup at https://www.datadoghq.com/free-datadog-trial/; free tier / sandbox documented. Investigated: docs 100%.Self-serve key/account creation is the fast first call for partners, with no sales gate.
passDescription completenessvia spec15/1593% of operations + parameters have substantive descriptions. Investigated: spec 100%.Complete descriptions are the context humans and agents need to use endpoints.
passChangelog publishedvia sdk13/13Newest official SDK activity 0 day(s) ago. Investigated: sdk 100%, spec 0%, docs 0%.A published changelog lets partners track changes without surprise.
failQuickstart presentvia docs0/25No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.A quickstart is the fastest path from landing page to first successful call.
failCode samples in docsvia docs0/18No detectable code samples across 20 sampled docs pages. Investigated: docs 0%.Multi-language samples shorten time-to-first-call.
Agent DiscoveryPartners and their agents can find your APIs — llms.txt, registries, crawlable and reachable docs3 pass1 warn0 fail93A+
SignalPointsFindingsRationale
passDocs reachable, not hard auth-gatedvia docs30/30All 50 sampled pages are publicly accessible. Investigated: docs 100%.Agents can only index and fetch docs they can reach — past auth gates and over correct HTTP semantics.
passRegistry & SDK presencevia docs28/28Indexed on Context7 (websites/datadoghq, 917366 snippets). Investigated: docs 100%, sdk 100%, cli 0%, mcp 0%, wellknown 0%.Listing in MCP registries and publishing SDKs puts the API where agents and their tooling look.
warnllms.txt present, valid & comprehensivevia docs22.5/30No /llms-full.txt found at the candidate origins. Investigated: docs 75%.A valid, comprehensive llms.txt is the machine-readable entry point for agents.
passCrawlable / AEOvia wellknown12/12Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.Bots allowed plus a fresh sitemap make docs findable by agent crawlers.
Agent UnderstandingAgents can correctly interpret your APIs — machine-readable errors, consistent descriptions, structured data, parseable docs2 pass1 warn2 fail78B
SignalPointsFindingsRationale
passMachine-readable errors (RFC 9457)via docs28/2815 distinct 4xx/5xx response codes documented. Investigated: docs 100%, spec 50%.RFC 9457 problem details and a documented error-code inventory let agents parse failures without burning tokens.
passOperation purpose clarityvia spec25/25100% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.Agents select the right endpoint from its summary + operationId; clear, named operations make tool-selection reliable — the strongest driver of correct tool choice.
warnAgent-navigable, token-efficient docsvia docs15.4/223 of 50 pages have substantive content differences between markdown and HTML (avg 13% missing). Investigated: docs 70%.Server-rendered, clean, small-footprint docs are what an agent can cheaply fetch and parse correctly.
failAgent instructions file (AGENTS.md)via wellknown0/10No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.An AGENTS.md gives coding agents explicit setup, auth, and usage instructions to interpret and operate the API — beyond llms.txt's link index.
failDocs structured datavia docs0/8Neither JSON-LD nor OpenGraph/meta tags detected across 3 assessed pages (3 JS-rendered). Investigated: docs 0%.Structured data (JSON-LD/schema.org) on docs pages gives agents an unambiguous parse target and is what answer engines cite. Detected on the JS-rendered head (Firecrawl) for a bounded page budget, so JS-injected JSON-LD is now caught; pages we can't render are excluded rather than failed.
naDescription consistency across surfaces—/7Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.Every surface tells the same story about what the product is.
Agent UsabilityAgents have the context to use your APIs reliably, not just find them3 pass0 warn2 fail71B
SignalPointsFindingsRationale
passRate-limit signalingvia spec22/22rate-limit behavior documented in the docs site at https://docs.datadoghq.com/api/latest/rate-limits/. Investigated: spec 100%, docs 100%.Machine-readable rate-limit headers let agents throttle adaptively.
passPagination documented & consistentvia spec22/22Pagination params detected on 291 list endpoint(s). Investigated: spec 100%, docs 100%.Consistent, documented pagination lets agents traverse collections.
passSandbox separationvia spec20/20Test credentials signaled (test-key prefixes) but no sandbox server declared in spec. Investigated: spec 100%, docs 100%.An isolated environment lets agents exercise destructive operations safely.
failIdempotency documentedvia spec0/270% of mutating operations document idempotency. Investigated: spec 0%, docs 0%.Documented idempotency lets agents retry safely.
failRunnable collection with test scriptsvia platform0/9No public Postman workspace discovered for the org. Investigated: platform 0%.A public, maintained collection with assertions is runnable truth agents validate against.
Resources Discovered

The public resources we found for Datadoghq — the evidence behind the score. All discovered from public sources; nothing here requires access to your systems.

Agent hintsContext7 (917,366)
APIs analyzed1Datadog API V2 Collection
Want to improve your results?