Jentic publishes the only available OpenAPI specification for LaunchDarkly REST API, keeping it validated and agent-ready. The LaunchDarkly REST API (v2) covers feature flag and experimentation management — projects, environments, feature flags, segments, contexts, AI Configs, approvals, audit logs, code references, account members, custom roles, applications, and Data Export destinations. It is the platform-wide control plane for releasing software safely behind flags and running experiments. The spec covers 355 operations across the entire LaunchDarkly product surface.
355 endpointsJentic publishes the only available OpenAPI specification for LaunchDarkly REST API, keeping it validated and agent-ready. This 5.3.0 cut of the LaunchDarkly REST API covers the core feature flag and experimentation surface — projects, environments, feature flags, segments, account members, custom roles, audit logs, Data Export destinations, and webhooks. It is the management plane for releasing software safely behind flags. The spec covers 105 operations across the platform's foundational resources.
105 endpointsJentic publishes the only available OpenAPI specification for LaunchDarkly REST API, keeping it validated and agent-ready. This 5.3.0 cut of the LaunchDarkly REST API covers the core feature flag and experimentation surface — projects, environments, feature flags, segments, account members, custom roles, audit logs, Data Export destinations, and webhooks. It is the management plane for releasing software safely behind flags. The spec covers 105 operations across LaunchDarkly's foundational resources.
105 endpointsStep 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.