For gateways and broker platforms, the right insurer code behind every API call

A gateway or broker platform sits in the middle. On one side are your partners: agents' apps, dealer systems, fintech apps and your own web journeys. On the other side are the insurers, each with its own quote API and its own vehicle master. Your partners send you a registration number or a set of RC details. Every insurer wants its own code. Whatever falls into the gap between the two lands on your desk.

Where the cost hides

It rarely shows up as one big line item. It shows up as a mapping desk that never quite catches up, a support queue full of "quote not coming for this vehicle", and partners who quietly send their tricky vehicles somewhere else.

A few things make it worse for a platform than for anyone else:

• You map for everyone. One unmapped variant breaks the quote for every partner who sells that car, not just one.
• Your partners can't fix it themselves. They don't see the insurer masters, so every gap turns into a ticket for your team.
• Adding an insurer means mapping its whole master before the first quote, and keeping it current afterwards.
• A wrong code costs more than a missing one. The missing one gets reported. The wrong one becomes a policy with the wrong variant on it, and the correction comes back to you weeks later as an endorsement or a complaint.

What changes with Dorvy Tech

You send the vehicle fields you already have from the RC: maker and model as written, fuel, cc, seats, body type, norms and class. One call returns the listing and code for every insurer master you use, in about 7 ms per vehicle for five insurers. That's quick enough to run inside a live quote, so you don't need a batch job and a lookup table that goes stale.

Every pick carries a confidence level of HIGH, MEDIUM or LOW, and that's what lets you change how your team works. You decide which levels go straight to the quote and which go to a short review queue, with the closest alternatives already listed, so a reviewer chooses from a few options instead of searching a master. Most teams start cautious and loosen it once they've seen the numbers on their own vehicles. When a vehicle isn't in an insurer's master at all, the answer says "no listing" with the reason. You can tell the partner plainly, instead of sending a request you know will fail.

It runs on your own servers on an ordinary CPU, with no GPU and no outbound calls, so your security review stays short. It needs no registration numbers or owner details. When you add an insurer, we set its master up and test it with you before it goes live.

How much better, and what it's worth

On our held-out test of 150 real RC records across five insurer masters, Dorvy Tech picked the exact listing 77.0% of the time. The best standard matcher we tried managed 66.2%. More important for a platform, it made less than half the wrong picks, about 13% against 32%. The test set is deliberately hard, so your own numbers will differ, and the free comparison measures them on your vehicles. How we measured has the detail.

To put a value on it, count three things for a month: quote requests that failed or were abandoned because of the vehicle, hours your team spent mapping and fixing, and endorsements raised to correct a vehicle. Then ask what each one costs. For example, with made-up numbers: a platform that fixes 1,500 vehicle problems a month at 6 minutes each spends 150 hours on it. That's most of one person's month. Halve the wrong picks, give the reviewer the alternatives up front, and most of that person's month goes back to other work.

The quotes you stop losing are harder to count and usually worth more. Every partner who gets a quote for a car they couldn't quote before is a sale you'd otherwise never have seen.

Getting started

Start with the free comparison. Send about 300 recent vehicles with the code you use today for each insurer. Within 3 working days you get our pick, confidence and alternatives next to yours, and your team decides which is right. If it beats what you have, we run a pilot on your own traffic.