openfeature.dev valid

OpenFeature

OpenFeature is a vendor-neutral, community-driven specification for feature flagging.

For agents: OpenFeature: vendor-neutral, community feature flagging specification with docs on the evaluation API, providers, hooks and a five-minute tutorial.

feature flagsopenfeaturefeature flagging specificationevaluation apiproviders

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T02:12:24.949Z. Cached copy · Source on openfeature.dev

# OpenFeature

> OpenFeature is a vendor-neutral, community-driven specification for feature flagging.
> This index points coding agents and language models to the project's primary documentation and ecosystem resources.

## Start here

- [OpenFeature documentation](https://openfeature.dev/docs/reference/intro): Learn the core concepts and how OpenFeature fits into a feature flagging system.
- [Five minutes to feature flags](https://openfeature.dev/docs/tutorials/five-minutes-to-feature-flags): Follow a short, practical introduction to evaluating feature flags with OpenFeature.
- [OpenFeature specification](https://openfeature.dev/specification): Read the normative API, evaluation context, provider, hook, and event definitions.

## Concepts

- [Evaluation API](https://openfeature.dev/docs/reference/concepts/evaluation-api): Learn how to evaluate feature flags and retrieve evaluation details.
- [Providers](https://openfeature.dev/docs/reference/concepts/provider): Understand how providers connect the OpenFeature API to a feature flag management system.
- [Evaluation context](https://openfeature.dev/docs/reference/concepts/evaluation-context): Supply contextual data for targeting and dynamic flag evaluation.
- [Hooks](https://openfeature.dev/docs/reference/concepts/hooks): Learn how hooks add behavior before, during, and after flag evaluation.
- [Events](https://openfeature.dev/docs/reference/concepts/events): React to provider readiness, errors, and flag configuration changes.
- [SDK paradigms](https://openfeature.dev/docs/reference/concepts/sdk-paradigms): Compare the design patterns shared across OpenFeature SDKs.
- [Tracking](https://openfeature.dev/docs/reference/concepts/tracking): Associate user actions and metrics with flag evaluation contexts for experimentation.

## Getting started by language

- [.NET and ASP.NET Core](https://openfeature.dev/docs/tutorials/getting-started/dotnet): Integrate the .NET SDK into an ASP.NET Core application.
- [Go and Gin](https://openfeature.dev/docs/tutorials/getting-started/go): Integrate the Go SDK into a Gin application.
- [JavaScript and Express](https://openfeature.dev/docs/tutorials/getting-started/node): Integrate the JavaScript SDK into an Express application using JavaScript or TypeScript.
- [Java and Spring Boot](https://openfeature.dev/docs/tutorials/getting-started/java/spring-boot): Integrate the Java SDK into a Spring Boot application.
- [Java and Dropwizard](https://openfeature.dev/docs/tutorials/getting-started/java/dropwizard): Integrate the Java SDK into a Dropwizard application.
- [PHP and Laravel](https://openfeature.dev/docs/tutorials/getting-started/php): Integrate the PHP SDK into a Laravel application.
- [Python and Flask](https://openfeature.dev/docs/tutorials/getting-started/python): Integrate the Python SDK into a Flask application.
- [Rust and Axum](https://openfeature.dev/docs/tutorials/getting-started/rust): Integrate the Rust SDK into an Axum application.

## SDKs and integra
…

Related sites

Other listed sites in Developer tools. See the whole category →

Machine-readable: GET /v1/resolve?q=openfeature.dev · GET /v1/domain/openfeature.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for openfeature.dev:
1. POST https://agentwebmap.com/v1/sites/openfeature.dev/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://openfeature.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/openfeature.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/openfeature.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.