> ## Documentation Index
> Fetch the complete documentation index at: https://docs.b3iq.org/llms.txt
> Use this file to discover all available pages before exploring further.

# 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.

**Sandbox is not protocol proof**

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.

## Related

**[Hosted Gateway](/developers/hosted-gateway)**

Use hosted endpoint examples against seeded sandbox credentials.
  **[Errors](/developers/errors)**

Confirm client behavior against stable machine codes.
  **[Current Status](/operations/current-status)**

Separate sandbox evidence from live pilot evidence.