Rules in. Proof out.

Two ways to send driving records, one set of results. Your system calls a versioned API, or your team uploads records in the portal. Either way, you get a recommendation for each driver and the reasons behind it.

How an integration works

  1. 01

    Create a case.Your system opens a case over the API and attaches the drivers' MVRs as PDFs. Or a signed-in user uploads them in the portal.

  2. 02

    Indicary applies your rules.It reads each record and checks each driver against your program's rules. It works only on the records you send.

  3. 03

    Get the results.Read the case at any time, and receive a signed webhook when a driver's recommendation is ready, when the case completes, and when a recommendation changes.

What comes back

A recommendation, and the reasons for it

  • A recommendation for each driver
  • The reasons behind any referral or adverse recommendation
  • A needs-human-review flag, with reason codes, when a record needs a person's eyes
  • A reading-confidence score
  • The name and version of the rules that were applied
  • Where each driver's record sits in the document (the page range)

Recommendations are never edited

When a new document arrives, a document is withdrawn or the roster changes, Indicary produces a new recommendation linked to the previous one and sends a webhook. The history stays intact.

Recommendation only

The API never binds, rates or acts on a policy. Your underwriter makes the call.

Records

What Indicary reads

PDF motor vehicle records in the common layouts from the main MVR providers, using the standard violation codes.

Indicary works alongside your MVR provider: keep them for the records, and Indicary works out eligibility on top. It never orders or pulls records itself.

It works alongside intake tools too. Intake collects what the applicant says; Indicary shows what the record says.

Access and security

  • Per-customer API credentials over HTTPS
  • Each customer can reach only its own data
  • Credentials rotate without downtime
  • Separate sandbox and production credentials
  • Customer data is hosted in the United States.
Getting started

Build against a sandbox

Integrating customers get a sandbox with synthetic data, a machine-readable API specification and an integration guide, along with their sandbox credentials.

API documentation is shared on request.

Questions

Do you connect to motor vehicle agencies or MVR providers?

No. You send the records you already obtain. Indicary doesn't order or pull records, and doesn't connect to agencies or providers.

Can we test before going live?

Yes. The sandbox uses synthetic data and its own credentials, separate from production.

What if more records arrive after a recommendation?

Send them to the same case. Indicary produces a new recommendation linked to the earlier one, and your webhook tells you it changed.

Plan your integration

Tell us about your system and how driving records reach your underwriters today.

Talk to us