Access map

Sakana Fugu is listed on more than one door. Those doors are not interchangeable.

The official product page currently says Fugu is also available on OpenRouter, Vercel, opencode, and two other named partners. That is a product-listing fact. It is not a statement that every partner copies official rates, Cyber access, EU policy, usage fields, or training-data controls.

Checked August 17, 2026No partner SLA claimed

1. The official console is still the source of product rules

Sakana AI documents model IDs, ignored fields, Cyber access, EU and EEA unavailability, subscription tiers, and Ultra token rates on its own Models and Pricing pages. If you need those rules to be the ones you are operating under, start at the official API. A partner listing does not automatically import every console policy.

Use the official route when you need:

  • The documented Responses, Chat Completions, Messages, and Models endpoints
  • The published Ultra rate table and usage-object explanation
  • The Cyber access request and pay-as-you-go-only rule
  • Console settings such as Fugu agent opt-out and training-data opt-out

2. What the product page actually listed on August 17, 2026

The live Sakana Fugu product page showed partner marks and links for:

  • OpenRouter, pointing at a Fugu Ultra listing
  • Vercel AI Gateway, pointing at a Fugu Ultra listing
  • opencode / models.dev provider listing
  • Creao and Merge, via public posts rather than a console docs page
This site does not certify those routes.

We did not independently verify each partner’s current price, data-retention policy, Cyber availability, regional block behavior, or whether orchestration tokens appear in their invoices. If a procurement decision depends on those details, read the partner’s own terms and compare a test request’s usage object.

3. Questions a partner route must still answer

QuestionWhy it mattersWhere to verify
Which model IDs are exposed?fugu-ultra and fugu-ultra-v1.1 are not the same pinning choicePartner model catalog plus a live list call if one exists
Is Cyber available?Official Cyber is pay-as-you-go and access-gatedPartner listing; do not assume yes
Are orchestration tokens itemized?Official Ultra bills those fields as real usageOne paid test request and the invoice line items
Who is the data controller?Training opt-out on the Sakana console may not travelPartner privacy terms
Does the EU and EEA rule still apply?The official product is not offered thereOfficial FAQ plus partner geo policy

4. A practical default

Use the official console when Fugu is a production dependency and you need the documented billing object, Cyber request path, or console-side opt-outs. Use a listed partner only after you have compared those five questions on a real request. Do not migrate a cost model from this site’s Ultra calculator onto a partner invoice unless the partner publishes the same rates and the same usage fields.

If the reason you want a partner is “one key for many vendors,” that is a platform choice. It does not remove the need to know which Fugu version you called. Record the model ID in application logs either way.

Sources