Config builder

Pick models, get a config

Search the catalog or type any model id (the model name is a config value, so anything your provider serves works). Add two or more and they become a weighted pool with automatic failover. Keys stay in environment variables; the config never holds a secret.

Or add any model id by hand, including a custom endpoint

Cloud backends (Azure OpenAI, Oracle OCI) whose host is per-resource aren't a fixed catalog row. Pick one from the provider dropdown above to prefill the fields you edit. The catalog is a convenience, not a boundary: any provider on the six protocols works.

Pool name what your clients put in the model field

your pool, in all six languages

config.yaml busbar 1.5+

providers.yaml

environment

run

Check it before you run: busbar --validate parses and validates both files with no server, no network, and no secrets required (exit 0 = valid). Wire it into CI. How validation works.

Two tiers here. Providers in the shipped catalog (114, verified: endpoint shape confirmed against each provider's own API docs, error dialects mapped where documented) work with the default providers.yaml. Everything else is generated from a reviewed models.dev snapshot: Busbar speaks its language, but the entry is inferred, so verify it and add it to your providers.yaml (the pane below writes it for you). A model that isn't listed anywhere still works: type its id by hand, and cloud backends whose host is per-resource (Azure OpenAI, Oracle OCI) come as fill-in templates. The catalog is a convenience, not a boundary, since any provider on the six protocols works. Bedrock credentials go in one variable as ACCESS_KEY_ID:SECRET_ACCESS_KEY. Full reference: Configuration · Adding a provider · Pools.