Install Jentic One Beta

Connect the Root Bind API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Root Bind API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fjoinroot.com%2Fjoinroot" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fjoinroot.com%2Fjoinroot" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Root Bind API.

Create and update auto insurance quotes with applicant and vehicle data

Retrieve available coverages and coverage rules for a quote or by state

Generate prefill reports to pre-populate quotes from limited applicant input

Finalize a quote and bind an active policy through the bind endpoint

Affirm legal documents required to complete a binding transaction

GET STARTED

Start building with Root Bind API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Root Bind API for, with concrete tasks.

★ Embedded auto insurance quoting

Partners selling cars, financial products, or telematics services can offer Root auto insurance inline in their checkout. The API supports the full path: validate the address, create a quote, fetch available coverages and rules for the applicant's state, finalize the chosen coverages, and bind the policy. End-to-end the flow can complete in a single session without leaving the partner's UI.

Call POST /quotes with applicant data, GET /quotes/{quoteId}/coverages to fetch options, POST /quotes/{quoteId}/finalize, then POST /quotes/{quoteId}/bind to issue the policy

Agency portal reporting

Independent agencies that produce business through Root can build internal reporting dashboards using the agency-scoped list endpoints. GET /agency/quotes and GET /agency/policies surface volume across the book, and GET /agency/agents/{agentId}/policies isolates production by individual agent. This lets agency principals run loss-ratio and conversion analysis without exporting CSVs from Root's portal.

Call GET /agency/quotes and GET /agency/policies, then aggregate by agent_id to produce a weekly conversion report for the agency principal

Prefill-driven low-friction quoting

Consumer-facing partners can drastically shorten quote forms by using prefill reports - POST /prefill takes minimal applicant input and returns enriched data that pre-populates the quote. This reduces drop-off on insurance forms which historically ask for many fields. The returned prefillId can then be referenced when creating the actual quote.

Call POST /prefill with the applicant's name and address, then POST /quotes referencing the returned prefillId to create a fully populated quote

Agent-orchestrated bind via Jentic

An AI assistant integrated into a partner agency's CRM can drive the full quote-to-bind sequence using Jentic. The agent calls Jentic operations in order - quote, coverages, finalize, bind - with the partner's stored bearer token injected at execution. This keeps the bearer credential out of the agent's reasoning context while still letting the assistant complete the binding workflow.

Use Jentic to search 'create a Root quote', then chain GET coverages, POST finalize, and POST bind operations using the agency's stored bearer token

Key Endpoints

35 endpoints — root insurance's bind api is the partner-facing surface that lets brokers, agencies, and embedded-insurance platforms quote, finalize, and bind auto insurance policies in root's system.

METHOD

PATH

DESCRIPTION

POST

/quotes

Create a new auto insurance quote

GET

/quotes/{quoteId}/coverages

Get available coverages for a quote

POST

/quotes/{quoteId}/finalize

Finalize a quote

POST

/quotes/{quoteId}/bind

Bind a policy

POST

/prefill

Create a prefill report

GET

/policy/{policyId}

Get policy summary

POST

/legal-documents/{documentId}/affirm

Affirm a legal document

GET

/agency/quotes

List agency quotes

POST

/quotes

Create a new auto insurance quote

GET

/quotes/{quoteId}/coverages

Get available coverages for a quote

POST

/quotes/{quoteId}/finalize

Finalize a quote

POST

/quotes/{quoteId}/bind

Bind a policy

POST

/prefill

Create a prefill report

GET

/policy/{policyId}

Get policy summary

POST

/legal-documents/{documentId}/affirm

Affirm a legal document

GET

/agency/quotes

List agency quotes

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Root Bind API by hand means learning its bearer auth, refreshing the tokens it issues, and threading quote and policy ids through the quote-to-bind flow yourself. Through Jentic you install once, import the Root Bind API from the API Directory, store the token once, and your agent calls it.

Permission scoping

