canonical: https://jentic.com/apis/swaggerhub.jaroop/swaggerhub-jaroop

# Jaroop AccuQuote AgentCloud REST API

REST API for third-party access to the AccuQuote AgentCloud platform. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. Authentication The API authenticate. The API exposes 27 endpoints.

## For AI agents

Programmatically creates a new lead, updates a lead. Covers 27 operations.

## Scope

Does not handle payments, communications, or crm - use for identity and authentication only.

## Capabilities

- Creates a new lead
- Updates a lead
- Adds email addresses to the do-not-contact list.
- Gets the number of agents available to field calls, filtered by the 
given param
- Monitor AccuQuote AgentCloud REST API operational status and events

## Use cases

### Identity and Authentication Operations

Use the AccuQuote AgentCloud REST API to perform identity auth operations programmatically. The API provides 27 endpoints covering core functionality including creates a new lead, updates a lead, adds email addresses to the do-not-contact list..

Example prompt: Call POST /leads to creates a new lead

### Automated Leads Management

Automate leads operations by combining multiple AccuQuote AgentCloud REST API endpoints. Agents can updates a lead and then adds email addresses to the do-not-contact list. in a single workflow.

Example prompt: Call PUT /leads/{leadId} to updates a lead, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call AccuQuote AgentCloud REST 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 none tokens manually.

Example prompt: Search Jentic for 'creates a new lead', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /leads | Creates a new lead |
| PUT | /leads/{leadId} | Updates a lead |
| POST | /emails/do-not-contact | Adds email addresses to the do-not-contact list. |
| GET | /agents/available | Gets the number of agents available to field calls, filtered by the given param |
| GET | /opportunities/match | Gets a list of opportunities matching a set of filter parameters |
| GET | /opportunities/{opportunityId} | Gets information about an opportunity |
| PUT | /opportunities/{opportunityId} | Updates an opportunity |
| GET | /opportunities/{opportunityId}/medicare | Retrieves Medicare and policy information for an opportunity |

## Key resources

- **Leads** — Operations related to Leads
- **Opportunities** — Operations related to Opportunities
- **Emails** — Operations related to Emails
- **Agents** — Operations related to Agents
- **Contacts** — Operations related to Contacts

## Why Jentic

- **Setup:** Wiring the AccuQuote AgentCloud REST API by hand means reading its spec, building calls across its leads, agents, and opportunities endpoints, and handling request formatting and retries yourself. Through Jentic you install once, import AccuQuote AgentCloud from the API Directory, store any required connection detail once, and your agent calls it.
- **Permission scoping:** AccuQuote puts the lead and opportunity ids in the URL path (/leads/{leadId}, /opportunities/{opportunityId}), so a rule can pin your agent to reading one opportunity. You choose the operations it may call, so write operations like updating a lead or adding an email to do-not-contact are not included unless you add them.
- **Credential handling:** Any connection detail the AccuQuote AgentCloud REST API needs 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 'create a new lead' or 'find an available agent', and Jentic returns the matching AccuQuote AgentCloud operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Auth0** — Alternative identity auth API
- **Okta** — Alternative identity auth API

## FAQ

### What authentication does the AccuQuote AgentCloud REST API use?

The AccuQuote AgentCloud REST API uses no authentication. 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 creates a new lead with the AccuQuote AgentCloud REST API?

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

### What are the rate limits for the AccuQuote AgentCloud REST 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 creates a new lead through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'creates a new lead'. Jentic returns the matching AccuQuote AgentCloud REST API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the AccuQuote AgentCloud REST API have?

The AccuQuote AgentCloud REST API exposes 27 endpoints covering leads, opportunities, emails operations.

### Can I limit what my agent is allowed to do with the AccuQuote AgentCloud REST API?

Yes. Jentic One is self-hosted by you, so your own rules decide which AccuQuote AgentCloud operations and credentials the agent may use. You pick the exact operations it can call, so read-only actions like getting an opportunity stay in scope while write operations such as updating a lead or adding an email to the do-not-contact list are excluded unless you add them. Because the API puts lead and opportunity ids in the URL path, such as /leads/{leadId} and /opportunities/{opportunityId}, you can pin the agent to a single record.