Each count answers a different question.

These counts come from one catalogue dated 2026-10-13. They differ because each one counts something different, and none of them is a promise about what a plan includes.

Outside the catalogue, so in none of these counts and without a tile below, the CLI also takes a key for Ollama Cloud.

395 catalogue entriesEvery model record in the shared catalogue, whichever provider lists it. This is the widest figure, and it is the catalogue the apps compile in, not a list of models an account can use.
392 BYOK model entriesThe catalogue entries listed under the 12 providers on the bring-your-own-key list. It is the gateway entries plus the direct entries, and it leaves out the 3 entries listed under providers that are not on that list.
350 gateway entriesEntries a gateway lists on behalf of other developers, reached with your gateway key. The same model can also appear under its own developer, so this is a count of routes, not of distinct models.
42 direct model entriesEntries listed under a provider you reach with that provider's own key, with no gateway in between.
12 BYOK providersProviders on the bring-your-own-key list that have a catalogue record. 1 of them lists no models in the catalogue, so it adds to the provider count and not to the model count.
1 provider with no listed modelsProviders that take your key but carry no catalogued models. Each adds to the provider count and not to the model count.
2 local runtimesRuntimes the CLI discovers on your own machine. They carry no catalogued models, because the server you started reports what it holds.
23 provider recordsEvery provider record in the catalogue. 12 are on the bring-your-own-key list, 4 are local runtime records, of which the CLI uses 2, and 7 are records for the managed router, media models and providers that are not on the bring-your-own-key list. It is a bookkeeping count, not a number of integrations you can configure.
16 managed roster modelsThe models the plan allow lists name for AGI managed cloud, which is the only route AGI Web uses. Which of them a plan includes is shown on the pricing page.

The roster

Each tile is a read from the shared model catalog.

The CLI takes a key you hold for each of the 12 BYOK providers below, and each one bills you on your own account at its own rates. AGI adds no markup and shows no per-token price. Between them they carry 392 catalogue entries.

The CLI also keeps web search keys for Brave Search and Tavily, which are not model providers. The CLI is coming soon.

Anthropic4 modelsclaude-sonnet-5-5Your keyBilled by provider
OpenAI9 modelsgpt-6-astraYour keyBilled by provider
Google15 modelsgemini-3.8-flashYour keyBilled by provider
xAI1 modelgrok-4.7Your keyBilled by provider
DeepSeek2 modelsdeepseek-flashYour keyBilled by provider
MiniMax1 modelminimax-m3Your keyBilled by provider
Perplexity4 modelssonar-deep-researchYour keyBilled by provider
Alibaba Model Studio3 modelsqwen-3.7-plusYour keyBilled by provider
Moonshot AI1 modelkimi-k3Your keyBilled by provider
ZhipuAI2 modelsglm-5.3Your keyBilled by provider
OpenRouter350 modelsopenrouter-autoGatewayBilled by provider
NVIDIA NIMLists its own modelsGatewayBilled by provider

Local runtimes

The CLI also talks to Ollama and LM Studio. Neither carries catalogued models, because AGI asks the server you started what it is holding rather than assuming.

OllamaLists its own modelsLocal runtimeNo key, no meter
LM StudioLists its own modelsLocal runtimeNo key, no meter

The source file

The CLI compiles this catalog; the web app imports it.

packages/contracts/types/src/models.json is embedded in the CLI, and the web app imports the same module. A label, default model, or model entry changed there changes both and this page at once. The CLI surface itself is coming soon.

pub const SHARED_MODELS_JSON: &str =    include_str!("../../../packages/contracts/types/src/models.json");

The CLI embeds the file at compile time.

Inside one session

Swapping a model is not the same as moving a session.

/model resolves the provider for the model you name. In a BYOK session, one cloud provider to another is a swap, and the thread carries on; a model on another route is refused, with a message to start a new session. In a Local session, naming a cloud model changes the model and the next send stops at the privacy boundary; the error names the command for the reviewed fork described on the Local page.

How a Local session moves

› /model <model>Switched to <model> (<provider>)

Bring the key

The catalog is already there.

Your key, your provider

The CLI keeps one credential per provider, in the operating system keyring or in owner-only files on Linux or when the keyring is turned off, and calls that provider directly. The CLI is coming soon.

Keys saved on your own machine
Traffic goes straight to the provider
The status bar names the route in use

Read the provider-key guide

The same catalog in the terminal

The CLI compiles the same catalog and is coming soon.

agi models scan finds local servers
Every turn prints its tokens and cost
Works offline with a local model

Check surface availability

Explore providers and local runtimes.

The catalogue in numbers