launchdarkly
LaunchDarkly is a feature management platform that enables development teams to deliver and control software through feature flags, allowing them to test in production and roll out features safely.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles launchdarkly the way a machine reads it — 127 machine-readable artifacts across 27 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 — launchdarkly scores 47.1/100 (developing), with a separate agent-readiness read of 54/100 (agent ready). 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 launchdarkly
Each block below is one kind of artifact we hold for launchdarkly. 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 27
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.
LaunchDarkly Webhooks API
The LaunchDarkly Webhooks API allows developers to build custom integrations that subscribe to activity events within LaunchDarkly. When actions occur such as flag changes, proj...
launchdarkly Access Tokens API
Create and manage personal and service access tokens used to authenticate API requests.
launchdarkly Account Members API
Manage team members, invitations, and member roles within a LaunchDarkly account.
launchdarkly Approvals API
Manage approval requests and workflows for flag changes that require review before deployment.
launchdarkly Audit Log API
Access the change history of all modifications made to resources in the LaunchDarkly account.
launchdarkly Client-Side Evaluation API
Flag evaluation endpoints for client-side and mobile SDKs using environment IDs or mobile keys for authentication.
launchdarkly Client-Side Streaming API
Server-Sent Events streaming endpoints for client-side and mobile SDKs to receive real-time flag updates.
launchdarkly Code References API
View code references that show where feature flags are used in your codebase.
launchdarkly Custom Roles API
Define custom roles with fine-grained permissions using resource specifiers and actions.
launchdarkly Environments API
Manage environments within projects such as production, staging, and development.
launchdarkly Experiments API
Create and manage experiments to measure the impact of feature flag variations on metrics.
launchdarkly Feature Flags API
Create, update, and manage feature flags and their targeting rules across projects and environments.
launchdarkly Flag Triggers API
Create triggers that allow external services to toggle feature flags via unique webhook URLs.
launchdarkly Integration Audit Log Subscriptions API
Manage integrations that subscribe to audit log events and forward them to external tools.
launchdarkly Metrics API
Define and manage metrics used to measure experiment outcomes and feature flag impact.
launchdarkly PHP Polling API
Polling endpoints for PHP server-side SDKs which do not support streaming mode.
launchdarkly Projects API
Manage projects that organize feature flags and other resources.
launchdarkly Relay Proxy Configurations API
Manage automatic configuration entries for LaunchDarkly Relay Proxy instances.
launchdarkly Releases API
Manage release pipelines for coordinating feature flag rollouts across environments.
launchdarkly Segments API
Create and manage user segments for targeting groups of contexts with feature flags.
launchdarkly Server-Side Evaluation API
Flag evaluation endpoints for server-side SDKs using SDK keys for authentication.
launchdarkly Server-Side Streaming API
Server-Sent Events streaming endpoints for server-side SDKs to receive real-time flag updates.
launchdarkly Status API
Health and status monitoring endpoints for the Relay Proxy. No authentication is required for these endpoints.
launchdarkly Tags API
The Tags API from launchdarkly — 1 operation(s) for tags.
launchdarkly Teams API
Organize account members into teams for collaborative flag management and permissions.
launchdarkly Webhooks API
Configure webhooks to receive HTTP POST notifications when changes occur in LaunchDarkly.
launchdarkly Workflows API
Create and manage automated workflows for scheduling and orchestrating flag changes.
Scroll within the panel for all 27 ·
Open Collections 2
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).
LaunchDarkly Relay Proxy
OPEN COLLECTIONLaunchDarkly REST API
OPEN COLLECTIONGraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
LaunchDarkly GraphQL Schema
LaunchDarkly does not publish a native GraphQL API. This is a conceptual GraphQL schema derived from the LaunchDarkly REST API (version 20240415) data model documented at https:...
GRAPHQLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Launchdarkly Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Launchdarkly Finops
FINOPSFeatures 16
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Scroll within the panel for all 16 ·
Event 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.
LaunchDarkly Webhooks Events
LaunchDarkly sends webhook notifications as HTTP POST requests when changes occur within the platform. The webhook payload format is identical to audit log entries and includes ...
ASYNCAPISemantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Launchdarkly Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
launchdarkly API Rules
SPECTRALlaunchdarkly API Rules
SPECTRALJSON Schema 70
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AccessToken
JSON SCHEMAAccessTokenBody
JSON SCHEMAAccessTokens
JSON SCHEMAApprovalRequest
JSON SCHEMAApprovalRequestBody
JSON SCHEMAApprovalRequests
JSON SCHEMAAuditLogEntries
JSON SCHEMAAuditLogEntry
JSON SCHEMAClause
JSON SCHEMACodeReferenceRepositories
JSON SCHEMACustomRole
JSON SCHEMACustomRoleBody
JSON SCHEMACustomRoles
JSON SCHEMAEnvironment
JSON SCHEMAEnvironmentBody
JSON SCHEMAEnvironments
JSON SCHEMAEnvironmentStatus
JSON SCHEMAEvaluationContext
JSON SCHEMAExperiment
JSON SCHEMAExperimentBody
JSON SCHEMAExperiments
JSON SCHEMALaunchDarkly Feature Flag
JSON SCHEMAFeatureFlag
JSON SCHEMAFeatureFlagBody
JSON SCHEMAFeatureFlags
JSON SCHEMAFlagData
JSON SCHEMAFlagEnvironment
JSON SCHEMAFlagEvaluation
JSON SCHEMAFlagEvaluations
JSON SCHEMAFlagTrigger
JSON SCHEMAFlagTriggerBody
JSON SCHEMAFlagTriggers
JSON SCHEMAIntegrationSubscriptions
JSON SCHEMALinks
JSON SCHEMAMember
JSON SCHEMAMemberInviteBody
JSON SCHEMAMembers
JSON SCHEMAMemberSummary
JSON SCHEMAMetric
JSON SCHEMAMetricBody
JSON SCHEMAMetrics
JSON SCHEMAPatchOperation
JSON SCHEMAProject
JSON SCHEMAProjectBody
JSON SCHEMAProjects
JSON SCHEMARelayProxyConfig
JSON SCHEMARelayProxyConfigBody
JSON SCHEMARelayProxyConfigs
JSON SCHEMARelayProxyStatus
JSON SCHEMAReleasePipeline
JSON SCHEMAReleasePipelineBody
JSON SCHEMAReleasePipelines
JSON SCHEMARollout
JSON SCHEMARule
JSON SCHEMASegment
JSON SCHEMASegmentBody
JSON SCHEMASegmentRule
JSON SCHEMASegments
JSON SCHEMAStatement
JSON SCHEMATagCollection
JSON SCHEMATarget
JSON SCHEMATeam
JSON SCHEMATeamBody
JSON SCHEMATeams
JSON SCHEMAVariation
JSON SCHEMALaunchDarkly Webhook Event
JSON SCHEMAWebhook
JSON SCHEMAWebhookBody
JSON SCHEMAWebhooks
JSON SCHEMAWorkflows
JSON SCHEMAScroll within the panel for all 70 ·
JSON Structure 1
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Launchdarkly Structure
JSON STRUCTURESecurity Posture 2
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 launchdarkly — 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.
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 1
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/launchdarkly · machine-readable index on apis.io