Independent metering for coordinated capacity.

We’re a meter. We read data from every party in a coordinated capacity arrangement and keep one sealed record of what was delivered.

V-Meter doesn’t dispatch, trade, or own anything in a sleeve. We just measure.

How coordinated capacity works

Transmission upgrades take 5 to 7 years, and large loads can’t wait that long. A load can connect early on a flexible basis, but then it can be curtailed when the grid gets tight, and most large loads don’t want that risk. Batteries elsewhere on the grid can take it on by discharging where the congestion is. V-Meter provides the proof of action across time, space, and multiple parties.

1

Load connects early

Upgrades aren’t built yet, so the grid can curtail the load.

V-Meter reads consumption and price.
2

Batteries offer to go first

Remote batteries reprice so they get dispatched ahead of the load.

V-Meter reads availability and price.
3

Batteries discharge

Congestion eases and the load keeps running.

V-Meter reads Operator instructions and grid conditions.
4

The pool is reconciled

The Program Manager settles using one shared set of numbers.

V-Meter publishes delivered, committed, and entitled MW per interval.

What independent means here

V-Wire pushes for rules that let sleeves exist. V-Meter has a smaller job: record what happened, the same way for every party.

How we stay neutral

  • Same formula for every party. Every party is measured the same way.
  • Checkable. The formula is named and versioned, and inputs are sealed, so any interval can be replayed.
  • Outside timestamp. Each interval is fingerprinted and timestamped by an outside service.
  • Private data stays private. Raw readings stay with whoever sent them. Only verified results are shared.

What we stay out of

  • Dispatch and trading. We never instruct a battery or place a bid.
  • Ownership. We hold no stake in any asset or sleeve.
  • Picking sides. V-Meter stays neutral throughout.
  • Money. We report megawatts. Prices and payments are between the parties and the Program Manager.

Who sends what, and who reads it

The Program Manager structures the pool and runs settlement. The operator (QSE, etc.) runs dispatch in real time. V-Meter takes in data from each of them and gives everyone the same record back.

Flexible loadconsumption, price Battery ownertelemetry, availability Operatordispatch, cosigned intervals Program Managersleeve allocations V-Meter read, reconcile, seal delivered · committed · entitled public grid data (cross-check) Program Managersettles the pool Insurers and lendersread the record Load and battery ownersverify what was delivered

What we are building

Every interval goes through the same four steps. The result is tamper-evident, meaning a change after the fact can be detected.

Each interval gets a fingerprint anchored to an outside timestamp.

Read
Data comes in through the Ingest API, tagged with who sent it.
Reconcile
The named formula runs on the sealed inputs. Delivered is compared with committed, and the Program Manager’s allocations give each party’s entitlement.
Seal
Everything goes into an append-only log, one fingerprint per interval. Corrections are added as new entries.
Report
The verified record is published, insurers are notified, and results are checked against public grid data.

Become a design partner

We’re working with a few early partners on the first sleeves. You’d get preferred terms and a say in the API schema. It usually starts with an API review, then a replay of historical intervals, then a live pilot.

Get in touch