Validation build: prices are simulated and no cover is in force. What that means

Usage · counted live, from the ledger

How much is recorded, and by whom

Every figure on this page is counted from the quote ledger and the evidence log at the moment you load it, by your browser, from a public endpoint. Nothing here is typed in by us, so it cannot show traction we do not have. Where a number is zero, it says zero.

Right now

Entries, and who recorded them

…
entries in both logs
…
in the last 28 days
…
recorded by keys that are not ours
…
distinct keys recording, 28 days

The third figure is the one that matters. Everything else on this site can be produced by our own effort. An entry recorded with a key that is not ours means somebody outside decided the API was worth writing code against, ran it, and sent a key. Self-serve sandbox keys count as outside and are also shown separately below, because a key nobody had to ask us for is weaker evidence than a contracted one.

Detail

By log, and by origin of the key

FigureCountNote
Quote ledger (v1) entries…
Evidence log (v2) entries…
Entries by keys that are not ours…
… of which self-serve sandbox keys…
Distributors with a key…

Twelve weeks

Entries per calendar week

Week starting (Monday)QuotesEvidenceNot ours
counting…

Adoption by people who are not us

Witnesses and conformant implementations

none yet
independent witnesses
none yet
conformance results published by others

Counted from witnesses/ and conformance-results/ in the repository when this page was built. A witness is listed only when it publishes its own key; a result only when its implementer publishes it themselves. Become a witness · Run the conformance suite

How this is counted

What the figures mean, and what they do not

Where the numbers come from
GET /api/v1/usage, a public endpoint that counts the two logs on request and returns nothing but numbers and week dates: no identifier, no premium, no record. It is cached for five minutes at the edge. API reference.
“Ours”
Entries recorded with RiskRouter’s own validation keys, and entries that predate attribution. Everything else is “not ours”, including self-serve sandbox keys.
What an entry is not
Not a customer, not a policy, not revenue. It is one record sealed into a log. No cover is in force anywhere behind these figures; this is a validation build.
Why publish it at all
Because a number an outsider can fetch is worth more than a number on a slide, and because a small number said plainly is the only kind that can be believed when it grows. Every other claim we make, and where to check it.