Skip to main content
The model catalog is Pangolin’s list of known model ids, which provider type owns them, and token pricing. It is used for:
  • The Known Models picker on a provider’s Models tab
  • Expanding wildcard allows in GET /v1/models
  • Provider selection when more than one attached provider allows the same id
  • Budgets and usage cost, which look up in / out / cache / reasoning rates for a model key
See Model Routing for allow lists, inherit vs select, and how those lists combine with the catalog at request time.

​
Catalog Providers

Default source: https://api.fossorial.io/api/v1/models. Typed AI provider types map as follows: Unmapped types skip Known Models and wildcard expansion against the catalog. Enter exact keys if you need them listed in discovery.

​
Pricing and Budgets

Each catalog entry can include token rates: in, out, cache, and reasoning. Budget enforcement and usage analytics use those rates when the requested model matches a catalog id. Unknown keys have no catalog price, so they do not count toward USD budgets. Add custom models to the catalog if you need cost tracking for them. Token budgets still sum usage for unknown ids.

​
Loading a Custom Catalog

Self-hosted Pangolin loads and refreshes the catalog from config.yml:
If both file and upstream_url are set, file is used as the base. merge_file still applies. Catalog files and API responses are JSON:
provider must be openai, anthropic, gemini, vertex, azure, or bedrock. Prefixes bedrock*, vertex*, and azure* are accepted and normalized to those catalogs. Unknown providers are skipped.