Back to market

API hatch

Build with Fish.

One key. One chat request. Credits and route labels included.

API keysModelsUsagePrivacy
Venice market API hatch with Ocean Navy compute tools

Flow

1

Get a key

Start with one Fish API key.

2

Pick a model

Choose the model you want Fish to use.

3

Send a request

Use a familiar chat shape.

4

Check usage

See credits used and route status.

API

Familiar chat

Use a common chat request shape so builders can move fast.

Routing

Clear route labels

Fish says whether an answer came from demo mode, outside AI, or selected Ocean providers.

Credits

Credits from day one

Every request should show the credits it used.

Providers

Proof for provider work

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

Honest modes only.

Fish should say the truth about privacy. Stronger privacy labels arrive only when the route really supports them.

1

Outside AI

An outside AI provider may receive the prompt. Their policy applies.

2

Ocean policy

Selected Ocean provider with reviewed privacy rules.

3

Stronger runner

More locked-down provider runner, later.

4

Hardware proof

Hardware-backed privacy, later.

5

End-to-end private

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.