Get a key
Start with one Fish API key.
API hatch
One key. One chat request. Credits and route labels included.

Flow
Start with one Fish API key.
Choose the model you want Fish to use.
Use a familiar chat shape.
See credits used and route status.
API
Use a common chat request shape so builders can move fast.
Routing
Fish says whether an answer came from demo mode, outside AI, or selected Ocean providers.
Credits
Every request should show the credits it used.
Providers
Provider jobs need public-safe proof before they become normal routes.
Builder start
Fish starts with keys, models, chat, balance, and usage records. Selected Ocean provider routes come after provider testing.
Privacy ladder
Fish should say the truth about privacy. Stronger privacy labels arrive only when the route really supports them.
An outside AI provider may receive the prompt. Their policy applies.
Selected Ocean provider with reviewed privacy rules.
More locked-down provider runner, later.
Hardware-backed privacy, later.
Encrypted all the way to the runner, much later.
For now, do not treat Fish as private encryption. If outside AI is used, that provider receives the prompt.