Public AI provider catalog: providers, models, and offerings with pricing, capabilities, and freshness metadata. Consumed by fusionAIze products (Gate, Grid, Lens, Fabric) and any community tool that wants a curated catalog of LLM provider data.
Looking for product-specific overlays, routing heuristics or operator packages? Those live in the private companion repo fusionaize-metadata (access by request).
fusionaize-metadata-public/
README.md
LICENSE
schemas/
provider-catalog.v1.schema.json
model-catalog.v1.schema.json
offering-catalog.v1.schema.json
providers/
catalog.v1.json # Provider entries (Anthropic, OpenAI, DeepSeek, …)
sources.v1.json # Source tracking & freshness metadata
models/
catalog.v1.json # Model definitions with capability matrix
offerings/
catalog.v1.json # Concrete model × provider × pricing offerings
Per-provider metadata: pricing rates per 1M tokens, recommended model,
aliases, volatility flags, evidence level, signup/source URLs, freshness
status, and tier info (active, deprecated, expired, preview).
Model-level definitions: canonical IDs, display names, families, capabilities (context window, modalities, tool support, JSON mode), typical use cases.
Concrete offerings — the cartesian product of model_id × provider_id
with pricing, region, and availability per offering.
Endpoint URLs and freshness/check-tracking for the provider source pages that catalog editors monitor.
curl -fsSL https://raw.githubusercontent.com/fusionAIze/fusionaize-metadata-public/main/providers/catalog.v1.jsongit clone https://github.com/fusionAIze/fusionaize-metadata-public.git
export FAIGATE_PROVIDER_METADATA_DIR=$(pwd)/fusionaize-metadata-publicfaigate's upcoming MetadataCatalogSync pulls this catalog over HTTPS
with If-None-Match/ETag conditional GET, caches at
~/.cache/faigate/metadata/, falls back to a bundled default. See the
faigate repo's docs/CATALOG-UPDATER.md for setup.
Each catalog file declares its own schema_version. Schemas live in
schemas/. Versioning is additive within a major version: minor bumps
add optional fields without breaking older consumers.
- CI Validation: JSON syntax + duplicate-ID checks on every push
- CodeQL: security scanning over JSON/YAML
- Security Audit: gitleaks scan for secrets
- Scheduled refresh: weekly validation cron
To update pricing, models, or providers:
- Edit the relevant
catalog.v1.jsonfile - Bump
last_reviewedto today - Bump
pricing.refreshed_atif pricing changed - Open a PR — CI will validate JSON + duplicate IDs
- Merge → consumers refresh on their next sync (default 24h)
PRs welcome for:
- Pricing corrections (cite the provider's pricing page in the PR body)
- New providers / models / offerings
- Schema improvements (must remain backward compatible)
Out of scope: routing heuristics, evaluations, scoring rationale, operator-specific quotas — those belong in the private companion repo.
Apache-2.0 — see LICENSE.