Escrows opened by the allowlisted wallet
We operate the privileged escrow wallet and assign escrows to one broker only.
Broker infrastructure for Gonka inference
Dedicated devshard capacity. One broker API.
OpenBroker handles the escrow wallet, devshard runtime, version routing, observability, and GNK-native accounting for brokers building on the Gonka inference network.
OPENBROKER CONTROL PLANEreserved capacity
Activation
100 GNK
API keys
obk-…
Protocol
v1 / v2
Markup
0%
Each broker gets isolated accounting and capacity. Traffic stops when the broker balance or dedicated devshard capacity is unavailable.
Infrastructure brokers should not run themselves
Running as a broker should be about users, billing, and products — not escrow wallets, devshard rotation, and chain-level accounting.
Dedicated gateway state per broker
Broker traffic is isolated through its own devshardctl instance and on-chain state.
Hard capacity enforcement
OpenBroker does not fall back to public nodes. If capacity is unavailable, the request stops — no silent routing to shared infrastructure.
Built for broker observability
Dashboard and Prometheus metrics are broker-labeled: balance, runtime split, devshard ID, model, request status, token volume, latency surfaces, and escrow state.