quonfig.com valid

Quonfig

Quonfig is a feature-flag and configuration platform that stores config as JSON files in real git repositories instead of a database. Backend SDKs evaluate flags locally in-process (sub-millisecond, no network call), every change is a reviewable git commit with author/diff/timestamp, and you can clone your workspace anytime. Built for the age of AI-written code, where agents create flags far faster than humans retire them.

For agents: Git-native feature flag and config platform with local-evaluation SDKs, JSON configs stored in git, runtime log levels, secrets and LLM prompt management.

feature flagsdynamic configurationgit-native configsecrets managementllm prompts as config

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T15:45:14.197Z. Cached copy · Source on quonfig.com

# Quonfig

> Quonfig is a feature-flag and configuration platform that stores config as JSON files in real git repositories instead of a database. Backend SDKs evaluate flags locally in-process (sub-millisecond, no network call), every change is a reviewable git commit with author/diff/timestamp, and you can clone your workspace anytime. Built for the age of AI-written code, where agents create flags far faster than humans retire them.

- [llms-full.txt](https://quonfig.com/llms-full.txt): full page content in markdown

## Product

- [Feature flags](https://quonfig.com/features/feature-flags): Git-native feature flags. Backend SDKs download full config and evaluate every check locally in-process; changes propagate via SSE in about a second.
- [Dynamic config](https://quonfig.com/features/config): Typed dynamic configuration values stored as JSON in git, changed without a deploy and targeted by cohort.
- [Dynamic log levels](https://quonfig.com/features/log-levels): Change log verbosity at runtime per user or environment, no redeploy, through the same targeting engine.
- [Secret management](https://quonfig.com/features/secrets): Zero-knowledge secrets — encrypted locally with a key you hold; Quonfig never sees the plaintext.
- [AI prompts as config](https://quonfig.com/ai-prompts): Store LLM prompts in Quonfig, version them in git, change them without a deploy, target by cohort, and run `qfg generate` to emit type-safe TypeScript render functions from Mustache templates.
- [For AI agents](https://quonfig.com/agents): Git-native files plus the scriptable `qfg` CLI and OpenFeature give agents a clean, auditable surface for the full flag lifecycle.
- [For developers](https://quonfig.com/developers): Nine native SDKs (Node, Go, Ruby, Python, .NET, Java, Browser JavaScript, React, React Native) and seven OpenFeature providers.
- [Pricing](https://quonfig.com/pricing): Fully public, transparent pricing with a live calculator — roughly 10x cheaper than the major platforms at scale. Free seats and a free open-source mode.

## API & agents

- [REST API](https://api.quonfig.com/v1): Public REST API for flags, config, and segments. Bearer auth with a workspace-scoped API key — `qf_uk_*` for a user, `qf_sa_*` for a service account — and the workspace acted on is inferred from the key.
- [OpenAPI spec](https://app.quonfig.com/public-api/v1/openapi.json): Machine-readable OpenAPI description of every public endpoint.
- [API reference](https://app.quonfig.com/public-api/v1/docs): Browsable HTML reference for the same endpoints.
- [MCP server](https://mcp.quonfig.com/mcp): Model Context Protocol server over Streamable HTTP. Authenticate with a Bearer API key, or with OAuth — protected-resource metadata (RFC 9728) at https://mcp.quonfig.com/.well-known/oauth-protected-resource/mcp, authorization server https://nifty-tint-21.authkit.app.
- [CLI](https://docs.quonfig.com/docs/tools/cli): `npm install -g @quonfig/cli` installs `qfg`, the scriptable client for reading
…

Related sites

Find similar publishers by meaning →

Other listed sites in DevOps and observability. See the whole category →

Machine-readable: GET /v1/resolve?q=quonfig.com · GET /v1/domain/quonfig.com · 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 quonfig.com:
1. POST https://agentwebmap.com/v1/sites/quonfig.com/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://quonfig.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/quonfig.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/quonfig.com).
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.