Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Root Insurance website screenshot

Root Insurance

Root Insurance is a usage-based auto insurance company that prices policies primarily based on driving behavior captured via smartphone telematics. Root provides a REST API platform for insurers, MGAs, and distribution partners to build, embed, and operate insurance products — covering quoting, policy administration, claims processing, premium collections, and data management. The Root Bind API enables partners to embed auto insurance quoting and checkout directly into their applications.

agent ready

Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.

Kin Score

API Evangelist profiles Root Insurance the way a machine reads it — 311 machine-readable artifacts across 18 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Root Insurance scores 51.0/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 51.0/100 · developing
Contract Quality 15.3 / 25
Developer Ergonomics 4.3 / 20
Commercial Clarity 10.0 / 20
Operational Transparency 2.7 / 13
Governance 8.8 / 12
Discoverability 10.0 / 10
Regulatory · Insurance 7.5 / 15
Agent readiness — 48/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 15 / 15
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Root Insurance

Each block below is one kind of artifact we hold for Root Insurance. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 18

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

Individual APIs this provider publishes, each with its own machine-readable definition.

Root Bind API

The Root Bind API enables distribution partners to embed auto insurance quoting, checkout, and servicing within their own applications. Supports both a hosted experience (Root-m...

Root Insurance Applications API

The Applications API from Root Insurance — 16 operation(s) for applications.

Root Insurance Calls API

The Calls API from Root Insurance — 4 operation(s) for calls.

Root Insurance Claims API

The Claims API from Root Insurance — 31 operation(s) for claims.

Root Insurance Complaints API

The Complaints API from Root Insurance — 10 operation(s) for complaints.

Root Insurance Data exports API

The Data exports API from Root Insurance — 9 operation(s) for data exports.

Root Insurance Data stores API

The Data stores API from Root Insurance — 4 operation(s) for data stores.

Root Insurance Embed API

The Embed API from Root Insurance — 2 operation(s) for embed.

Root Insurance Files API

The Files API from Root Insurance — 1 operation(s) for files.

Root Insurance Leads API

The Leads API from Root Insurance — 2 operation(s) for leads.

Root Insurance Notifications API

The Notifications API from Root Insurance — 3 operation(s) for notifications.

Root Insurance Payment Methods API

The Payment Methods API from Root Insurance — 7 operation(s) for payment methods.

Root Insurance Payments API

The Payments API from Root Insurance — 6 operation(s) for payments.

Root Insurance Policies API

The Policies API from Root Insurance — 32 operation(s) for policies.

Root Insurance Policyholders API

The Policyholders API from Root Insurance — 7 operation(s) for policyholders.

Root Insurance Quotes API

The Quotes API from Root Insurance — 1 operation(s) for quotes.

Root Insurance Secret keys API

The Secret keys API from Root Insurance — 2 operation(s) for secret keys.

Root Insurance Webhooks API

The Webhooks API from Root Insurance — 9 operation(s) for webhooks.

Scroll within the panel for all 18 ·

Pricing Plans 1

Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.

Published pricing tiers and plan structures.

Root Plans Pricing

4 plans

PLANS

Rate Limits 1

Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.

Documented rate limits and quota policies.

Root Rate Limits

0 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.

Cost, billing, and metering signals for API financial operations.

Root Finops

FINOPS

Semantic Vocabularies 1

JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.

JSON-LD contexts and semantic vocabularies used across these APIs.

Root Platform Api Context

0 classes · 272 properties

JSON-LD

Spectral Rules 1

Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.

Root Insurance API Rules

5 rules · 4 warnings

SPECTRAL

JSON Schema 85

Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.

Standalone JSON Schema definitions for this provider's data models.

actor-type

0 properties

JSON SCHEMA

alteration-package

5 properties

JSON SCHEMA

alteration-packages

0 properties

JSON SCHEMA

application-alteration-hook

9 properties

JSON SCHEMA

application-alteration-hooks

0 properties

JSON SCHEMA

application-alteration-package

14 properties

JSON SCHEMA

application-alteration-packages

0 properties

JSON SCHEMA

application

27 properties

JSON SCHEMA

applications

0 properties

JSON SCHEMA

attachment

7 properties

JSON SCHEMA

attachments

0 properties

JSON SCHEMA

bank-name

0 properties

JSON SCHEMA

beneficiaries-request

0 properties

JSON SCHEMA

beneficiaries

0 properties

JSON SCHEMA

beneficiary-relationship

0 properties

JSON SCHEMA

call

12 properties

JSON SCHEMA

calls

0 properties

JSON SCHEMA

cellphone-string

0 properties

JSON SCHEMA

cellphone

2 properties

JSON SCHEMA

claim

27 properties

JSON SCHEMA

claims

0 properties

JSON SCHEMA

collection-type

0 properties

JSON SCHEMA

complaint

13 properties

JSON SCHEMA

complaints

0 properties

JSON SCHEMA

custom-event-type

0 properties

JSON SCHEMA

daily-frequency

1 properties

JSON SCHEMA

data-export-run-log-item

4 properties

JSON SCHEMA

data-export-run-log-items

0 properties

JSON SCHEMA

data-export-run

6 properties

JSON SCHEMA

data-export-runs

0 properties

JSON SCHEMA

data-store-entities

0 properties

JSON SCHEMA

data-store-entity

8 properties

JSON SCHEMA

data-store

10 properties

JSON SCHEMA

data-stores

0 properties

JSON SCHEMA

failure-action

0 properties

JSON SCHEMA

fulfillment-request

12 properties

JSON SCHEMA

https-adapter

5 properties

JSON SCHEMA

lead

17 properties

JSON SCHEMA

leads

0 properties

JSON SCHEMA

monthly-frequency

2 properties

JSON SCHEMA

note

2 properties

JSON SCHEMA

notes

0 properties

JSON SCHEMA

notification-data

0 properties

JSON SCHEMA

notification-email-data

7 properties

JSON SCHEMA

notification-other-data

4 properties

JSON SCHEMA

notification-sms-data

4 properties

JSON SCHEMA

notification

11 properties

JSON SCHEMA

notifications

0 properties

JSON SCHEMA

payment-batch

18 properties

JSON SCHEMA

payment-batches

0 properties

JSON SCHEMA

payment-charge-type

0 properties

JSON SCHEMA

payment-coupon

12 properties

JSON SCHEMA

payment-coupons

0 properties

JSON SCHEMA

payment-create-async

0 properties

JSON SCHEMA

payment-create

15 properties

JSON SCHEMA

payment-creates-async-array

0 properties

JSON SCHEMA

payment-details

2 properties

JSON SCHEMA

payment-method

18 properties

JSON SCHEMA

payment-response

26 properties

JSON SCHEMA

payment-status

0 properties

JSON SCHEMA

payment-type

0 properties

JSON SCHEMA

payment-update

5 properties

JSON SCHEMA

payment-updates

0 properties

JSON SCHEMA

payment

30 properties

JSON SCHEMA

policies

0 properties

JSON SCHEMA

policy-status

0 properties

JSON SCHEMA

policy

41 properties

JSON SCHEMA

policyholder-request

20 properties

JSON SCHEMA

policyholder

26 properties

JSON SCHEMA

policyholders

0 properties

JSON SCHEMA

premium-type

0 properties

JSON SCHEMA

quote-package

12 properties

JSON SCHEMA

quote-packages

0 properties

JSON SCHEMA

s3-adapter

6 properties

JSON SCHEMA

scheduled-data-export

11 properties

JSON SCHEMA

scheduled-data-exports

0 properties

JSON SCHEMA

secret-keys-list

0 properties

JSON SCHEMA

secret-keys

10 properties

JSON SCHEMA

sftp-adapter

6 properties

JSON SCHEMA

webhook-queue-event

13 properties

JSON SCHEMA

webhook-subscription-event

0 properties

JSON SCHEMA

webhook-subscription-events

0 properties

JSON SCHEMA

webhook

14 properties

JSON SCHEMA

webhooks

0 properties

JSON SCHEMA

weekly-frequency

2 properties

JSON SCHEMA

Scroll within the panel for all 85 ·

Examples 199

Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.

Example request and response payloads for these APIs.

Approve Claim Request

2 fields

EXAMPLE

Approve Claim Response 200

12 fields

EXAMPLE

Cancel Policy Request

1 fields

EXAMPLE

Cancel Policy Response 200

26 fields

EXAMPLE

Claim Add Note Request

1 fields

EXAMPLE

Claim Link Policy Request

3 fields

EXAMPLE

Close Claim Request

1 fields

EXAMPLE

Close Claim Response 200

12 fields

EXAMPLE

Create Call Request

11 fields

EXAMPLE

Create Call Response 200

11 fields

EXAMPLE

Create Claim Request

9 fields

EXAMPLE

Create Claim Response 200

15 fields

EXAMPLE

Create Data Store Request

4 fields

EXAMPLE

Create Lead Request

7 fields

EXAMPLE

Create Lead Response 200

12 fields

EXAMPLE

Create Quote Request

2 fields

EXAMPLE

Create Secret Key Request

3 fields

EXAMPLE

Create Webhook Request

5 fields

EXAMPLE

Goodwill Claim Request

2 fields

EXAMPLE

Goodwill Claim Response 200

12 fields

EXAMPLE

Issue A Policy Request

2 fields

EXAMPLE

Issue A Policy Response 200

24 fields

EXAMPLE

No Claim Request

1 fields

EXAMPLE

No Claim Response 200

12 fields

EXAMPLE

Ping Webhook Response 200

1 fields

EXAMPLE

Policy Add Note Request

1 fields

EXAMPLE

Reopen Claim Request

1 fields

EXAMPLE

Reopen Claim Response 200

12 fields

EXAMPLE

Repudiate Claim Request

1 fields

EXAMPLE

Requote Policy Request

1 fields

EXAMPLE

Requote Policy Response 200

26 fields

EXAMPLE

Retrieve Call Response 200

11 fields

EXAMPLE

Send To Capture Request

1 fields

EXAMPLE

Send To Review Request

1 fields

EXAMPLE

Send To Review Response 200

12 fields

EXAMPLE

Update Claimant Request

6 fields

EXAMPLE

Update Data Store Request

1 fields

EXAMPLE

Update Payment Request

1 fields

EXAMPLE

Update Payment Response 200

22 fields

EXAMPLE

Update Policy Request

2 fields

EXAMPLE

Update Policy Response 200

22 fields

EXAMPLE

Update Webhook Request

3 fields

EXAMPLE

Updating A Claim Request

5 fields

EXAMPLE

Upsert Secret Key Request

2 fields

EXAMPLE

Scroll within the panel for all 199 ·

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Root Authentication

http · 1 scheme

SECURITY

Root Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Root Vulnerability Disclosure

disclosure policy published

SECURITY

Agentic Access 1

An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.

Recommended x-agentic-access execution contracts for AI agents.

Root Agentic Access

198 operations · 128 acting · 1 human-in-the-loop

198 operations · 128 acting

AGENTIC

Resources

Every other property we hold for Root Insurance — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Build 1

SDKs, sample code, and the tooling you integrate with

Operate 2

Status, limits, changes, and where to get help

Commercial 3

Pricing, plans, and the legal terms of use

Company 3

The organization behind the API

Other 1

Properties that don't map to a standard resource type

← All providers · Data indexed from github.com/api-evangelist/root · machine-readable index on apis.io