Set your price. Announce to the network. Receive USDC for settled deliveries - whether you run a model, a routing service, or a specialized agent.
All three serve buyers on the open market. What runs behind is entirely yours.
You run a model or proxy an upstream API - Ollama, a fine-tune, a local GPU, OpenAI, Together. Point Antseed at it with one config entry and announce it to the network. Buyers choose you based on price, latency, and onchain reputation; payments depend on demand and successful settlement.
You've built domain expertise in AI form. A legal agent, a security researcher, a trading analyst. Announce it as a named service. Buyers pay for your expertise, not just the tokens.
Build specialized routing logic and offer it on the network. Latency-optimized, cost-minimizing, TEE-only, or domain-aware. Receive payment for settled routed requests without running a single model.
Providers must add value on top of upstream APIs: TEE-secured inference, agents, fine-tunes, or managed products. Reselling raw API access or subscription credentials is not allowed.
Buyers see enough to route and verify. Everything else stays on your machine.
Public to the network
Under your control - secure your node
No code to write. Point Antseed at an OpenAI-compatible endpoint, set your prices and categories, and offer capacity to buyers.
1 · Configure with the CLI
# Point at any OpenAI-compatible endpoint antseed config seller add-provider together \ --plugin openai \ --base-url https://api.together.ai # Announce a service with your price + categories # (--cached is optional - set it to charge less for # cached-input tokens when your upstream supports them) antseed config seller add-service together deepseek-v3.1 \ --upstream "deepseek-ai/DeepSeek-V3.1" \ --input 0.6 --cached 0.06 --output 1.7 \ --categories chat,math,coding # Start serving export OPENAI_API_KEY=<your-key> antseed seller start
Compatible with any OpenAI-API endpoint - your own Ollama, vLLM, a fine-tune, or an upstream you have the right to resell. You are responsible for complying with your upstream's terms of service.
2 · Or edit config.json directly
{
"seller": {
"providers": {
"together": {
"plugin": "openai",
"baseUrl": "https://api.together.ai",
"services": {
"deepseek-v3.1": {
"upstreamModel": "deepseek-ai/DeepSeek-V3.1",
"pricing": {
"inputUsdPerMillion": 0.6,
"cachedInputUsdPerMillion": 0.06,
"outputUsdPerMillion": 1.7
},
"categories": ["chat", "coding", "math"]
}
}
}
}
}
}Your backend URL, API key, and routing logic are intended to remain under your control. The network only sees the service name, price, and categories; you are responsible for securing your node and credentials. Read the config reference
The buyer reserves a budget. You deliver and the buyer authorizes. You settle on Base.
Before the first request, the buyer signs a reservation that locks USDC in the deposits contract on Base. It caps what you can collect on that channel.
After each response the buyer signs the running total you may collect, and your node signs a receipt with the exact usage. No onchain transaction per request.
Your node submits the latest authorization when the channel closes or after 10 minutes idle. The USDC lands in your wallet and the unused budget returns to the buyer.
antseed seller status # earnings, peers, wallet address antseed seller register # register on-chain; all you need to sell antseed seller stake <ants> --epochs <n> # optional: stake ANTS for rewards
Your EVM wallet is derived automatically from your node's secp256k1 identity key. Payouts land in it on every settlement - no claim step, no separate wallet setup. Read the payment protocol
Every delivery is recorded onchain. Your reputation belongs to your wallet. No platform can revoke it.
Every settled delivery is recorded onchain against your wallet: success rate, latency, token accuracy from signed receipts, and uptime across the windows you announce. Buyers and routers read those stats when they rank you, so a strong track record brings more traffic and can command a higher price. How trust is computed
Before you start
Providers are independent operators and are solely responsible for their models, infrastructure, outputs, logs, privacy practices, data handling, security, sanctions/export compliance, tax obligations, applicable AI laws, and upstream API provider terms.
Provider-side ANTS emissions are currently tracked but locked in a dedicated Provider Pool while Antseed develops stronger validation and proof systems. Fake usage, sybil behavior, or incentive extraction may be excluded or subject to future slashing.
The network only sees what you announce: your service names, pricing, capability tags, and onchain reputation. Your backend URL, model provider, routing strategy, system prompt, and fine-tune weights stay under your control. You are responsible for securing your own node, credentials, logs, and infrastructure.
Three: Raw Inference (serve a model or proxy an existing API), Routing Service (select providers on behalf of buyers and receive payment per routed request), or AI Agent (wrap domain expertise as a named always-on service). A single node can run all three at once, each at its own price.
No. Providers announce uptime windows in their listing. When you go offline, the network routes around you. Your onchain reputation persists across sessions.
The buyer reserves a USDC budget onchain before the first request, then signs a running total after each response. Your node settles that total on Base when the channel closes or after 10 minutes idle, and the USDC lands in your wallet automatically. No invoicing, no billing cycles. More questions in the FAQ →
Install the CLI, configure your provider, and offer AI capacity as an independent operator.