Back to market

Route compass

Where does your request go?

Demo mode. Demo answer today.

DemoOutside AIOcean providersPrivate later
Fish route compass in a Venice Ocean Navy workshop

Flow

1

Ask Fish

User sends one normal chat/API request.

2

Choose path

Fish chooses the best available route.

3

Use credits

The request shows what it used.

4

Show status

The UI says how the answer was made.

Active route

Demo mode

Demo answers stay inside the local app process.

Proof tag

Marked as a demo estimate so nobody confuses it with provider work.

active

Demo answer

Local answer for the first version.

No outside provider is called.

Demo usage record.

needs config

Outside AI

Real AI through an outside provider.

Outside provider policy applies.

Outside AI usage record.

pilot

Ocean providers

Selected Ocean providers run jobs.

Provider terms and Fish routing policy apply.

Signed provider proof.

future

Private Ocean lane

Ocean provider with reviewed privacy rules.

Provider commits to no prompt/output retention.

Policy review plus usage records.

future

Stronger runner

Controlled runner with tighter isolation.

Runner-level storage and access controls.

Runner logs without raw prompt text.

future

Hardware proof

Hardware-backed route much later.

Hardware-backed execution boundary.

Hardware proof plus provider proof.

Harbor rules

Simple promises.

JSON policy

Name the route

Demo, outside AI, and Ocean provider work must be labeled differently.

No fake Ocean

Fish must not claim Ocean routing until selected providers run jobs.

Usage stays clean

Usage records keep hashes, costs, and provider ids, not raw prompts or outputs.

Privacy is explicit

Outside AI can help launch, but that provider's privacy policy applies.

Next: Connect selected Ocean provider jobs to the chat/API route behind an allowlist and public-safe proof.
Fish labels every route. If selected Ocean providers did not run the work, Fish will say so.