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

# Vertafore API

Insurance agency management software API. The API exposes 4 endpoints secured with apiKey authentication.

## For AI agents

Programmatically list policies, get policy. Covers 4 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- List policies
- Get policy
- Create claim
- Query and filter Vertafore API records by parameters
- Monitor Vertafore API operational status and events

## Use cases

### Developer Tools Operations

Use the Vertafore API to perform developer tools operations programmatically. The API provides 4 endpoints covering core functionality including list policies, get policy, list clients.

Example prompt: Call GET /policies to list policies

### Automated Claims Management

Automate claims operations by combining multiple Vertafore API endpoints. Agents can get policy and then list clients in a single workflow.

Example prompt: Call GET `/policies/{policyId}` to get policy, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Vertafore API 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 apiKey tokens manually.

Example prompt: Search Jentic for 'list policies', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/policies` | List policies |
| GET | `/policies/{policyId}` | Get policy |
| GET | `/clients` | List clients |
| POST | `/claims` | Create claim |

## Key resources

- **Claims** — Operations related to Claims
- **Clients** — Operations related to Clients
- **Policies** — Operations related to Policies

## Why Jentic

- **Setup:** Wiring the Vertafore API by hand means passing its key in the Authorization header against api.vertafore.com and coding each policy, client, and claim call yourself. Through Jentic you install once, import the Vertafore API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Vertafore puts the policy id in the URL path (`/policies/{policyId}`) for reads while claims are submitted through the request body, so a rule can pin your agent to reading one policy and limit it to the operations it needs. You choose that allowed set, so writes like creating a claim are excluded unless you add them.
- **Credential handling:** Your Vertafore API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list policies' or 'look up a client', and Jentic returns the matching Vertafore operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Vertafore API use?

The Vertafore API uses an API key passed in the `Authorization` header. 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 list policies with the Vertafore API?

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

### What are the rate limits for the Vertafore API?

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 list policies through Jentic?

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

### How many endpoints does the Vertafore API have?

The Vertafore API exposes 4 endpoints covering claims, clients, policies operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Vertafore operations and credentials the agent may use. Since the policy id sits in the URL path for reads (GET `/policies/{policyId}`), you can pin the agent to reading a single policy and grant only the calls it needs, such as GET /policies and GET /clients. Write operations like POST /claims to create a claim stay excluded unless you add them to the allowed set.