Market opens
Landing page, dashboard, pilot forms, and public proof points.

Flow
Landing page, dashboard, pilot forms, and public proof points.
One simple app/API with keys, usage records, and metered usage.
Selected Ocean providers run real jobs behind Fish.
Supply, demand, reliability, and payouts become visible.
Staked OCEAN can earn AI credits from funded budgets.
Providers can bond OCEAN for routing eligibility.
Useful app, API, privacy, billing, and routing layers.
Only later, after usage and settlement are real.
Now
Show the market clearly: who wants AI, who has compute, and where the first route can work.
Next
A useful chat/API surface comes before complex token mechanics.
Then
Provider payouts come from usage, reserves, or funded budgets, not from staking magic.
Later
Credits, bonds, and capacity markets make more sense once the product has traffic.
Full product loop
Fish should cover the useful product layers: app, API, billing, privacy, routing, credits, staking, provider payments, and proof.
Chat, model menu, API keys, usage dashboard, and credit balance.
Internal credits first, then grants, top-ups, subscriptions, and usage records.
Ocean providers, outside AI, provider preference, and cost-aware backup routes.
Outside AI, private Ocean providers, stronger runners, then hardware privacy much later.
Funded-budget credits from locked OCEAN, tracked with clear caps.
Lock, mint, spend, burn, and unlock only after settlement is safe.
Bonds can boost eligibility, but score and reliability cap the boost.
Unused credits may route demand only after legal and reserve controls.
No token launch until usage, reserves, audits, and legal rails exist.
Build order