Doppler
Doppler is a centralized, cloud-based SecretOps platform that manages application configuration and secrets for humans, CI/CD pipelines, and AI agents across environments. It provides Git-style activity logs, rollbacks, webhooks, SDKs, and deep integrations with AWS, Azure, GCP, Kubernetes, and the major CI providers, with SOC 2 and ISO compliance. The Doppler REST API offers full programmatic control over projects, configs, secrets, tokens, service accounts, and audit logs using Bearer token authentication.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Doppler the way a machine reads it — 15 machine-readable artifacts across 9 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Doppler scores 32.9/100 (thin), with a separate agent-readiness read of 41/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Doppler
Each block below is one kind of artifact we hold for Doppler. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 9
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Doppler REST API
Versioned REST API (v3) for managing Doppler workplaces, projects, environments, configs, secrets, dynamic secrets, service tokens, service accounts, integrations, audit logs, a...
Doppler ActivityLogs API
The ActivityLogs API from Doppler — 1 operation(s) for activitylogs.
Doppler Auth API
The Auth API from Doppler — 1 operation(s) for auth.
Doppler Configs API
The Configs API from Doppler — 2 operation(s) for configs.
Doppler Environments API
The Environments API from Doppler — 1 operation(s) for environments.
Doppler Projects API
The Projects API from Doppler — 2 operation(s) for projects.
Doppler Secrets API
The Secrets API from Doppler — 3 operation(s) for secrets.
Doppler ServiceTokens API
The ServiceTokens API from Doppler — 1 operation(s) for servicetokens.
Doppler Webhooks API
The Webhooks API from Doppler — 1 operation(s) for webhooks.
Scroll within the panel for all 9 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Doppler REST API
OPEN COLLECTIONSecurity Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Doppler — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Commercial 1
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/doppler · machine-readable index on apis.io