ANTSEED / NETWORK
Antseed Network.
Not another API gateway.
Your device finds providers itself, talks to them directly, and pays per request. Nobody sits in the middle: no account, no server that sees your prompts, no company that can shut you off.
01 / FIND
Your device finds providers itself.
It asks Mainline DHT, the same network BitTorrent uses, for provider addresses, then reads each provider’s signed listing: which models, at what price.
How a request travels.
Four steps, all of them either on your device, between you and the provider, or on Base. None of them on an Antseed server.
Find
Providers are found over Mainline DHT, the same network BitTorrent uses. It holds only addresses, never model names or prompts.
Read the specChoose
Your device picks the provider by price and trust. There is no Antseed server making that call.
Read the specPay
You sign a running total per request, and the provider settles it in USDC on Base.
Read the specWhat lives where.
Three places, and nothing else. Once you know which is which, you know what Antseed can and cannot see.
On your machine
Routing preferences, local history, and your allow/block rules.
Between the peers
Requests and responses. The provider you chose can read the request it serves.
On Base
Deposits, payment authorizations, usage totals, stake, and rewards. Prompts and outputs never go onchain.
Encryption protects traffic in transit. It does not hide anything from the provider you chose.
Where the security boundaries areTrust you can check.
Anyone can join, so a name is not enough. Your device scores every provider from public signals and skips the ones below your bar. Proven wash trading sets the score to zero.
History
Completed channels and settled USDC volume.
Usage
Share of recognized usage in the last epoch.
Backing
ANTS locked behind the provider’s identity.
Identity
A verified GitHub account or domain.
USDC pays. ANTS rewards.
Two separate systems with two separate jobs.
USDC pays for the work.
- You top up by card in the AI VPN, or with USDC from the CLI.
- Before the first request, a budget is reserved. After each response, you sign the running total.
- The provider settles on Base and the unused budget returns to you.
ANTS rewards real usage.
- Providers lock ANTS behind their service as long-term backing.
- Settled, buyer-authorized usage that passes the eligibility rules earns rewards.
- Rewards are capped and never guaranteed. Losing a reward never reverses a payment.
When things go wrong.
Independent providers go offline and fail requests. The network is built for that.
A provider disappears.
Your device moves on to another eligible provider. The money reserved for that channel returns to your deposit after a short grace period.
A provider keeps failing.
Your device cools it down and prefers others. No central operator has to step in.
Infrastructure goes down.
Other bootstrap servers can still get you into the network. Settlement still needs Base, so peer-to-peer does not mean zero dependencies.
Every layer is open.
Discovery, encrypted transport, metering, settlement, and reputation, all open source. Read the spec, inspect the code, and build on the same pieces.
Run a node. Build a provider.
Make the network your own.
Open source · Independent peers · USDC settlement on Base