01 / Routing
A familiar OpenAI-compatible request can express model, provider, budget and policy preferences. Provider health, price and latency guide the selected route.
A concise architecture overview, not a replacement for the official whitepaper.
A familiar OpenAI-compatible request can express model, provider, budget and policy preferences. Provider health, price and latency guide the selected route.
A prepaid balance and documented payment routes support inference. Settlement accounting uses SOL; supported token payment routes apply caps and valuation requirements.
Per-call records include model, provider, tokens and itemized costs. Ed25519 signatures provide inspectable router-issued evidence, subject to the signing-key trust model.
Private routes and sealed hosting depend on approved builds, fresh hardware attestation and verified policy. Evidence should be inspected with its scope and limitations in mind.