DevCycle
DevCycle is an OpenFeature-native feature flag and feature management platform (a Dynatrace company) for creating, targeting, rolling out, and cleaning up feature flags without disrupting developer workflow. It exposes a Management API for administering projects, environments, features, variables, variations, and audiences, and a Bucketing API for server-side flag evaluation, backed by client and server SDKs across every major language, OpenFeature providers, a `dvc` CLI, a Terraform provider, and an official hosted MCP server for AI coding agents.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles DevCycle the way a machine reads it — 35 machine-readable artifacts across 25 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 — DevCycle scores 62.7/100 (strong), with a separate agent-readiness read of 78/100 (agent native). 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 DevCycle
Each block below is one kind of artifact we hold for DevCycle. 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 25
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.
DevCycle Audiences API
The Audiences API from DevCycle — 3 operation(s) for audiences.
DevCycle Audit Log API
The Audit Log API from DevCycle — 1 operation(s) for audit log.
DevCycle [Beta] Semantic Patch API
The [Beta] Semantic Patch API from DevCycle — 1 operation(s) for [beta] semantic patch.
DevCycle Bucketing API API
The Bucketing API API from DevCycle — 4 operation(s) for bucketing api.
DevCycle Custom Properties API
The Custom Properties API from DevCycle — 2 operation(s) for custom properties.
DevCycle [Deprecated] Features v1 API
The [Deprecated] Features v1 API from DevCycle — 7 operation(s) for [deprecated] features v1.
DevCycle EdgeDB API
The EdgeDB API from DevCycle — 1 operation(s) for edgedb.
DevCycle Environments API
The Environments API from DevCycle — 4 operation(s) for environments.
DevCycle Feature Change Requests API
The Feature Change Requests API from DevCycle — 7 operation(s) for feature change requests.
DevCycle Feature Configurations API
The Feature Configurations API from DevCycle — 1 operation(s) for feature configurations.
DevCycle Feature Opt-in API
The Feature Opt-in API from DevCycle — 2 operation(s) for feature opt-in.
DevCycle Features v2 API
The Features v2 API from DevCycle — 6 operation(s) for features v2.
DevCycle Integrations: Dynatrace API
The Integrations: Dynatrace API from DevCycle — 2 operation(s) for integrations: dynatrace.
DevCycle Integrations: Jira API
The Integrations: Jira API from DevCycle — 3 operation(s) for integrations: jira.
DevCycle Metric Associations API
The Metric Associations API from DevCycle — 1 operation(s) for metric associations.
DevCycle Metrics API
The Metrics API from DevCycle — 4 operation(s) for metrics.
DevCycle OpenFeature Remote Evaluation API (OFREP) API
See the OpenFeature documentation for more information: https://github.com/open-feature/protocol
DevCycle Overrides API
The Overrides API from DevCycle — 3 operation(s) for overrides.
DevCycle Project Change Requests API
The Project Change Requests API from DevCycle — 1 operation(s) for project change requests.
DevCycle Projects API
The Projects API from DevCycle — 5 operation(s) for projects.
DevCycle Results API
The Results API from DevCycle — 3 operation(s) for results.
DevCycle User Profiles API
The User Profiles API from DevCycle — 1 operation(s) for user profiles.
DevCycle Variables API
The Variables API from DevCycle — 3 operation(s) for variables.
DevCycle Variations API
The Variations API from DevCycle — 2 operation(s) for variations.
DevCycle Webhooks API
The Webhooks API from DevCycle — 2 operation(s) for webhooks.
Scroll within the panel for all 25 ·
Arazzo Workflows 3
Real integrations are rarely a single call. Arazzo describes the multi-step sequences — auth, then create, then confirm — so both a human and an agent can follow the choreography, not just the endpoints.
Multi-step API workflows described with the Arazzo specification.
_Index
ARAZZODevCycle - create a feature with a variable and variation
Create a feature flag, a variable, and a variation via the DevCycle Management API.
ARAZZODevCycle - evaluate feature flags for a user (Bucketing API)
Fetch all variables and features for a user context and report an event.
ARAZZOMCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
devcycle-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Devcycle Webhooks
ASYNCAPISecurity 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 DevCycle — 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 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 5
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 8
Pagination, idempotency, versioning, errors, and events
Scroll within the panel for all 8 ·
Build 4
SDKs, sample code, and the tooling you integrate with
Access & Security 7
Authentication, authorization, and security posture
Scroll within the panel for all 7 ·
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/devcycle · machine-readable index on apis.io