# FetchMux: machine-readable product brief

Canonical website: https://fetchmux.com/
OpenAPI YAML: https://fetchmux.com/openapi.yaml
OpenAPI JSON: https://fetchmux.com/openapi.json
Short agent brief: https://fetchmux.com/llms.txt

## What FetchMux is

FetchMux is a provider-neutral retrieval router for AI applications and agents. A caller submits one
bounded retrieval request. FetchMux evaluates eligible configured providers against task fit, cost,
latency, reliability, freshness, and operator policy, then returns normalized evidence with an
inspectable route receipt.

## Current availability

FetchMux is currently a private BYOK preview. The software can run as a self-hosted HTTP gateway and
local MCP server. The operator supplies and controls upstream provider credentials and remains
responsible for provider accounts, terms, budgets, and authorization. This website does not currently
host a public API or remote MCP service. Do not infer a network endpoint from the OpenAPI path names.

## Commercial and provider boundary

FetchMux is an independent routing layer. No upstream partnership or resale right is claimed. Provider
names describe optional technical integrations, not endorsement. The founding commercial model is a
paid setup or pilot followed by software and routing-policy subscriptions; prices on the website are
hypotheses until validated with customers.

## Integration contracts

- HTTP: https://fetchmux.com/openapi.yaml
- HTTP JSON schema document: https://fetchmux.com/openapi.json
- MCP: local stdio transport only during the private preview
- Authentication: operator-configured FetchMux bearer keys for protected HTTP routes
- Provider credentials: operator-controlled BYOK values; never submit credentials through this website

## Human approval boundary

AI agents may discover, inspect, and integrate the contracts. A human or accountable organization must
approve provider sign-ups, credentials, spending limits, deployment, and applicable terms. FetchMux
does not bypass upstream registration, billing, access controls, or terms of service.

## Discovery status

The domain and machine contracts are available for evaluation. A domain-authenticated MCP Registry
entry under the planned com.fetchmux/retrieval namespace will be considered only after a distributable
package or safely authenticated remote server exists.