How many AI models does Sakana AI serve?
2 tracked models as of 11 August 2026: 2 language models (2 with a public ModelCap Index position), across 2 live endpoints observed through OpenRouter.
Inference provider
Every tracked model Sakana AI serves through OpenRouter, with Sakana AI's own input and output price per 1M tokens, the context window it serves, disclosed quantization and measured endpoint uptime. Rows link to the model page, where every provider's deployment is listed side by side.
Snapshot as of 11 August 2026
Sakana AI serves 2 tracked models through 2 endpoints as of 11 August 2026; the highest-ranked is Fugu Ultra (ModelCap Index #160).
Ranked models first, in ModelCap Index order. Prices are the lowest Sakana AI lists for the model; the endpoint count shows how many deployments carry it.
2 tracked models as of 11 August 2026: 2 language models (2 with a public ModelCap Index position), across 2 live endpoints observed through OpenRouter.
Fugu Ultra from Sakana AI is the highest-ranked language model Sakana AI serves, at ModelCap Index position #160 and $30.00 per 1M output tokens on Sakana AI. The table lists every model in Index order.
Sakana Namazu at $4.00 per 1M output tokens ($0.95 per 1M input), the lowest positive language-token price Sakana AI lists. Free-tier endpoints, where present, show as $0 and are excluded from that comparison.
Fugu Ultra, served with a 1M-token context window on Sakana AI. Providers sometimes serve less than the model's published maximum, so the figure here is the provider's own.
OpenRouter reports no uptime measurement for Sakana AI endpoints in the current snapshot.
From the OpenRouter catalogue entry for each Sakana AI endpoint, in USD per 1M tokens, re-observed on every ModelCap refresh. Where Sakana AI exposes several deployments of one model at different prices, the table shows the lowest and notes the count; the model page lists each deployment.
It re-renders within a minute of every dataset refresh; this snapshot was published 11 August 2026. Offers retained from a failed refresh are marked stale in the data and are not counted here.