canonical: https://jentic.com/apis/rootplatform.com/rootplatform

# Rootplatform Root

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.

## For AI agents

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

## Scope

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

## Capabilities

- Create an application
- List all applications
- Retrieve an application
- Requote an application
- Apply application alteration package

## Use cases

### E-Commerce Operations

Use the Root to perform e commerce operations programmatically. The API provides 190 endpoints covering core functionality including create an application, list all applications, retrieve an application.

Example prompt: Call POST /applications to create an application

### 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.

Example prompt: 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.

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

## Key endpoints

| 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 |

## Key resources

- **Quotes** — Operations related to Quotes
- **Policyholders** — Operations related to Policyholders
- **Applications** — Operations related to Applications
- **Policies** — Operations related to Policies
- **Payments** — Operations related to Payments

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### 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.