Docs / Buying
Routing and pinning
How the AntSeed proxy chooses a seller, and the three ways to make it choose us.
How the proxy chooses
Every request leaves your machine through AntSeed's local proxy. For each request the proxy looks at the model name, finds the sellers that announce it, drops those outside your price limits or below the network's reputation gate, and picks one. Unless you pin a seller, the pick is the proxy's, and it can change from one request to the next.
Pinning tells the proxy to send requests to one peer. Our peer ID:
d19ffae0e85b5230422019926b2f37ec0f1f41f3
Three ways to pin
1. Pin the proxy
Every tool that uses this proxy goes to Super Seeder. No restart.
antseed buyer connection set --peer d19ffae0e85b5230422019926b2f37ec0f1f41f3
The running proxy adopts it at once and keeps it across restarts. antseed buyer connection get shows the current state, port and pin. Undo:
antseed buyer connection clear
2. Pin one tool, per request
Put the peer in front of the model name. The proxy reads it and strips it before the seller sees the request.
[email protected]
This works anywhere you can set a model name: antseed codex --model ..., antseed opencode, antseed claude, or the model field of any OpenAI-compatible SDK.
3. Pin with a header
For tools that let you add a default header to every request:
x-antseed-pin-peer: d19ffae0e85b5230422019926b2f37ec0f1f41f3
Do not add an x-antseed-provider header. The proxy sets it, and a value we do not announce makes the request fail.
Precedence
A per-request pin wins over a proxy pin. A proxy pin wins over the proxy's own choice. So a tool pinned to another seller keeps going there even if the proxy is pinned to us.
Pinning is strict
Pinned, your requests go to this peer and nowhere else. If we are unreachable, or do not serve the model you asked for, the proxy answers with an error instead of trying another seller. The errors are listed in Limits and errors. If you would rather fall back, do not pin: the proxy's own ranking already prefers cheaper sellers, and ours is usually among them.
A proxy started seconds ago may need up to a minute to discover us. If a pinned request keeps saying the peer is not reachable after that, update the AntSeed CLI and restart the proxy.
Prove where a request went
The proxy names the seller that answered in a response header, on every response, streaming included:
x-antseed-peer-id: d19ffae0e85b5230422019926b2f37ec0f1f41f3
To check a pin, send a request through the path you changed without adding a pin header of your own, and read that header. antseed buyer channels --json lists your channels per peer with request counts, which is a second proof.
For agents
The page at agent.md is this page written for a coding agent: how to tell which setup the person has, the one change to make, how to verify, and how to undo. The prompt to give the agent is on Use.