Agent report card
Can an agent use Datadog API through Monitor operations?
Five-stage assessment
Where agent autonomy holds and where it breaks
- EvaluateReady
- Sign upLimited
- PayLimited
- ProvisionLimited
- OperateLimited
The exact service and stable evaluation or access entrypoints are publicly discoverable.
Datadog explicitly provides its public API documentation entrypoint, noting that the Datadog API allows programmatic access to the platform, uses standard HTTP response codes, and authenticates via DD-API-KEY and DD-APPLICATION-KEY headers.
Applicable terms are stable, readable, retrievable, and materially complete.
Eligibility conditions and required inputs are explicit and decidable.
Price or no-charge status, variables, currency, and material conditions are explicit.
Verified structured artifacts accelerate discovery of the evaluation surface.
Web-agent access policy is explicit and verified for the assessed resources.
Evidence and actions6 signals
Can an agent decide every material eligibility condition before commitment?
supported: freshEligibility conditions and required inputs are explicit and decidable.
Datadog's Master Subscription Agreement explicitly sets out eligibility and authority conditions, specifying that individual users represent they are legally permitted and competent, while organizational users represent they have the right, power, and authority to enter into the agreement.
Can an agent estimate cost or confirm no-charge status before commitment?
supported: freshPrice or no-charge status, variables, currency, and material conditions are explicit.
Datadog's pricing page explicitly states log ingestion pricing starting at $0.10 per ingested or scanned GB per month (billed annually or on-demand) and standard indexing options in USD.
Can an agent find the exact service and its stable entrypoints?
supported: freshThe exact service and stable evaluation or access entrypoints are publicly discoverable.
Datadog explicitly provides its public API documentation entrypoint, noting that the Datadog API allows programmatic access to the platform, uses standard HTTP response codes, and authenticates via DD-API-KEY and DD-APPLICATION-KEY headers.
Are verified structured discovery artifacts available?
supported: freshVerified structured artifacts accelerate discovery of the evaluation surface.
Datadog explicitly provides verified structured documentation artifacts for AI agents on its API Reference page, offering a markdown version at https://docs.datadoghq.com/api/latest.md and a documentation index at /llms.txt.
Can an agent retrieve and understand the applicable commitment terms?
supported: freshApplicable terms are stable, readable, retrievable, and materially complete.
The Master Subscription Agreement for Datadog is publicly retrievable, readable, and defines stable, comprehensive terms governing the purchase and use of Datadog services.
Does the vendor deliberately describe access for web agents?
supported: freshWeb-agent access policy is explicit and verified for the assessed resources.
Datadog explicitly declares access for AI agents on its public API and authentication documentation pages by providing dedicated markdown versions (e.g., https://docs.datadoghq.com/api/latest.md) and an index at /llms.txt.
Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.
Datadog provides scoped application keys and non-interactive service accounts to access APIs without associating scripts with specific individuals. However, application keys are created within the web application, leaving issuance or manual copying constrained.
A stable canonical route begins the required access bootstrap.
Evidence and actions5 signals
Can an agent operate the access controls and safe handoffs deterministically?
supported: freshCurrent admissible evidence does not resolve this finding.
The captured endpoint for https://app.datadoghq.com/signup returned a browser upgrade message requiring Chrome, Firefox, Safari, or Edge. Current admissible evidence does not resolve access control operability.
Is there a stable route to begin obtaining service access?
supported: freshA stable canonical route begins the required access bootstrap.
Documentation provides an explicit link to create a Datadog account as the starting entrypoint for obtaining service access.
Can an agent obtain access without an unsupported CAPTCHA boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
The signup endpoint captures display a browser compatibility prompt, and documentation pages do not explicitly state whether CAPTCHA challenges are used. Evidence across all evaluated targets does not resolve CAPTCHA compatibility.
Can an agent obtain scoped, revocable authority for this service?
supported: freshMachine credentials exist but require manual copying, broad authority, or weak lifecycle support.
Datadog provides scoped application keys and non-interactive service accounts to access APIs without associating scripts with specific individuals. However, application keys are created within the web application, leaving issuance or manual copying constrained.
Can required phone verification be completed through a supported boundary?
supported: freshCurrent admissible evidence does not resolve this finding.
The signup capture returns an unresolved browser requirement message and documentation does not state phone verification terms. Admissible evidence does not resolve whether phone verification is required or supported.
What would improve this stage
- Provide scoped delegated authorization with consent, revocation, and deterministic resumption.
The public commitment omits a material component until later in the flow.
Datadog discloses pricing currency ($) and recurrence options (monthly and annual) across products such as App and API Protection (starting at $31 per host per month) and Feature Flags, but notes that volume terms, overages, and custom billing plans can be customized, making overall commitment components contextual.
A documented direct purchase path reaches paid access without a vendor decision point.
Evidence and actions4 signals
Can an agent construct checkout, hand off approval safely, and resume?
supported: freshCurrent admissible evidence does not resolve this finding.
Datadog accepts payment by credit card through the Plan page under Plan & Usage -> Plan. Current evidence describes where administrators manage credit card payment details but does not document an API, protocol, or accessible web flow supporting deterministic checkout, approval handoff, and resumption.
Is the exact commercial commitment disclosed before authorization?
supported: freshThe public commitment omits a material component until later in the flow.
Datadog discloses pricing currency ($) and recurrence options (monthly and annual) across products such as App and API Protection (starting at $31 per host per month) and Feature Flags, but notes that volume terms, overages, and custom billing plans can be customized, making overall commitment components contextual.
Can payment be authorized within scoped agent or explicit human authority?
supported: freshCurrent admissible evidence does not resolve this finding.
The documentation states that administrators can manage and update credit cards on the Plan page, and future bills are auto-charged. However, current evidence does not establish a documented rail for scoped delegation or explicit human-confirmed payment authorization with receipts.
Is a direct self-service path to paid access documented?
supported: freshA documented direct purchase path reaches paid access without a vendor decision point.
Datadog explicitly documents a self-service path to pay by credit card through the Plan page (Plan & Usage -> Plan) for administrators on monthly plans without requiring sales intervention.
What would improve this stage
- Disclose the complete commitment before payment authorization.
Delivery needs additional human transfer or has weak scope or lifecycle semantics.
Datadog application keys are displayed only once during creation when One-Time Read (OTR) mode is enabled and cannot be retrieved later.
Provisioning is machine-triggerable or follows deterministically from an allowed handoff.
A synchronous success response returns a usable created resource or access material; otherwise asynchronous work exposes progress, terminal state, reconciliation, and a documented bound.
Evidence and actions3 signals
Can usable access material be delivered securely to an authorized agent?
supported: freshDelivery needs additional human transfer or has weak scope or lifecycle semantics.
Datadog application keys are displayed only once during creation when One-Time Read (OTR) mode is enabled and cannot be retrieved later.
Can an agent determine successful provisioning completion and reconcile asynchronous failure?
supported: freshA synchronous success response returns a usable created resource or access material; otherwise asynchronous work exposes progress, terminal state, reconciliation, and a documented bound.
Creating a monitor synchronously returns the created monitor object containing its created timestamp, ID, name, overall state, and options.
Can provisioning be initiated within supported agent authority?
supported: freshProvisioning is machine-triggerable or follows deterministically from an allowed handoff.
Monitor creation can be initiated programmatically via HTTP requests using the Datadog API.
What would improve this stage
- Deliver scoped access material through a secure documented machine-usable flow.
Safe failure handling is documented only partially.
Datadog documents rate limit failure handling, returning HTTP status code 429 along with X-RateLimit-Period and X-RateLimit-Limit response headers to guide retry timing. However, idempotency, cancellation, and reconciliation semantics are not fully established in the retained text.
Only part of the credential lifecycle is agent-operable.
Every essential target has a stable documented agent-usable interface alternative.
Request-time authentication is documented and usable under scoped agent authority.
Essential operations have stable readable request, response, and effect semantics.
Evidence and actions6 signals
Is an agent-native protocol interface verified against the essential targets?
supported: freshCurrent admissible evidence does not resolve this finding.
The retained excerpts describe REST or RPC interfaces, SDKs and CLIs for Datadog API; they contain no first-party statement that an agent-native protocol interface is absent, and several navigation excerpts mention MCP resources without establishing coverage of the assessed targets.
- monitor-api
Can an agent manage credential expiry, rotation, revocation, compromise, and recovery?
supported: freshOnly part of the credential lifecycle is agent-operable.
Datadog documents API key revocation and client token deletion in the UI, managed rotation via AWS Secrets Manager, and key lifecycle API endpoints (creation, retrieval, editing, deletion, and personal access token revocation). However, complete agent-executable credential lifecycle recovery is not established.
Can an agent handle applicable failure modes safely?
supported: freshSafe failure handling is documented only partially.
Datadog documents rate limit failure handling, returning HTTP status code 429 along with X-RateLimit-Period and X-RateLimit-Limit response headers to guide retry timing. However, idempotency, cancellation, and reconciliation semantics are not fully established in the retained text.
Can an agent authenticate service operations with scoped authority?
supported: freshRequest-time authentication is documented and usable under scoped agent authority.
API requests require authentication via DD-API-KEY and DD-APPLICATION-KEY HTTP headers. Datadog explicitly supports scoping application keys to minimal granular authorization permissions.
Are essential operation inputs, outputs, and effects stable and decidable?
supported: freshEssential operations have stable readable request, response, and effect semantics.
Datadog API endpoints have stable, readable contracts using standard HTTP methods and JSON responses. For example, the Create a Monitor endpoint explicitly documents query syntax, index parameters, rollup methods, time windows, operators, and threshold values, while rate limit errors return standard HTTP 429 codes.
- monitor-api
Can an agent perform every essential assessment target through a usable interface?
supported: freshEvery essential target has a stable documented agent-usable interface alternative.
Every essential target has documented machine-operable HTTP API endpoints across all Datadog site regions (e.g., POST https://api.datadoghq.com/api/v1/monitor), accessible via standard HTTP requests and official client SDKs.
- monitor-api
What would improve this stage
- Document applicable structured errors, retry, cancellation, and reconciliation semantics.
- Provide scoped expiry, rotation, revocation, compromise, and recovery operations.
What works
- Evaluate: The exact service and stable evaluation or access entrypoints are publicly discoverable.
What blocks agents
No stage is established as blocked.
Where autonomy is limited
- Sign up: Machine credentials exist but require manual copying, broad authority, or weak lifecycle support.
- Pay: The public commitment omits a material component until later in the flow.
- Provision: Delivery needs additional human transfer or has weak scope or lifecycle semantics.
- Operate: Safe failure handling is documented only partially.
What this grade establishes
14 of 14 graded signals have current supporting evidence. 0 of 5 additional barrier checks are verified.Unknown checks are not a pass or a confirmed blocker. This report is not proof of an end-to-end purchase or service session.
How the grade is derived
A through C grades count Limited stages; D and F reflect Blocked stages by lifecycle severity.
Coverage is complete only when every graded signal has supported, fresh, non-conflicting evidence. Barrier and informational signals do not change coverage; only fresh, supported barrier values that passed their admission evidence rule participate in stage outcomes.
Each stage takes its worst graded signal or verified barrier. A fresh, supported mandatory barrier that passed its admission evidence rule can block that stage; incomplete or stale barrier evidence remains context only. The overall grade is derived from the five stage states.
Startup offers
Datadog on the startup-offers board
- Up to $100,000 in credits (up to 1 year free)Datadog for Startups
Distribution
The grade’s badge
One stable image resolving the record’s current live facts, linking to the canonical page. Embed it once; it keeps itself current. Placement is never evidence and never affects rank.
[](https://sourcey.com/log/datadog/agent-readiness/datadog-api/monitor-operations)Improve the report
Correct it, rerun it, or improve the funnel.
- Profile
- arp_01kzf0m4x7n0qb42yj8v6ce9ds
- Projection
- sha256:79b7e625d20c3a772426603a8dfd5ef7a7cb4268c6b31cca33448360a4c266a3
- Policy
- service-use-2026-09-07-blocking-barriers-r12 · sha256:fc9e8f046d86fcf19ab2f1bc547219e503cdc11ffa135d020db7285965cd7d1d
Every request carries these exact identifiers.How report cards are assessed →View the exact declaration