Sakana AI
Listed at https://sakana.ai
💰 Token Pricing
| Type | Price | Note |
|---|---|---|
| Input | Fugu Max: $2/M (fixed any context); Fugu Ultra v2: $5/M standard (≤272K) or $10/M long context (>272K) | per million tokens |
| Output | Fugu Max: $6/M (fixed); Fugu Ultra v2: $30/M standard or $45/M long context | per million tokens |
🤖 Supported Models (4)
✨ Pros
- ✓Tokyo-based AI lab focused on multi-agent orchestration architecture (multi-agent system as a model)
- ✓Sep 11 release: Fugu Max ($2/$6 fixed) and Fugu Ultra v2 ($5/$30, doubled >272K), all behind one OpenAI-compatible endpoint
- ✓Fugu Max wins or ties top score on six benchmarks (Terminal Bench 2.1, GPQAD, AA-LCR, GDP.pdf, AutomationBench, SWEFish); output pricing 40-60% below Sonnet 5, GPT 5.6 Terra, Kimi K3
- ✓Fugu Ultra v2 Chartography 48.3 (Opus 5: 27.3, Fable 5: 29.5) and DeepSWE 74.3; explicitly does NOT use Fable 5/5.1 or GPT-6-Astra in its agent pool
- ✓Underlying model pool includes NVIDIA Nemotron via Sakana-NVIDIA collaboration plus open and specialized models; one key covers all four variants
- ✓Standard subscription $20/month (lightweight daily use); Token Plan (pay-as-you-go) at higher priority than subscription tokens
⚠️ Cons
- ×Fugu Ultra v2 output price ($30/M) is materially higher than Sonnet 5, GPT 5.6 Terra, Kimi K3 frontier models
- ×Fugu Cyber has no published pricing — must go through sales
- ×Long-context (>272K) doubles the rate; cross-boundary workloads need to budget both tiers
- ×Orchestration (not single model) means response latency bounded by the slowest agent in the pool
- ×No mainland-China edge; stable overseas proxy required
🎯 Best For
Teams that want one OpenAI-compatible endpoint with multiple orchestration tiers selected per workload; long-context agents (budget against Ultra v2 long-context tier); complex chains where you only pay the top-tier model's standard rate per request; mixed workflows with predictable per-call web search/fetch costs.
💰 Pricing & Plans
| Model | Context | Input ($/M tok) | Output ($/M tok) | Cached input ($/M tok) | Notes |
|---|---|---|---|---|---|
| Fugu Max | Any | $2.00 | $6.00 | $0.25 | Fixed pricing regardless of context length; Pareto cost tier |
| Fugu Ultra v2 (standard) | ≤ 272K | $5.00 | $30.00 | $0.50 | Peak performance; open weights + specialized pool, no Fable 5/5.1 or GPT-6-Astra |
| Fugu Ultra v2 (long context) | > 272K | $10.00 | $45.00 | $1.00 | Doubles above 272K context; chartography 48.3 / DeepSWE 74.3 |
| Fugu | Standard | Pay-as-you-go | Pay-as-you-go | Per console | Default tier; balanced performance and latency |
| Fugu Cyber | Standard | Sales-led | Sales-led | — | Cybersecurity specialist; contact Sakana for pricing |
🔧 API & Developer Experience
- •Endpoint: OpenAI-compatible base URL at console.sakana.ai — most OpenAI SDKs work by swapping base_url and api_key. A single key covers all four Fugu variants; switching is a single parameter change in the request payload, not a separate integration.
- •Streaming & Responses: Standard Chat Completions streaming (SSE). The Responses API breaks out orchestration tokens separately from user-visible model work — a Sakana-specific addition not present in standard OpenAI responses.
- •Orchestration Pricing: When a single underlying model is selected, you pay only that model's standard rate. When multiple agents fire, Sakana does not stack fees — only the top-tier model involved is billed at its standard rate.
- •Web Tools: web_search and web_fetch are billed at $0.007 per call on top of token charges. Useful for retrieval-augmented agents; budget for the per-call cost separately because it can dominate token cost for search-heavy workloads.
- •Subscription vs Token Plan: Standard subscription at $20/month is positioned for lightweight daily usage and is served at standard priority. Token Plan (pay-as-you-go) is served at higher priority than subscription tokens — recommended for production workloads even when a subscription is active.
- •Regional & Latency: Japan-origin hosted API; no mainland-China edge. Direct connections from China require a stable overseas proxy. No published SLA tier; Sakana does not currently publish latency benchmarks per region.
🐡 The Fugu Thesis: Orchestration Over Single-Model Stacking
Sakana's defining bet is that the cost-performance frontier is two-dimensional: capability on one axis, cost on the other. Rather than building one massive frontier model and scaling it, Sakana orchestrates a swappable pool of open and specialized models (NVIDIA Nemotron among them) and routes each request to the leanest model capable of solving it. The result is Fugu Max expanding the Pareto frontier northwest — performance within striking distance of elite models at 40-60% lower output cost than Sonnet 5, GPT 5.6 Terra, and Kimi K3 — and Fugu Ultra v2 pushing peak performance upward while explicitly not relying on Fable 5, Fable 5.1, or GPT-6-Astra. The architecture is the product; the underlying weights are replaceable. For teams that want frontier-class results without vendor lock-in to a single model's roadmap, that is the differentiator. The trade-off is structural: orchestration latency is bounded by the slowest agent in the pool, and the cost model has a soft ceiling that does not always reflect the work done.
🌐 China Access & Latency
Sakana AI is a Japan-based lab serving its Fugu API from Japanese infrastructure with no mainland China regional endpoint. Production use from mainland China therefore requires a stable overseas proxy or an aggregator that fronts the Sakana API; direct connections typically time out or face elevated latency. Real-world latency from China is dominated by the cross-border round trip to Japan, making Fugu a poor choice for latency-sensitive interactive workloads and a workable choice for batch jobs and agentic workflows that tolerate a slower first byte. There is no China-specific pricing, billing, or data-residency option. For teams targeting Chinese end users, a domestic LLM (Qwen, DeepSeek, Zhipu, Doubao) is the latency-safe default, while Sakana remains attractive for Japan-hosted workloads, English/Japanese multilingual tasks, and teams that want the orchestration architecture rather than a single-model provider.