Orbitmeter Settlement Network
Use cases

Different units, same window

An API call, a kilowatt hour and a container move are all just units with two counters and a price. That is the whole trick.

API and compute

01

Bill per call without the monthly argument

Readings land every hour from the gateway and the client. A mismatch raises a ticket the same day, not six weeks later.

  • Hourly windows
  • Both-sided readings
  • Prefunded vault optional
Energy

02

Settle generation and supply between operators

Meter readings from substations become signed batches. Settlement follows the same window everyone already reconciles against.

  • Half-hourly readings
  • Split across operators
  • Dispute window per period
Logistics

03

Pay per container moved, not per estimate

Terminal and carrier each submit counts. The window closes on what both submitted, and the difference is visible before invoicing.

  • Daily windows
  • Partner splits
  • Evidence attached per batch
Status

Testnet, two pilots, no production volume

We would rather say this on the homepage than in the third call. If you need a live settlement rail this quarter, we are not it yet.

Bring one invoice your customer disputed.

We will model it as a meter, replay the usage, and show what both sides would have signed at the time.