Apifare Providers MCP Server

apifare-providers

The open provider registry (APIFARE WO Part B4): community-submitted provider manifests for the apifare gateway. The GATEWAY stays closed until the Verdict Gate; this repo opens only the MANIFEST format.

Manifest format (v1)

One JSON file per provider under providers/:

{
  "slug": "example",
  "name": "Example API",
  "baseUrl": "https://api.example.com",
  "auth": { "kind": "bearer" },
  "pricing": { "kind": "per-request", "credits": 0.3 },
  "keySource": "MASTER | VAULT",
  "legalityNote": "REQUIRED — path to a legality/<slug>.md in this repo analyzing resale terms",
  "docs": "https://docs.example.com"
}

auth kinds: bearer | basic | header{header,prefix?} | query{param} — mirrors the gateway proxy registry. pricing kinds: per-request | apify-run | none{requestCapPerDay}.

Rules (PR template + CI enforce)

1. legalityNote file is REQUIRED — no manifest merges without a written resale/terms analysis.
2. Prices follow pricing v2: the listed number IS the billed number.
3. MASTER submissions need the provider's written resale permission linked; VAULT submissions don't (user's own key).
4. CI gate: schema validation + legality-file presence + no secrets.
5. Merge ≠ deployment: the apifare team imports merged manifests into the gateway registry on its own review cadence.