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
You pay for the value of the network, not for an opaque license.
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.
Running your node
What it costs to operate
Dispatch, payments, white-label apps and panels — your sovereign operation, billed by the scale you run.
Being connected
What it costs to interoperate
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
One model, scaled to who you are.
From a single-city operator to a sovereign national network — the same protocol, priced to the scale you run.
Multi-fleet operators scaling across a region.
Volume · bonuses
- Everything in Operators
- Initial waivers by driver threshold
- Discounts that grow with the fleet
- Scheme proven in government proposals
Operators interoperating across cities.
Per txn · roaming
- Everything in Fleets
- Per cross-network transaction fee
- Originating network settles with the executing one
- Network fee settles over ledger events Roadmap
Cities and countries running mobility as public infrastructure.
Talk to us
- Sovereign-node licensing + network fee
- Tailored institutional model
- Bonus structures by onboarded drivers
- Data sovereignty, governance & audit
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
Build on the protocol — pay per dispatch.
For AI agents and merchants moving people and things through the network, pricing follows the work the protocol does on your behalf.
Per dispatch
A fee per dispatch processed through the protocol — you pay for movement that actually happens, not for a seat.
- Billed per dispatch routed through the protocol
- Scales with the work you send, not headcount
Free sandbox
Plans with a free sandbox for development and certification — build and verify your integration before a single live charge.
- Free 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
The same foundation, at every scale.
No tier strips out what makes a node yours. These come with the model, not as add-ons.
- White-label apps with your brand
- Data sovereignty
- Reputation and payments in the ledger
- Protocol and SDK access
Transparency
Every network charge reconciles against verifiable ledger events.
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.
Node cost
What it costs to run your sovereign operation — billed by scale.
Network fee
What it costs to be connected — settled over verifiable ledger events.
Reconciliation
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
Get a model built for your region, scale and integrations.
Concrete amounts are set by contract. Tell us what you operate and we'll map the model to it.