For broker-software vendors

What changes for your brokers

What a broker on your package gets

A fixed record of the advice

When the broker saves a demands-and-needs note, your software records a salted SHA-256 of it with us. From that moment the note cannot be altered without the fingerprint showing it. The note itself, and the customer’s name, stay in your database.

Quotes they cannot be accused of editing

Quotes priced through the API with the broker’s key are appended to a hash-chained ledger that the database refuses to edit or delete, and whose head is signed and timestamped in Bitcoin.

An evidence pack per customer

For one customer: the note, its salt and the two proofs. An inspector can check it offline with public tools, and learns nothing about any other customer. 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 prices a quote, records it, replays it safely, records a note’s fingerprint, exports and proves. The integration kit.
3. Wire three calls into your product. POST /api/v1/quote with the broker’s key and an Idempotency-Key derived from your own quote id, so a double-click never records twice; POST /api/v2/evidence with the note’s fingerprint; and GET /api/v2/evidence/proof or GET /api/v1/ledger/export when a broker needs the evidence.
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.

You can use the evidence log without our pricing at all: record fingerprints of the advice records your product already produces. The format is published, so you may also implement it yourself without asking us.

What we do not do

We will not compete with you or your brokers

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 brokers 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:

• Your developers talk directly to the person who builds the API.
• What you need goes to the top of what gets built next, if it fits the rules the product keeps.
• Your name appears on this site only once you have agreed to it in writing.
• No exclusivity and no lock-in: the specification is open and the verifiers are free.
• The sandbox is free. There are no commercial terms yet; we would agree them with you, not announce them to you.

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 brokers keep if we stop.