Local Sandbox
Use B3IQ sandbox mode to develop hosted gateway flows with fixture nodes, fake billing, benchmark evidence, and receipts.
Sandbox mode lets developers exercise hosted gateway and billing endpoints without a real protocol-eligible paid node.
What Sandbox Seeds
Local control-plane sandbox mode can seed:
- One explicit fixture node.
- Customer-owned
b3iq_gateway_key. - Fake billing rows.
- Observed benchmark evidence.
- Fixture receipts.
This supports endpoint-only local development for /v1/models,
/v1/chat/completions, billing status, receipt lookup, and route-readiness UI.
Production application traffic uses the public https://b3iq.org/v1/api
facade; local sandbox calls the control-plane Worker directly.
Typical Flow
Enable sandbox mode
Start the control plane with sandbox mode enabled (see the internal operations runbook for the exact command).
Seed fixture state
Load the sandbox fixtures using the control-plane sandbox seed utility (see the internal operations runbook).
Call endpoint surfaces
Use the seeded gateway key against your local control-plane URL to test hosted model listing, chat, billing, usage, receipts, and route-readiness.
Fixture state is useful for development and UI testing. It does not prove real paid routing, real customer billing, real node execution, or settlement.
Good Uses
- Build endpoint-only examples.
- Test model listing UI.
- Validate stable error handling.
- Exercise billing and receipt views.
- Develop command center panels without touching production state.
Bad Uses
- Claim production route readiness.
- Demonstrate real payout settlement.
- Benchmark real models.
- Test production signing, installer trust, or live node durability.