Validation build: the evidence log is live; the pricing example is simulated and places no cover. What that means

For the companies that build software for insurers, brokers, investment advisers and lenders

For software vendors serving regulated finance

Your customers are asked, sometimes years later, what they advised or decided and why: a demands-and-needs note, a suitability statement, a credit assessment. They need to show the record and show it has not been changed since. You integrate RiskRouter once, and every firm on your software can do both. The file stays in your product; only a salted fingerprint of it reaches us.

What changes for your customers

What a firm on your software gets

A fixed record of each advice or decision
When the record is saved, your software sends a salted SHA-256 of it to the evidence log. From that moment it cannot be altered without the fingerprint showing it. The record, and the client’s name, stay in your database. Insurance distribution · Investment advice · Credit
A date nobody can move
Every entry sits in a Merkle tree whose head we sign, time-stamp with two independent authorities (not qualified under eIDAS) and anchor in Bitcoin. Neither your customer, nor you, nor we can back-date a record.
An evidence pack per client
For one client: the record, its salt and the proof. An inspector, an ombudsman or a court checks it offline with public tools, and learns nothing about any other client. See the reference app that builds one.

The work involved

What the integration involves

  1. Take a sandbox key. No form and no contract: one click on /integrate.
  2. Run the example in your language. PHP, C#/.NET, Python and Java, each using only the language’s standard library: a client of 60 to 90 lines and a short demo. Each one records a note’s fingerprint, fetches its proof and verifies it offline. The integration kit.
  3. Wire two calls into your product. POST /api/v2/evidence with the record’s fingerprint when it is saved, and GET /api/v2/evidence/proof when a customer needs the evidence. Up to 500 records go in one call with POST /api/v2/evidence/batch.
  4. Keep the salt with the note, in your own database. Without it nobody, including us, can link a fingerprint back to a person.

The reference broker desk does all of it in one Python file of about 150 lines. Every example in the kit is run against the real API code on every change we make, so an example that stopped working would fail our own build.

The pricing example in the documentation is a worked example, not part of the offer: you record fingerprints of the records your product already produces. The format is published, so you may also implement it yourself without asking us, and check that implementation with the conformance suite: it grades your code against the specification’s own test vectors and checks the exports and proofs your product writes, offline, and gives you a result file that is yours to publish. Nothing about it depends on us.

What we do not do

We will not compete with you or your customers

RiskRouter never contacts the customer, never handles a claim, never holds the carrier relationship and never stores the customer file. Those are fixed boundaries of the product, not a roadmap we have yet to reach. Your customers stay yours.

Working together

What a first integrating vendor can expect

No vendor has integrated yet, so there is no programme to join and no logo wall to be added to. Here is what we can promise today:

A pilot is recorded in a one-page letter of intent: no fees, no exclusivity, no personal data, and either side can end it at any time. What the letter says · What comes next, and what it waits on

Before you commit

For your security and compliance review

The security questionnaire is answered in advance, with evidence and plain answers where the answer is no. The bill of materials shows no third-party package runs in production, status checks the service live, and the continuity plan sets out what your customers keep if we stop and how a backup of the ledger is restored and checked: every day, automatically.