Current Status
Historical B3IQ pilot evidence, the current earnings model, and how to confirm service readiness.
Source review: October 3, 2026. The pilot evidence and launch gates below were documented between May and August 2026. They have not been revalidated here as a current production acceptance report.
Historical pilot results do not establish current service support or that a launch gate is closed. Ask B3IQ for dated acceptance evidence for the service and machine you intend to use.
Current source boundary
Account gateway keys select only their own machines. The October 3 source change permanently removes third-party provider fallback and the public node explorer, leaderboard and rate pages. Old page links redirect to current machine, hardware and earnings-planning pages. This source review does not confirm that change is deployed.
Current machine checkout, supported USDC payment rails, private machine telemetry, shared receipt types and historical account records remain. Historical pilot evidence below is preserved for interpretation, not presented as current production acceptance.
Current earnings model
Serving inference creates no per-request charge or payout. Machine earnings come from capacity rented by the hour. Under Managed Hosting, the owner receives 85% of rental revenue before hosting costs are deducted. The ownership terms explain the deductions and estimates; income is not guaranteed.
Historical request-payout ledger entries and on-chain settlement batches remain readable. They are not evidence of earnings from requests served today or of the current hourly rental payout process.
Historical pilot snapshot
| Area | Status | Evidence |
|---|---|---|
| b3iq.org | Live during pilot | Cloudflare Workers Static Assets site with machine purchase, inference rates, node readiness, telemetry, and protocol views |
| Local host agent | Pilot evidence | Linux host agent with local setup, local OpenAI-compatible APIs, local auth, API keys, support grants, receipts, and runtime/model readiness |
| Hosted real work | Deployed development evidence | Real-work smokes documented hosted completion, generation, streaming, and private process work with receipts, usage rows, and public telemetry deltas |
| Supply | Pilot evidence | Protocol-eligible managed supply served routed workloads; durability was a documented launch gate |
| Settlement | Historical settlement evidence | The pilot documented finalization of submitted on-chain payout batches; this was the earlier request-payout rail |
| Provisioning & updates | Pilot evidence | Checksum-verified host-agent artifacts and signed self-update were documented; production signed-metadata enforcement was a launch gate |
Checking current readiness
Sign in to the machine dashboard to inspect your machine's state. A current deployment review should include a dated successful request on the intended model and machine, the service's support scope, and the relevant operational acceptance evidence. A merged change or published documentation alone does not establish those facts.
See Route readiness for routing blockers and Receipts and settlement for interpreting work receipts and historical settlement records.
Live public pages
Historical launch gates
The July 2026 gate list covered the work below. This page does not mark any of these gates open or closed today.
- Supply that stays routable without active SSH sessions or fragile user-service state.
- Production signed-update enforcement, package trust, and clean/reused-machine provisioning checks.
- Hosted gateway auth, keys, usage reporting, abuse controls, rate limits, audit logs, roles, and incident controls.
- Recurring settlement automation for the earlier request-payout rail. Current hourly rental payouts require their own acceptance evidence.