Install Jentic One Beta

Connect the Root to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Root, 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%2Frootplatform.com%2Frootplatform" | 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%2Frootplatform.com%2Frootplatform" | 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 API.

Create an application

List all applications

Retrieve an application

Requote an application

Apply application alteration package

Use Cases

GET STARTED

Start building with Root API

Explore with Jentic One

View OpenAPI Document

Automated Quotes Management

Automate quotes operations by combining multiple Root endpoints. Agents can list all applications and then retrieve an application in a single workflow.

Call GET /applications to list all applications, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Root endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic tokens manually.

Search Jentic for 'create an application', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

190 endpoints — root is an end-to-end digital insurance platform that enables you to launch new products and digital engagement channels fast.

METHOD

PATH

DESCRIPTION

POST

/applications

Create an application

GET

/applications

List all applications

GET

/applications/{application_id}

Retrieve an application

PUT

/applications/{application_id}

Requote an application

POST

/applications/{application_id}/alteration-packages

Create an application alteration package

GET

/applications/{application_id}/alteration-packages/{alteration_package_id}

Retrieve an application alteration package

POST

/applications/{application_id}/alteration-packages/{alteration_package_id}/apply

Apply application alteration package

POST

/applications/{application_id}/attachments

Add application attachment

POST

/applications

Create an application

GET

/applications

List all applications

GET

/applications/{application_id}

Retrieve an application

PUT

/applications/{application_id}

Requote an application

POST

/applications/{application_id}/alteration-packages

Create an application alteration package

GET

/applications/{application_id}/alteration-packages/{alteration_package_id}

Retrieve an application alteration package

POST

/applications/{application_id}/alteration-packages/{alteration_package_id}/apply

Apply application alteration package

Why Jentic?

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

Setup

Wiring Root by hand means implementing its HTTP basic auth, choosing the right sandbox or production host in its UK or default region, and handling the request plumbing yourself. Through Jentic you install once, import Root from the API Directory, store the basic credentials once, and your agent calls it.

Permission scoping

Root puts the application id in the URL path (/applications/{application_id}/...), so a rule can pin your agent to one application: it can read it and manage its alteration packages and attachments and nothing else. You choose the operations it may call, so ones like applying an alteration package are not included unless you add them.

Credential isolation

Your Root basic credentials 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 an insurance application' or 'add an attachment to an application', and Jentic returns the matching Root operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Shopify

Alternative e commerce API

Choose Shopify when you need a different approach to e commerce operations

Alternative

Stripe

Alternative e commerce API

Choose Stripe when you need a different approach to e commerce operations

FAQs

Specific to using Root API through Jentic.

What authentication does the Root use?

The Root uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I create an application with the Root?

Yes. Use the POST /applications endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Root?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I create an application through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create an application'. Jentic returns the matching Root operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Root have?

The Root exposes 190 endpoints covering quotes, policyholders, applications operations.

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

Yes. Jentic One runs self-hosted, so your own rules decide which Root operations and credentials the agent may use. Because Root puts the application id in the URL path, such as /applications/{application_id}/alteration-packages and /applications/{application_id}/attachments, you can pin the agent to a single application and let it read that application and manage its alteration packages and attachments only. You choose the operations it may call, so sensitive ones like POST /applications/{application_id}/alteration-packages/{alteration_package_id}/apply stay out of reach unless you add them.

Rootplatform Root

Name: Root API
Brand: Root
Availability: InStock

Official vendor OpenAPI document · agent-readyE CommerceStorefrontbasic190 EndpointsREST

For Agents

Programmatically create an application, list all applications. Covers 190 operations with basic authentication.

Use for: I need to an application, I want to all applications, Search for an application, Find all requote an application

Not supported: Does not handle payments, communications, or crm - use for e-commerce only.

Root is an end-to-end digital insurance platform that enables you to launch new products and digital engagement channels fast. The API exposes 190 endpoints secured with basic authentication.

Jentic One on Github View OpenAPI Document