For Agents
Manage insurance-agency cases, contacts, tasks, notes, sub-agents, carriers, and benefits in NextAgency, with OAuth 2.0 authorization-code login and full search on every major resource.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the NextAgency 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with NextAgency API.
Provision an OAuth 2.0 access token through /oauth/authorize and /oauth/token for downstream API calls
Create, update, and search cases (the platform's term for businesses) along with their associated addresses
Track tasks against a case with create, update, and search endpoints scoped under /api/v2/businesses/{business_id}/tasks
GET STARTED
Use for: I need to create a new case for an incoming insurance prospect, Search NextAgency contacts by phone number to identify a caller, List every task open against a specific business, Add a note to a case after a customer call
Not supported: Does not handle policy quoting, premium calculation, or carrier rating — use for managing the NextAgency book of business records (cases, contacts, tasks, notes, benefits, carriers, sub-agents) only.
NextAgency is an insurance-agency management platform whose v2 REST API exposes 55 endpoints for managing the data inside an agency book of business. The API covers cases (the platform's term for businesses), addresses, agency benefits, tasks, notes, contacts, sub-agents, carriers, employees, users, and VOIP recordings, with dedicated search endpoints on every major resource. Authentication is OAuth 2.0 — the /oauth/authorize and /oauth/token endpoints handle the authorization-code grant and the rest of the API uses the resulting access token as a bearer credential.
Store and search notes attached to a case for activity logging and customer-conversation recall
Maintain agency benefit records on a case to capture the products and policies the agency placed
Manage the carrier catalog, sub-agent roster, and contact directory shared across the agency
Search contacts by phone number to identify a caller before answering or returning a call
Patterns agents use NextAgency API for, with concrete tasks.
★ Caller Identification on Inbound Phone Calls
When a phone rings into the agency, hit GET /api/v2/contacts/search_by_phone_number with the caller ID to find the matching contact and the case they belong to. The agent can then surface the contact name, last note, and open tasks before the call is answered. Combine with GET /api/v2/businesses/{business_id}/notes to pull recent activity into the answering screen.
Call GET /api/v2/contacts/search_by_phone_number with phone_number=+15551234567 to identify the caller, then GET /api/v2/businesses/{business_id}/notes for the last 5 notes on their case
New-Business Case Creation
When a prospect submits a quote request, create the case in NextAgency, attach an address, and seed the initial task list. POST /api/v2/businesses creates the case (the API name for a business), POST /api/v2/businesses/{business_id}/tasks adds the follow-up tasks, and POST /api/v2/businesses/{business_id}/notes captures the intake summary. The case becomes the central record for benefits, carriers, and sub-agent assignment.
POST /api/v2/businesses with the prospect's name and primary contact, then POST /api/v2/businesses/{business_id}/tasks with a follow-up task due in 48 hours
Renewal Task and Benefit Tracking
Drive policy renewal workflows by listing tasks and benefits per case. GET /api/v2/businesses/{business_id}/tasks lists open work, PATCH on a specific task moves it through statuses, and GET /api/v2/businesses/{business_id}/agency_benefits surfaces the products in force. Search /api/v2/businesses/{business_id}/tasks/search filters tasks by due date or owner so renewal sweeps can be batched per producer.
GET /api/v2/businesses/{business_id}/tasks/search with a status filter for open tasks due this week, then PATCH each task to mark it complete after the renewal call
AI Agent Agency Operations
Through Jentic, an AI agent reads and writes NextAgency records without holding the OAuth client secret. The agent searches Jentic with the intent 'create a NextAgency case', loads the POST /api/v2/businesses schema, and executes with structured arguments. Subsequent calls to tasks, notes, and contacts endpoints reuse the same OAuth flow, with the access token handled by Jentic's MAXsystem vault.
Use Jentic search query 'create a NextAgency case' to load POST /api/v2/businesses, execute with the prospect's details, then chain task and note creation calls under the new business_id
55 endpoints — nextagency is an insurance-agency management platform whose v2 rest api exposes 55 endpoints for managing the data inside an agency book of business.
METHOD
PATH
DESCRIPTION
/oauth/token
Exchange an authorization code for an access token
/api/v2/businesses
List cases (businesses)
/api/v2/businesses
Create a case
/api/v2/businesses/search
Search cases
/api/v2/businesses/{business_id}/tasks
Create a task on a case
/api/v2/businesses/{business_id}/notes
Create a note on a case
/api/v2/contacts/search_by_phone_number
Search contacts by phone number
/api/v2/carriers/search
Search the carrier catalog
/oauth/token
Exchange an authorization code for an access token
/api/v2/businesses
List cases (businesses)
/api/v2/businesses
Create a case
/api/v2/businesses/search
Search cases
/api/v2/businesses/{business_id}/tasks
Create a task on a case
Three things that make agents converge on Jentic-routed access.
Credential isolation
The OAuth client ID, client secret, and refresh token are stored encrypted in the Jentic MAXsystem vault. Jentic exchanges them for a short-lived access token at execution time and adds it as Authorization: Bearer, so the agent never handles the OAuth secret or long-lived refresh token.
Intent-based discovery
Agents search Jentic with intents like 'create a NextAgency case' or 'search NextAgency contact by phone' and Jentic returns the matching /api/v2 endpoint with its parameter schema, so the agent populates the request without browsing NextAgency docs.
Time to first call
Direct NextAgency integration: 2-4 days to wire the OAuth authorization-code flow, refresh handling, and per-resource pagination across 55 endpoints. Through Jentic: under 1 hour to search, load, and execute any of the case, task, note, or contact operations.
Alternatives and complements available in the Jentic catalogue.
Specific to using NextAgency API through Jentic.
What authentication does the NextAgency API use?
NextAgency uses OAuth 2.0 with the authorization-code grant. /oauth/authorize starts the consent flow and POST /oauth/token exchanges the returned code for an access token, which is then sent as Authorization: Bearer on the /api/v2 endpoints. Jentic stores the OAuth client and refresh token in the MAXsystem vault and refreshes the access token automatically.
How do I create a new case in NextAgency?
POST /api/v2/businesses with a JSON body containing the business name and any required contact data. The response returns the business_id, which is then used as the path segment on every nested resource — tasks, notes, agency_benefits — under /api/v2/businesses/{business_id}.
Can I look up a NextAgency contact by their phone number?
Yes. GET /api/v2/contacts/search_by_phone_number accepts a phone_number query parameter and returns matching contacts with their associated business_id. Use this for inbound-call screen pops or outbound dialing reconciliation.
How do I search tasks across an agency's cases?
Tasks are scoped per case in the API. Use GET /api/v2/businesses/{business_id}/tasks/search with status, due_date, or owner filters to narrow down within a specific case. To sweep across cases, iterate the businesses list from GET /api/v2/businesses and call the per-case task search for each one.
What resources are available beyond cases, tasks, and contacts?
The API also exposes addresses, agency_benefits, sub_agents, carriers, employees, users, and VOIP recordings, each with list, get, update, and (where applicable) search endpoints under /api/v2. This covers the operational data an insurance agency needs alongside the core case record.
How do I integrate NextAgency through Jentic?
Run pip install jentic, then use the Jentic search query 'create a NextAgency case' to load POST /api/v2/businesses. Jentic handles the OAuth token exchange and refresh from the MAXsystem vault, so the agent only deals with the business arguments. Sign up at https://app.jentic.com/sign-up.
/api/v2/businesses/{business_id}/notes
Create a note on a case
/api/v2/contacts/search_by_phone_number
Search contacts by phone number
/api/v2/carriers/search
Search the carrier catalog