canonical: https://jentic.com/apis/swaggerhub.apex.kobul/swaggerhub-apex-kobul

# Apex Kobul APEX INSURANCE TRAVEL API

swaggerhub.apex.kobul/apex-insurance-ap-is version 3.0.0. The API exposes 15 endpoints secured with basic authentication.

## For AI agents

Programmatically create a new insurance policy, get insurance policy. Covers 15 operations with basic authentication.

## Scope

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

## Capabilities

- Create a new insurance policy
- Get insurance policy
- Travel Insurance Cost Calculator
- Passenger Insurance Cost Calculator
- Monitor APEX INSURANCE TRAVEL API operational status and events

## Use cases

### Developer Tools Operations

Use the APEX INSURANCE TRAVEL API to perform developer tools operations programmatically. The API provides 15 endpoints covering core functionality including create a new insurance policy, get insurance policy, travel insurance cost calculator.

Example prompt: Call POST /contract to create a new insurance policy

### Automated Annulation Management

Automate annulation operations by combining multiple APEX INSURANCE TRAVEL API endpoints. Agents can get insurance policy and then travel insurance cost calculator in a single workflow.

Example prompt: Call POST /policy to get insurance policy, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call APEX INSURANCE TRAVEL 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 basic tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/contract` | Create a new insurance policy |
| POST | `/policy` | Get insurance policy |
| POST | `/calculator_travel` | Travel Insurance Cost Calculator |
| POST | `/contract_passenger` | Create a new insurance policy |
| POST | `/calculator_passenger` | Passenger Insurance Cost Calculator |
| POST | `/country` | Getting information by country |
| POST | `/program_travel` | Getting information on programs |
| GET | `/purpose` | Getting a list of travel purposes |

## Key resources

- **Annulation** — Operations for annulation
- **Calculator_Passenger** — Operations for calculator_passenger
- **Calculator_Travel** — Operations for calculator_travel
- **Contract** — Operations for contract
- **Contract_Passenger** — Operations for contract_passenger

## Why Jentic

- **Setup:** Wiring the APEX INSURANCE TRAVEL API by hand means setting up its HTTP basic auth, choosing between the online.aic.uz and rest.aic.uz hosts, and formatting each contract, policy, and calculator POST yourself. Through Jentic you install once, import the APEX INSURANCE TRAVEL API from the API Directory, store the basic credentials once, and your agent calls it.
- **Permission scoping:** The targets for this API travel in the request body, not the URL path, so scope by operation: limit the agent to the operations it needs, such as calculating a travel quote or listing purposes, and leave others out. You choose the operations it may call, so ones like creating a policy stay unavailable unless you add them.
- **Credential handling:** Your APEX INSURANCE TRAVEL 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 'calculate a travel insurance quote' or 'create a new insurance policy', and Jentic returns the matching 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 APEX INSURANCE TRAVEL API use?

The APEX INSURANCE TRAVEL API 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 a new insurance policy with the APEX INSURANCE TRAVEL API?

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

### What are the rate limits for the APEX INSURANCE TRAVEL 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 create a new insurance policy through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a new insurance policy'. Jentic returns the matching APEX INSURANCE TRAVEL API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the APEX INSURANCE TRAVEL API have?

The APEX INSURANCE TRAVEL API exposes 15 endpoints covering annulation, calculator_passenger, calculator_travel operations.

### Can I limit what my agent is allowed to do with the APEX Insurance Travel API?

Yes. Because you run Jentic One yourself, your own rules decide which of this API's operations the agent may call, and the encrypted basic credentials are injected only for the calls you permit. Since the operation targets travel in the request body rather than the URL path, you scope by operation: allow only what the agent needs, such as calculating a travel quote via POST /calculator_travel or listing purposes via GET /purpose. Write operations like creating a policy through POST /contract stay unavailable unless you explicitly grant them.