Hermes, OpenClaw, Codex, OpenCode, or your own. Your agent installs Antseed itself from one skill and runs on the open market.
Give your agent the skill. Free models to start, no account, no API key.
CodexOpenCode
Claude CodePi
CodexOpenCode
Claude CodePiAgents make hundreds of context-heavy calls. Antseed routes each one to the cheapest verified provider in real time.
Nothing changes in how your agent works. It talks to your local endpoint instead of a hosted API.
http://localhost:8377/v1.Read the agent guideYour local endpoint at localhost:8377 speaks the OpenAI and Anthropic APIs. The key is a placeholder; there is no account behind it.
One file your agent reads. It handles the setup and tells you when it needs you.
Installs the Antseed CLI on the machine the agent runs on.
Starts your local endpoint. No account, no API key.
Shows you where to top up for paid models. Free models need nothing.
Points itself at the endpoint and picks a model. Every call goes to the best provider.
No signup, no email, no platform key. The agent pays per request from a wallet, so the provider never learns whose agent it is.
Learn moreRequire TEE verification when you start its endpoint and the agent only talks to verified providers. Its prompts and tool calls run in a secure enclave, hidden even from the provider.
Learn moreNo account, whether you run the AI VPN or the Antseed CLI. The local endpoint does not validate a key, but most agent SDKs want a non-empty value, so use a placeholder like antseed. Only a public endpoint you publish from the Agents view uses a real, generated key.
Anything that speaks the OpenAI or Anthropic API: Hermes, OpenClaw, Claude Code, Codex, OpenCode, Pi, or your own. Hermes and OpenClaw have maintained setup skills; Claude Code, Codex, and OpenCode also have CLI wrappers (antseed claude, antseed codex, antseed opencode). Any other agent uses its custom provider settings with the base URL and key above. Read the agent guide →
Yes. The simplest way is to install the CLI on that server and start the endpoint next to the agent, so it talks to localhost:8377 as usual. If the agent must reach an endpoint on a different machine, publish an authenticated endpoint from the AI VPN's Agents view, using ngrok or Cloudflare, and swap in the URL and key it shows. Public HTTPS tunnels guide → More questions in the FAQ →
Give your agent the skill, or download the AI VPN and connect it yourself.