Single-city companies and operators getting started.
Per driver · / month
- Per active driver, tiered by fleet size
- Larger fleet, lower per-driver cost
- Monthly admin charge per node
- Support, platform & protocol updates included
Pricing · the model
The model separates what it costs to run your node from what it costs to be connected to the network. Every network charge reconciles against verifiable ledger events, you see exactly what you pay and why.
Dispatch, payments, white-label apps and panels, your sovereign operation, billed by the scale you run.
The network fee for roaming between nodes and settling across them, reconciled against verifiable ledger events, never an opaque charge.
Concrete amounts are set by contract per region, scale and integrations. This page describes the model, not a public price list.
Who connects
From a single-city operator to a sovereign national network, the same protocol, priced to the scale you run.
Single-city companies and operators getting started.
Per driver · / month
Multi-fleet operators scaling across a region.
Volume · bonuses
Operators interoperating across cities.
Per txn · roaming
Cities and countries running mobility as public infrastructure.
Talk to us
Tier names describe who connects, not a public rate card. Network-plane pricing is indicative, roaming and the ledger are roadmap, not billed today.
Agents & merchants
For AI agents and merchants moving people and things through the network, pricing follows the work the protocol does on your behalf.
Per dispatchBilled per dispatch routed through the protocol
Scales with the work you send, not headcount
Free sandboxFree environment for development
Certify your integration before going live
Build status. The network layer (registry, ledger, roaming, protocol) is on the roadmap and shown as a target architecture, not a live service. Sandbox and certification flows describe the model. The operation plane (node, apps, dispatch, payments, tracking) is what ships today.
Always included
No tier strips out what makes a node yours. These come with the model, not as add-ons.
Transparency
You see exactly what you pay and why. The network fee isn't an opaque line item it settles over events you can audit yourself.
What it costs to run your sovereign operation, billed by scale.
What it costs to be connected, settled over verifiable ledger events.
Every charge maps to an event you can audit. No surprises, no black box.
Roadmap. The immutable ledger that backs this reconciliation is in active build. Reconciliation against ledger events describes the model it is not yet a live, audited service.
Talk to us
Concrete amounts are set by contract. Tell us what you operate and we'll map the model to it.
Usage-based pricing: per-dispatch and per-request fees for the Node, with network access priced separately, and every charge reconciled against verifiable ledger events. Sandbox access is free.
Yes. The Node deploys on your infrastructure, a sovereign cloud, or on-prem, and trips, passengers, fares, and local payments stay in your node by design.
Real-time trip dispatch turns orders into driver matches in about 1 second, across moto, car, van, shuttle, bus, and freight.
An immutable, append-only, signed record of driver reputation and network payments, validated by the network nodes. Private by design: personal data and routes never touch the ledger.
Yes. The Agent API exposes dispatch, fleet coordination, and merchant delivery over one open, versioned protocol, with a free sandbox for testing.