Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Datadog SLOs (BYOK) — connector documentation

  • MCP endpoint: https://byok-datadog-slos.connectorbay.com/mcp
  • REST API: POST https://byok-datadog-slos.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-datadog-slos.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Datadog SLOs Datadog API key (US1 site, datadoghq.com), sent in the X-Upstream-Key header and the Datadog application key (read scopes are enough) in X-Upstream-Key-2 of every request (never stored, logged or cached)
  • Health: https://byok-datadog-slos.connectorbay.com/health · Tool schemas: https://byok-datadog-slos.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-datadog-slos · agent@connectorbay.com

What Datadog SLOs (BYOK) is for

Datadog SLOs (BYOK) lets an AI assistant read your own Datadog SLOs data through the Datadog SLOs API with a key you supply (Datadog API key (US1 site, datadoghq.com)). Read-only: 6 tools (list_slos, get_slo, get_slo_history, list_slo_corrections, get_slo_corrections, get_slo_correction). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.datadoghq.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Datadog SLOs. Datadog SLOs and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which Datadog SLOs have a 99.9 target?"
  • "Show Datadog SLO abc123def456"
  • "What is the SLI and error budget of Datadog SLO abc123def456 for the last 7 days?"
  • "Which Datadog SLO corrections exist?"
  • "Which corrections apply to Datadog SLO abc123def456?"
  • "Show Datadog SLO correction c1"

What it does

  • list_slos: List service level objectives with type (metric, monitor, time_slice), target and warning thresholds, timeframe, tags and linked monitor ids. Filter by name, tag, ids or metrics query.
  • get_slo: Get one SLO by id: type, description, query, thresholds per timeframe, tags and linked monitors. Set with_configured_alert_ids to also get monitors that alert on it.
  • get_slo_history: Get an SLO's status over a time window: overall SLI value, uptime, remaining error budget and thresholds. Optional custom target.
  • list_slo_corrections: List SLO corrections (maintenance and deployment windows excluded from SLO calculations) with category, window, recurrence rule and timezone.
  • get_slo_corrections: List the corrections applied to one SLO.
  • get_slo_correction: Get one SLO correction by id.

BYOK key

You bring your own Datadog SLOs Datadog API key (US1 site, datadoghq.com) (https://app.datadoghq.com/organization-settings/api-keys). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.datadoghq.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Datadog SLOs API (api.datadoghq.com) with a BYOK key; documentation: https://docs.datadoghq.com/api/latest/service-level-objectives/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Datadog SLOs. Datadog SLOs and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Datadog SLOs account.

Built for: Worldwide. Languages: English.