Turn stable model capacity into agent-discoverable nodes
The seed stage solves one thing: providers can self-list nodes, be probed by the platform, discovered by agents, routed to, and audited with receipts. Payouts and stablecoin settlement stay outside the early core flow.
CRUCIBLE_AUTO_REGISTER=true \
CRUCIBLE_API_BASE_URL="https://api.a2a-crucible.xyz/api" \
CRUCIBLE_NODE_PUBLIC_URL="https://your-node.example.com" \
CRUCIBLE_EMAIL="[email protected]" \
CRUCIBLE_USERNAME="seed-provider-1" \
CRUCIBLE_PASSWORD="change-me" \
PROVIDER_NODE_MODELS="best:coding.high_reasoning,cheap:reasoning" \
CRUCIBLE_PROVIDER_TASKS="coding,reasoning" \
CRUCIBLE_PROVIDER_TAGS="deepseek,low-cost,zh" \
CRUCIBLE_PROVIDER_LANGUAGES="zh,en" \
CRUCIBLE_PROVIDER_REGION="CN" \
CRUCIBLE_PROVIDER_CONTEXT_TOKENS="128000" \
CRUCIBLE_PROVIDER_DATA_RETENTION="no_retention" \
node scripts/provider-node.mjs --check && node scripts/provider-node.mjsHeartbeat
fresh < 30s
Readiness
55+
Receipt
rcpt_*
Seed node path
Each step strengthens the capability network: list, probe, route, meter.
Choose capabilities
Use local Ollama/vLLM, OpenAI-compatible upstreams, or a custom model service you operate.
Run Provider Node
The script starts the compatible endpoint, registers, lists capabilities, and sends heartbeat.
Reach routable readiness
Keep heartbeat under 30s and target readiness above 55 before entering live routing.
Verify with receipts
Every routed call leaves a receipt for audit, scoring, dispute handling, and future billing plugins.
What must pass before routing
These are not payout promises or manual review gates. They are the minimum signals agents need before trusting a node.
Node is reachable by the platform gateway
Local tests can use localhost; seed nodes need public, Tailscale, tunnel, or reverse proxy reachability.
Heartbeat stays fresh
Heartbeat under 30s is normal; over 90s is treated as offline.
Invocation endpoint has basic protection
Use HMAC signing, rate limits, and upstream key scoping when exposed.
Capability description is clear
Agents should understand alias, price, latency, context limits, and suitable tasks.
Agent discovery
External agents can read the discovery card and capability network without using the dashboard first.
Platform routing
Only fresh, ready, policy-matching nodes enter routing candidates.
Billing later
Early flow records usage credits and receipts; billing plugins come after trust data stabilizes.