How usage-based royalties work
Ventures pay licensing fees for the platform capabilities they consume — identity, fabric, intelligence, and the substrate beneath them. Royalty metering is the engine that records those fees, and it is engineered to the same standard as the platform's money movement: every fee reconstructable, every entry tamper-evident, every aggregate verifiable. The essay automated royalties frames why this is shared infrastructure rather than a billing script.
From metered action to ledger entry
A metered action occurs
Something billable happens in a venture — a transaction processed, a verification run, an agent invocation. The venture reports the action with its user and transaction context. Crucially, the venture never sets the price: pricing is computed platform-side from the venture's subscription and usage terms.
The platform prices the action
The pricing engine evaluates the action against the venture's terms — flat per-action fees or volume percentages — in integer cents. Money never travels through floating-point math.
The entry is signed
The platform signs the entry — venture, action, timestamp, fee — with its deployment key. A signature is not a log line; it is a commitment the platform cannot later disown.
The signature is verified and the entry written
The receiving service verifies the signature against the registered key, then writes the entry through a transactional outbox: the ledger write and the event announcing it commit atomically, so neither can exist without the other.
The append-only metering ledger
The ledger has three guarantees, all structural:
- Append-only. Entries are never updated or deleted. A correction is a new entry referencing the old one — history is never rewritten, even to fix a mistake.
- Signed. Every entry carries the originating platform's signature, verifiable against the registered public key.
- Hash-chained. Each entry commits to the previous entry's hash —
H(n) = SHA256(H(n-1) ‖ venture ‖ action ‖ timestamp ‖ fee)— so altering any historical entry breaks every link after it.
venture_id: example-venture
action: transaction.processed
timestamp: "2026-07-25T09:00:00Z"
amount_cents: 10000 # integer cents, never float
royalty_fee_cents: 250
previous_hash: "9c4f…a1" # commits to the entry before it
current_hash: "2be7…d4" # SHA-256 over this entry + previous
signature: "platform deployment key signature"The nightly chain-parity check
Once a day, an automated check recomputes the entire hash chain and reconciles it against the stored ledger. A mismatch is not a warning: the billing run blocks, a high-priority alert reaches the operations dashboard, and licensing tokens freeze. The same fail-closed posture the platform takes for data isolation applies to money.
The monthly loop
On the monthly cycle, entries aggregate per venture into invoices, and settlement routes through governed treasury paths — billing & treasury splits covers how splits post and hold. Ventures settling in native utility tokens lock the monthly fee equivalent in escrow as part of the same run.
Boundary
This page describes the metering model. Fee schedules, terms, and any venture's actual ledger state are contractual and live in authenticated surfaces — nothing here states or implies any venture's pricing.