Vision
B3IQ's role as the AI, proof, and settlement layer for the B3 ecosystem.
B3IQ is a neocloud for AI inference: customers buy or rent-to-own bare-metal GPU servers that B3IQ hosts or ships and operates as managed, manually onboarded nodes. It is also the AI, proof, and settlement layer for the wider B3 ecosystem — B3 apps, agents, and execution systems can call B3IQ as standard HTTP infrastructure, then receive model output, usage metadata, receipts, and settlement evidence. Routing is own-nodes-strict and pricing/payouts are in USD.
The Contract
B3IQ does not need to become an agent marketplace, workflow system, or SDK vendor. The product contract is:
- OpenAI-compatible model listing and chat completions.
- B3IQ-native private job, receipt, billing, node-status, and route-readiness APIs.
- Public-safe protocol evidence for benchmark, settlement, reputation, and disputes.
- Operator tooling for install, setup, local auth, runtime readiness, and safe remote operations.
Target Architecture
B3 Ecosystem Fit
What Exists Now
Cross-platform host agent, setup wizard, local owner auth, local API keys, model profile readiness, and local OpenAI-compatible chat.
Public /v1/api/models, /v1/api/stats, /v1/api/pricing, authenticated
/v1/api/chat/completions, customer-owned gateway keys,
own-nodes-strict routing policy, streaming settlement metadata, and redacted accounting.
What Must Stay Out Of Scope
B3IQ should not maintain product-specific client libraries, agent SDKs, or bespoke adapters. The supported developer surface is endpoint behavior, OpenAPI contracts, examples, error codes, and public protocol metadata.
Launch Gate For The Vision
The vision is credible only when B3IQ proves real routed work without hiding gaps behind roadmap language:
Protocol-eligible, benchmarked, route-ready GPU supply exists in the current pilot path.
Hosted completions, generations, streaming, and private process work exercise real routed traffic and produce recorded evidence.
Receipts, usage rows, node payout rows, and public telemetry line up in redacted evidence packets.
Production installer trust, command-center controls, customer auth, and incident controls are complete enough for public traffic.

