Feature flag platform with automated dead-flag cleanup (via a GitHub Action), flat pricing, and API-first, agent-native surfaces. Exposes a Management REST API and a high-performance Evaluation API, both with public OpenAPI contracts, plus official SDKs for 13 languages, OpenFeature providers, a Terraform provider, and a local MCP server.
Featureflip publishes 11 API contracts indexed on the APIs.io network, including Client SDK API, Environments API, Feature Flags API, and 8 more. Tagged areas include Feature Flags, Feature Management, feature flag cleanup, Progressive Delivery, and Experimentation.
The Featureflip catalog on APIs.io includes 1 Spectral governance ruleset.
Featureflip’s developer surface includes authentication, changelog, documentation, getting-started guide, pricing, engineering blog, support, and 26 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Horizontal (data, software, accessibility, platform) regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it
carries 10 points of the composite. It is scored from the published contracts
themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already
holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in
front of it, and the first time that check is skipped a duplicate record is created.
Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet,
not penalised by it.
The six quality facets above are damped to 75 points between them,
because the conditional facet above carries the other
25. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 75% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/featureflip/"><img src="https://apis.io/badge/featureflip/card.svg" alt="Featureflip on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
Delegated User Identity+6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented) Ask about this →
Typed Event Surface+6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks Ask about this →
6 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.
Not sure how this applies to your stack? Ask about any one item. Kin Lane reads every question, looks at your profile and your situation, and replies with what a fix would take — scoped to that one area, priced up front, yours whether you ship it or not. Ask a question →
The Kin Score Market layer reads a provider inside its market:
its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted:
not part of the Kin Score or agent readiness.
Registered MCP server and declares compatibility are report only — not weighted.
Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
Client SDK endpoints for browser-side feature flag evaluation. All endpoints require a valid Client SDK key passed via the Authorization header. Unlike server SDK endpoints, the...
Environments within a resolved organization + project — one level deeper than ProjectsController. Every route here carries `{org}`, so ResolveTenantFilter has already resolved +...
The caller's own identity. This route has no `{org}` segment, so ResolveTenantFilter is a pass-through here — the caller is read entirely from the authenticated principal (via G...
The caller's organizations. `List` has no `{org}` segment (pass-through tenant filter) and dispatches ListOrganizationsQuery, which already scopes to the caller's own membership...
Projects within a resolved organization. Every route here carries `{org}`, so ResolveTenantFilter has already resolved + access-checked it before any action runs — dispatched co...
SDK keys within a resolved organization + project + environment — one level deeper than EnvironmentsController. Every action resolves `{project}` (key-or-guid, scoped to the res...
User segments within a resolved organization + project — mirrors EnvironmentsController's resolve-then-dispatch shape one level deeper. `{project}` is resolved key-or-guid, scop...
Manage outbound webhook subscriptions: where configuration-change events are sent, which events and projects they cover, their signing secrets, and their delivery log.
Local Model Context Protocol server that lets AI agents (Claude Code, Cursor, etc.) manage Featureflip flags by calling the Management API on the caller's behalf. It manages fla...
Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.
name: Featureflip
description: Feature flag platform with automated dead-flag cleanup (via a GitHub Action), flat pricing, and API-first, agent-native
surfaces. Exposes a Management REST API and a high-performance Evaluation API, both with public OpenAPI contracts, plus
official SDKs for 13 languages, OpenFeature providers, a Terraform provider, and a local MCP server.
url: https://raw.githubusercontent.com/api-evangelist/featureflip/refs/heads/main/apis.yml
accessModel:
pricing: freemium
onboarding: self-serve
trial: false
try_now: true
public: false
gated: none
gated_source:
- onboarding
label: Freemium · Self-serve signup
confidence: high
source:
- plans
- authentication
- rate-limits
- security
generated: '2026-11-13'
method: derived
created: '2026-09-12'
modified: '2026-09-13'
specificationVersion: '0.21'
tags:
- Feature Flags
- Feature Management
- feature flag cleanup
- Progressive Delivery
- Experimentation
- feature flags as code
- OpenFeature
- MCP
- Developer Tools
- DevOps/CI-CD
tags_raw:
- feature flags
- feature management
- feature flag cleanup
- progressive delivery
- experimentation
- feature flags as code
- OpenFeature
- MCP
- developer tools
- DevOps/CI-CD
apis:
- name: MCP Server (local)
description: Documentation for the @featureflip/mcp server, a local stdio process run via npx that calls the Management
API on your behalf using a bearer token.
humanURL: https://featureflip.io/docs/integrations/mcp/
baseURL: https://featureflip.io/docs/integrations/mcp/
tags:
- Feature Flags
- Feature Management
- feature flag cleanup
- Progressive Delivery
- Experimentation
- feature flags as code
- OpenFeature
- MCP
- Developer Tools
- DevOps/CI-CD
tags_raw:
- feature flags
- feature management
- feature flag cleanup
- progressive delivery
- experimentation
- feature flags as code
- OpenFeature
- MCP
- developer tools
- DevOps/CI-CD
properties:
- type: Documentation
url: https://featureflip.io/docs/integrations/mcp/
- type: MCPServer
url: mcp/featureflip-mcp.yml
- type: ToolCrosswalk
url: mcp/featureflip-tool-crosswalk.yml
- aid: featureflip:featureflip-client-sdk-api
name: Featureflip Client SDK API
description: 'Client SDK endpoints for browser-side feature flag evaluation.
All endpoints require a valid Client SDK key passed via the Authorization header.
Unlike server SDK endpoints, these evaluate flags server-side and return only values.'
humanURL: https://featureflip.io/docs/management-api/overview/
baseURL: https://eval.featureflip.io
baseurl_source: contract
tags:
- Client SDK
properties:
- type: OpenAPI
url: openapi/featureflip-client-sdk-api-openapi.yml
- type: APIReference
url: https://featureflip.io/docs/management-api/reference/
- type: Documentation
url: https://featureflip.io/docs/management-api/reference/
- type: Documentation
url: https://featureflip.io/docs/management-api/authentication/
- type: LLMsTxt
url: https://featureflip.io/llms.txt
- type: APIReference
url: https://featureflip.io/docs/api/reference/
- type: Documentation
url: https://featureflip.io/docs/api/reference/
- aid: featureflip:featureflip-environments-api
name: Featureflip Environments API
description: 'Environments within a resolved organization + project — one level deeper than
ProjectsController. Every route here carries `{org}`, so
ResolveTenantFilter has already resolved + access-checked
it before any action runs. `{project}` is resolved key-or-guid, scoped to the resolved
org, via ResolveProjectIdAsync for every action (list
needs it too, unlike ProjectsController''s org-only list). `{env}`
(get/update/delete) is then resolved key-or-guid, scoped to the resolved project, via
ResolveEnvironmentIdAsync. Dispatched commands/queries
always use the resolved GUIDs, never the raw route strings. Writes (create/update/delete)
require at least Member (RequireRole);
a Viewer attempting one gets a 403 `forbidden` envelope. Deleting a project''s last
environment surfaces the existing `LAST_ENVIRONMENT` guard
(DeleteEnvironmentCommandHandler) as-is — it throws the custom
ValidationException, which
PublicApiExceptionFilterAttribute maps to a 400
`validation_failed` envelope automatically, so Delete doesn''t special-case it.
ListEnvironmentsQuery has no `Skip`/`Take` (unlike
`ListProjectsQuery`) — a project''s environment count is small, so List
fetches the full set and paginates in-memory to still expose the standard cursor contract.'
humanURL: https://featureflip.io/docs/management-api/overview/
baseURL: https://api.featureflip.io
tags:
- Environment
tags_raw:
- Environments
properties:
- type: OpenAPI
url: openapi/featureflip-environments-api-openapi.yml
- type: APIReference
url: https://featureflip.io/docs/management-api/reference/
- type: Documentation
url: https://featureflip.io/docs/management-api/reference/
- type: Documentation
url: https://featureflip.io/docs/management-api/authentication/
- type: LLMsTxt
url: https://featureflip.io/llms.txt
- type: APIReference
url: https://featureflip.io/docs/api/reference/
- type: Documentation
url: https://featureflip.io/docs/api/reference/
- aid: featureflip:featureflip-feature-flags-api
name: Featureflip Feature Flags API
description: 'Feature flags within a resolved organization + project — mirrors
EnvironmentsController''s resolve-then-dispatch shape one level deeper.
`{project}` is resolved key-or-guid, scoped to the resolved org (with the service-token
project allowlist forwarded), via ResolveProjectIdAsync
for every action. `{flag}` (get/update/archive/restore/delete) is then resolved
key-or-guid, scoped to the resolved project, via
ResolveFlagIdAsync. Dispatched commands/queries always
use the resolved GUIDs, never the raw route strings. Writes (create/update/archive/restore/
delete) require at least Member
(RequireRole); a Viewer attempting one gets a 403
`forbidden` envelope. Flag deletion/variation-removal guards (`FLAG_HAS_DEPENDENTS`,
plan limits on create, etc.) surface as-is via the existing handlers'' custom
ValidationException, which
PublicApiExceptionFilterAttribute maps to a 400 `validation_failed`
envelope automatically — no action here special-cases them. Defers flag *runtime config*
(env-config, toggle, targeting rules, prerequisites) and variations to their own controllers
(phase 3b Task 3 / phase 3c).'
humanURL: https://featureflip.io/docs/management-api/overview/
baseURL: https://api.featureflip.io
tags:
- Feature Flags
properties:
- type: OpenAPI
url: openapi/featureflip-feature-flags-api-openapi.yml
- type: APIReference
url: https://featureflip.io/docs/management-api/reference/
- type: Documentation
url: https://featureflip.io/docs/management-api/reference/
- type: Documentation
url: https://featureflip.io/docs/management-api/authentication/
- type: LLMsTxt
url: https://featureflip.io/llms.txt
- type: APIReference
url: https://featureflip.io/docs/api/reference/
- type: Documentation
url: https://featureflip.io/docs/api/reference/
- aid: featureflip:featureflip-me-api
name: Featureflip Me API
description: 'The caller''s own identity. This route has no `{org}` segment, so
ResolveTenantFilter is a pass-through here — the caller
is read entirely from the authenticated principal (via GetCurrentUserQuery for a
user/PAT, or directly from claims for a service token), never from
ResolvedOrgId.'
humanURL: https://featureflip.io/docs/management-api/overview/
baseURL: https://api.featureflip.io
tags:
- Me
properties:
- type: OpenAPI
url: openapi/featureflip-me-api-openapi.yml
- type: APIReference
url: https://featureflip.io/docs/management-api/reference/
- type: Documentation
url: https://featureflip.io/docs/management-api/reference/
- type: Documentation
url: https://featureflip.io/docs/management-api/authentication/
- type: LLMsTxt
url: https://featureflip.io/llms.txt
- type: APIReference
url: https://featureflip.io/docs/api/reference/
- type: Documentation
url: https://featureflip.io/docs/api/reference/
- aid: featureflip:featureflip-organizations-api
name: Featureflip Organizations API
description: 'The caller''s organizations. `List` has no `{org}` segment (pass-through tenant
filter) and dispatches ListOrganizationsQuery, which already scopes to the
caller''s own memberships. `Get` carries `{org}`, so
ResolveTenantFilter resolves + access-checks it first —
the action dispatches GetOrganizationQuery with the resolved GUID
(ResolvedOrgId), never the raw route string.'
humanURL: https://featureflip.io/docs/management-api/overview/
baseURL: https://api.featureflip.io
tags:
- Organization
tags_raw:
- Organizations
properties:
- type: OpenAPI
url: openapi/featureflip-organizations-api-openapi.yml
- type: APIReference
url: https://featureflip.io/docs/management-api/reference/
- type: Documentation
url: https://featureflip.io/docs/management-api/reference/
- type: Documentation
url: https://featureflip.io/docs/management-api/authentication/
- type: LLMsTxt
url: https://featureflip.io/llms.txt
- type: APIReference
url: https://featureflip.io/docs/api/reference/
- type: Documentation
url: https://featureflip.io/docs/api/reference/
- aid: featureflip:featureflip-projects-api
name: Featureflip Projects API
description: 'Projects within a resolved organization. Every route here carries `{org}`, so
ResolveTenantFilter has already resolved + access-checked
it before any action runs — dispatched commands/queries always use
ResolvedOrgId, never the raw route string.
`{project}` (get/update/delete) is resolved key-or-guid, scoped to the resolved org, via
ResolveProjectIdAsync — same addressing pattern as
OrganizationsController uses for `{org}`. Writes (create/update/delete)
require at least Member
(RequireRole); a Viewer attempting one gets a 403
`forbidden` envelope.'
humanURL: https://featureflip.io/docs/management-api/overview/
baseURL: https://api.featureflip.io
tags:
- Project
tags_raw:
- Projects
properties:
- type: OpenAPI
url: openapi/featureflip-projects-api-openapi.yml
- type: APIReference
url: https://featureflip.io/docs/management-api/reference/
- type: Documentation
url: https://featureflip.io/docs/management-api/reference/
- type: Documentation
url: https://featureflip.io/docs/management-api/authentication/
- type: LLMsTxt
url: https://featureflip.io/llms.txt
- type: APIReference
url: https://featureflip.io/docs/api/reference/
- type: Documentation
url: https://featureflip.io/docs/api/reference/
- aid: featureflip:featureflip-sdk-keys-api
name: Featureflip SDK Keys API
description: 'SDK keys within a resolved organization + project + environment — one level deeper than
EnvironmentsController. Every action resolves `{project}` (key-or-guid,
scoped to the resolved org, with the service-token project allowlist forwarded) then
`{env}` (key-or-guid, scoped to the resolved project) via
IPublicApiTenantResolver, mirroring FeatureFlagsController''s
resolve-then-dispatch shape. Unlike `{project}`/`{env}`, `{sdkKey}` is
guid-only — SDK keys have no key/slug of their own — resolved via
ResolveSdkKeyIdAsync, which throws the same
not-found error for a non-guid segment as a genuinely missing key. Writes
(create/update/revoke) require at least Member
(RequireRole); a Viewer attempting one gets a 403
`forbidden` envelope.
Type is a bare string on the wire; Create
parses it to SdkKeyType against a NAME allowlist
(`Enum.TryParse` + `Enum.GetNames().Contains(...)`) rather than a bare
`Enum.TryParse`/`Enum.IsDefined` pair — the latter would silently accept a numeric
string (e.g. `"0"`) and resolve it to the first enum member. An unrecognized value throws
the custom ValidationException BEFORE the environment is resolved or any command
is dispatched, mapped to a 400 `validation_failed` envelope by
PublicApiExceptionFilterAttribute — same pattern as
MapConditions''s operator parse.
The plaintext key returned by CreateSdkKeyResult is a one-time value — it is
never recoverable afterward, so unlike Create''s
re-fetch-after-write pattern, Create builds its response directly from the
command result rather than dispatching a follow-up query. List and
Get return PublicSdkKeyResponse, which carries only
`LastFourCharacters` — never the plaintext.'
humanURL: https://featureflip.io/docs/management-api/overview/
baseURL: https://api.featureflip.io
tags:
- SDK Keys
properties:
- type: OpenAPI
url: openapi/featureflip-sdk-keys-api-openapi.yml
- type: APIReference
url: https://featureflip.io/docs/management-api/reference/
- type: Documentation
url: https://featureflip.io/docs/management-api/reference/
- type: Documentation
url: https://featureflip.io/docs/management-api/authentication/
- type: LLMsTxt
url: https://featureflip.io/llms.txt
- type: APIReference
url: https://featureflip.io/docs/api/reference/
- type: Documentation
url: https://featureflip.io/docs/api/reference/
- aid: featureflip:featureflip-server-sdk-api
name: Featureflip Server SDK API
description: 'SDK endpoints for feature flag evaluation and configuration retrieval.
All endpoints require a valid SDK key passed via the Authorization header.'
humanURL: https://featureflip.io/docs/management-api/overview/
baseURL: https://eval.featureflip.io
baseurl_source: contract
tags:
- Server SDK
properties:
- type: OpenAPI
url: openapi/featureflip-server-sdk-api-openapi.yml
- type: APIReference
url: https://featureflip.io/docs/management-api/reference/
- type: Documentation
url: https://featureflip.io/docs/management-api/reference/
- type: Documentation
url: https://featureflip.io/docs/management-api/authentication/
- type: LLMsTxt
url: https://featureflip.io/llms.txt
- type: APIReference
url: https://featureflip.io/docs/api/reference/
- type: Documentation
url: https://featureflip.io/docs/api/reference/
- aid: featureflip:featureflip-user-segments-api
name: Featureflip User Segments API
description: 'User segments within a resolved organization + project — mirrors
EnvironmentsController''s resolve-then-dispatch shape one level deeper.
`{project}` is resolved key-or-guid, scoped to the resolved org (with the service-token
project allowlist forwarded), via ResolveProjectIdAsync
for every action. `{segment}` (get/update/delete) is then resolved key-or-guid, scoped to
the resolved project, via ResolveSegmentIdAsync.
Dispatched commands/queries always use the resolved GUIDs, never the raw route strings. Writes
(create/update/delete) require at least Member
(RequireRole); a Viewer attempting one gets a 403
`forbidden` envelope.
There is no `GetUserSegmentQuery` — Get resolves `{segment}` then
dispatches ListUserSegmentsQuery and finds the match in-memory, throwing
NotFoundException if absent. This keeps the task scoped to the public layer with
no new Application handler: the resolver has already validated the id exists within the
project, and a project''s segment set is bounded (unlike flags/environments'' own list, this
never needs true server-side pagination for the lookup).
Operator is a bare string on the wire; write actions
parse it to OperatorType via TryParse``1(ReadOnlySpan{Char},Boolean,``0@)
(case-insensitive). An unrecognized value throws the custom
ValidationException BEFORE any command is dispatched — mapped to a 400
`validation_failed` envelope by PublicApiExceptionFilterAttribute, same as
every other handler-thrown validation failure on this surface.'
humanURL: https://featureflip.io/docs/management-api/overview/
baseURL: https://api.featureflip.io
tags:
- User Segments
properties:
- type: OpenAPI
url: openapi/featureflip-user-segments-api-openapi.yml
- type: APIReference
url: https://featureflip.io/docs/management-api/reference/
- type: Documentation
url: https://featureflip.io/docs/management-api/reference/
- type: Documentation
url: https://featureflip.io/docs/management-api/authentication/
- type: LLMsTxt
url: https://featureflip.io/llms.txt
- type: APIReference
url: https://featureflip.io/docs/api/reference/
- type: Documentation
url: https://featureflip.io/docs/api/reference/
- aid: featureflip:featureflip-webhooks-api
name: Featureflip Webhooks API
description: 'Manage outbound webhook subscriptions: where configuration-change events are sent, which
events and projects they cover, their signing secrets, and their delivery log.'
humanURL: https://featureflip.io/docs/integrations/mcp/
baseURL: https://featureflip.io/docs/integrations/mcp/
tags:
- Webhook
tags_raw:
- Webhooks
properties:
- type: OpenAPI
url: openapi/featureflip-webhooks-api-openapi.yml
maintainers:
- FN: Featureflip
email: contact@featureflip.io
url: https://featureflip.io/
generated:
by: apis.io/add
model: claude-opus-4-8
confidence: 97
at: '2026-09-12T04:54:28.200Z'
common:
- type: CapabilityMap
url: capabilities/featureflip-capability-edges.yml
name: Featureflip Business Capability Map
- type: Overlay
url: overlays/featureflip-management-overlay.yaml
- type: Overlay
url: overlays/featureflip-evaluation-overlay.yaml
- type: Website
url: https://featureflip.io/
- type: Authentication
url: authentication/featureflip-authentication.yml
- type: DomainSecurity
url: security/featureflip-domain-security.yml
- type: Packages
url: packages/featureflip-packages.yml
- type: SDKs
url: packages/featureflip-packages.yml
- type: Conventions
url: conventions/featureflip-conventions.yml
- type: Idempotency
url: conventions/featureflip-conventions.yml
- type: RateLimits
url: rate-limits/featureflip-rate-limits.yml
- type: Plans
url: plans/featureflip-plans-pricing.yml
- type: ChangeLog
url: changelog/featureflip-changelog.yml
- type: Lifecycle
url: lifecycle/featureflip-lifecycle.yml
- type: ErrorCatalog
url: errors/featureflip-problem-types.yml
- type: DataModel
url: data-model/featureflip-data-model.yml
- type: Conformance
url: conformance/featureflip-conformance.yml
- type: AgentSkill
url: skills/_index.yml
- type: Rules
url: rules/featureflip-spectral.yaml
- type: Documentation
url: https://featureflip.io/docs/
- type: DeveloperPortal
url: https://featureflip.io/docs/
- type: GettingStarted
url: https://featureflip.io/docs/quickstart/javascript/
- type: Pricing
url: https://featureflip.io/pricing/
- type: Blog
url: https://featureflip.io/blog/
- type: Support
url: https://featureflip.io/contact/
- type: SignUp
url: https://app.featureflip.io/signup
- type: GitHubOrganization
url: https://github.com/canopy-labs
- type: TermsOfService
url: https://featureflip.io/terms/
- type: PrivacyPolicy
url: https://featureflip.io/privacy/
- type: UsageTerms
url: terms/featureflip-terms-of-service.yml
- type: DataProcessing
url: privacy/featureflip-privacy-policy.yml
- type: Eligibility
url: eligibility/featureflip-eligibility.yml
- type: DataLicense
url: data-license/featureflip-data-license.yml
x-enrichment:
date: '2026-09-13'
status: enriched
artifacts_added: 24
pass: local-v3
Featureflip API — frequently asked questions
Does Featureflip have an API?
Yes. APIs.io lists 11 APIs from Featureflip, including MCP Server (local), Featureflip Client SDK API and Featureflip Environments API, and 8 more.
Is there an OpenAPI specification for the Featureflip API?
Yes. APIs.io indexes 10 OpenAPI specifications for Featureflip, each linked for download from this page.
How do I authenticate with the Featureflip API?
Featureflip uses bearer-token authentication (apiKey · 1 scheme). The details are profiled on APIs.io as Featureflip Authentication.
How much does the Featureflip API cost?
Featureflip publishes its prices; its Free plan is $0/mo as of 2026-10-28. APIs.io lists 8 pricing plans for Featureflip, with each plan's price, limits and inclusions under Pricing on this page.
Does Featureflip have an MCP server?
Yes. APIs.io lists 1 MCP server for Featureflip: Local Model Context Protocol server that lets AI agents (Claude Code, Cursor, etc.) manage Featureflip flags by calling the Management API on the caller's behalf. It manages flag configuration; it doe
Is the Featureflip API ready for AI agents?
Featureflip has a Kin Score of 51.3 out of 100 (developing) and an Agent Readiness score of 35.7 (agent-ready), scored by API Evangelist on 2026-11-13.
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.