Guide library
Sakana Fugu guides that add a decision, not another recap
Each page exists because an official product, models, or pricing page leaves a practical gap: unpublished Cyber rates, ignored OpenAI fields, third-party access, or a billing object that does not behave like OpenAI. If a page cannot add that kind of increment, it is not listed here.
How this library is curated
SakanaFugu.com is an independent editorial project. It is not Sakana AI, does not have private model access, and does not invent missing numbers. The August 17, 2026 recheck compared the live product page, Models documentation, and Pricing documentation against the previous July 21 snapshot. The useful result was not “more prose.” It was a list of facts that changed, facts that stayed, and facts that official pages no longer publish.
Fugu Cyber no longer has a public token-rate table on the official pricing page. Earlier public $6 / $36 / $0.60 figures are therefore withdrawn from this site. The official instruction is to contact Sakana AI sales. Repeating a stale rate would be a trust failure, not a helpful calculator feature.
Start with the decision you actually have
Transparent model chooser
Three visible rules: region, routing visibility, and workload. The result can be Fugu, Ultra, Cyber, self-managed orchestration, or “do not use Fugu here.”
Ultra published-rate calculator
Applies only the official Ultra table, including orchestration tokens. It refuses to invent a Fugu blended rate or a Cyber rate that sales now controls.
API quickstart
Environment checks, Responses examples, bounded retries, and a production checklist that treats ignored OpenAI fields as a real integration risk.
Benchmark evaluation playbook
How to use the published table as a map of strengths without treating it as independent proof on your repository or toolchain.
All current guides
Pricing explained
Fixed Ultra rates, variable Fugu billing, unpublished Cyber pricing, the 272K threshold, and worked examples that keep orchestration tokens in the formula.
Orchestration token accounting
Why Ultra and Cyber usage objects do not match OpenAI’s meaning of token_details, and how to persist the fields you will need after a bill arrives.
Subscription versus pay-as-you-go
What the $20 / $100 / $200 tiers actually disclose, why pay-as-you-go has higher official priority, and why a break-even formula is still dishonest.
Responses, Chat, and Messages
Three supported shapes, the fields that are accepted but ignored, and the reason previous_response_id cannot be used as conversation state.
Failure checklist
401, 403, missing models, EU and EEA unavailability, Cyber access, billing mode, and cost surprises mapped to a next action instead of a retry loop.
Official API versus listed partners
What the product page currently lists for OpenRouter, Vercel, and opencode, and what this site still cannot verify about those routes.
Fugu Cyber access and limits
Pay-as-you-go only, the official access request, unpublished rates, and the authorized-use boundary this site will not cross.
Fugu versus self-managed orchestration
When a learned pool is the right trade, and when you still need a graph you can inspect because routing details are proprietary.
August 17 source-check log
The dated list of product facts that changed, expired, or were withdrawn since the previous review. This is the page to read before trusting any older screenshot.
EU and EEA availability
Official unavailability is a stop, not a timeout. This page records the rule and refuses workarounds.
Pin model IDs
When to use the moving fugu-ultra alias and when to pin v1.1 or v1.0.
Glossary
Local meanings for orchestration tokens, the 272K threshold, and unpublished Cyber rates.
FAQ
Short stops that point at the matching guide instead of inventing a missing number.
What you will not find here
- A made-up average token rate for standard Fugu.
- A current Cyber rate table copied from an older snapshot.
- Hands-on benchmark numbers that this site did not run.
- Exploit steps, unauthorized scanning advice, or “jailbreak” content around Fugu Cyber.
- A promise that a listed third-party route has the same data handling as the official console.
Those omissions are the editorial method. They are also why the guides stay useful after a vendor page changes: the unknown stays labeled as unknown.