Featureflip

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 10 APIs on the APIs.io network, including Client SDK API, Environments API, Feature Flags API, and 7 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 21 more developer resources.

51.7/100 developing ▬ flat Agent 36/100 agent ready Front door AI 5/6 prominent Full breakdown ↓
scored 2026-09-25 · rubric v0.23.0
4 APIs 1 MCP Servers
Feature FlagsFeature Managementfeature flag cleanupProgressive DeliveryExperimentationfeature flags as codeOpenFeatureMCPDeveloper ToolsDevOps/CI-CD

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-25 · rubric v0.23.0
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/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/featureflip: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 10

Individual APIs this provider publishes, each with its own machine-readable definition.

MCP Server (local)

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.

Featureflip Client SDK API

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...

Featureflip Environments API

Environments within a resolved organization + project — one level deeper than ProjectsController. Every route here carries `{org}`, so ResolveTenantFilter has already resolved +...

Featureflip Feature Flags API

Feature flags within a resolved organization + project — mirrors EnvironmentsController's resolve-then-dispatch shape one level deeper. `{project}` is resolved key-or-guid, scop...

Featureflip Me API

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...

Featureflip Organizations API

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...

Featureflip Projects API

Projects within a resolved organization. Every route here carries `{org}`, so ResolveTenantFilter has already resolved + access-checked it before any action runs — dispatched co...

Featureflip SDK Keys API

SDK keys within a resolved organization + project + environment — one level deeper than EnvironmentsController. Every action resolves `{project}` (key-or-guid, scoped to the res...

Featureflip Server SDK API

SDK endpoints for feature flag evaluation and configuration retrieval. All endpoints require a valid SDK key passed via the Authorization header.

Featureflip User Segments API

User segments within a resolved organization + project — mirrors EnvironmentsController's resolve-then-dispatch shape one level deeper. `{project}` is resolved key-or-guid, scop...

Scroll for all 10

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Featureflip MCP Server

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...

MCP SERVER

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Featureflip Rate Limits

0 limits

RATE LIMITS

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Featureflip API Rules

0 rules ·

SPECTRAL

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Featureflip Authentication

apiKey · 1 scheme

SECURITY

Featureflip Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Scroll for all 7

Build 3

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

Commercial 4

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Other 2

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
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
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://api.featureflip.io
  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://api.featureflip.io
  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/
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: 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/
x-enrichment:
  date: '2026-09-13'
  status: enriched
  artifacts_added: 24
  pass: local-v3

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/featureflip"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/featureflip/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/featureflip/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

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.

A second provider on the same verified email joins the account you already have.