Root puts the quote id in the URL path (/quotes/{quoteId}/...), so a rule can pin your agent to one quote: it can read coverages, finalize, and bind that quote and nothing else. You choose the operations it may call, so ones like affirming legal documents or reading agency reporting are not included unless you add them.

Credential isolation

Your Root bearer token and its refresh token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create a Root insurance quote' or 'bind a policy', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Root Bind API through Jentic.

What authentication does the Root Bind API use?

The Root Bind API uses HTTP bearer authentication. Tokens are obtained via POST /auth/token and refreshed via POST /auth/token/refresh. Jentic stores the token encrypted and refreshes it automatically so the bearer never enters the agent's context.

Can I bind a Root policy end-to-end through the API?

Yes. The flow is POST /quotes to create the quote, GET /quotes/{quoteId}/coverages to fetch options, POST /quotes/{quoteId}/finalize to lock selections, then POST /quotes/{quoteId}/bind to issue the policy. Legal affirmations and payment method setup are required before bind can succeed.

What environment does the base URL point to?

The published spec uses the partner-testing host (app.partner-testing.joinroot.com). Production hosts are issued to partners after onboarding - switch the base URL after partner certification, the operations remain identical.

How do I quote a Root policy through Jentic?

Search Jentic for 'create a Root insurance quote', load POST /quotes, and execute with the applicant payload. Jentic injects the partner bearer token and returns the new quoteId for follow-on calls. Get started with Jentic One, the self-hosted execution layer.

Are coverage rules state-specific?

Yes. Auto insurance coverages and rules vary by US state. Use GET /coverages/by-state/{state} and GET /coverage-rules/by-state/{state} before quoting to surface only the options legal in that state, or GET /quotes/{quoteId}/coverages once a quote is created.

Can I report on agency-level production?

Yes. GET /agency/quotes, GET /agency/policies, and the per-agent variants (GET /agency/agents/{agentId}/quotes and /policies) return the agency's book filtered by agent. This is the surface to use for production dashboards and conversion reporting.

Can I limit what my agent is allowed to do with the Root Bind API?

Yes. Because Jentic One is self-hosted, your own rules decide which Root Bind operations and credentials the agent may use, and it can call nothing else. Root puts the quote id in the URL path (/quotes/{quoteId}/...), so a rule can pin the agent to a single quote, letting it read coverages, finalize, and bind that quote only. Operations like affirming legal documents or reading agency reporting (GET /agency/quotes) stay off-limits unless you explicitly grant them.

Joinroot Root Bind API

AI ReadinessAI-Aware (B+)70/100

See full scorecard

Official vendor OpenAPI document · agent-readyFinanceBankingbearer35 EndpointsREST

For Agents

Quote, finalise, and bind Root auto insurance policies, retrieve coverage rules by state, manage prefill reports, payment methods, and legal document affirmations on behalf of partner agencies.

Use for: I need to create a Root auto insurance quote for a customer in Ohio, Get the coverage rules available in Texas before quoting, Generate a prefill report so the applicant only enters their address, Finalize quote q_abc123 and bind the policy

Not supported: Does not handle claims processing, telematics scoring, or post-bind policy servicing changes - use for quote-to-bind workflows, policy summaries, and agency-level reporting only.

Root Insurance's Bind API is the partner-facing surface that lets brokers, agencies, and embedded-insurance platforms quote, finalize, and bind auto insurance policies in Root's system. The API covers the full quote lifecycle - creating quotes, fetching available coverages and rules by state, finalising and binding policies, and managing prefill reports, payment methods, and legal document affirmations. It is the right tool when a partner workflow needs to issue Root policies end-to-end without redirecting customers into Root's own UI.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

42%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

50%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4

48%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

52%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: A-Signals: 1

75%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Root Bind API to your agent

Capabilities

Start building with Root Bind API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Joinroot Root Bind API

Jentic AI Readiness Score

Root Bind API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness