canonical: https://jentic.com/apis/swaggerhub.apex-artem2/apexbox-api

# Apex Artem2 Apex_Box API

swaggerhub.apex-artem2/apex-box version 1.0.1. The API exposes 31 endpoints secured with basic authentication.

## For AI agents

Programmatically создание договора страхования, расчет страховой премии. Covers 31 operations with basic authentication.

## Scope

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

## Capabilities

- Создание договора страхования
- Расчет страховой премии
- Integrate Apex_Box API into automated workflows
- Query and filter Apex_Box API records by parameters
- Monitor Apex_Box API operational status and events

## Use cases

### Developer Tools Operations

Use the Apex_Box API to perform developer tools operations programmatically. The API provides 31 endpoints covering core functionality including создание договора страхования, расчет страховой премии, создание страхового полиса.

Example prompt: Call POST /osago to создание договора страхования

### Automated Accident Management

Automate accident operations by combining multiple Apex_Box API endpoints. Agents can расчет страховой премии and then создание страхового полиса in a single workflow.

Example prompt: Call POST /osago_calculation to расчет страховой премии, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Apex_Box 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 'создание договора страхования', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/osago` | Создание договора страхования |
| POST | `/osago_calculation` | Расчет страховой премии |
| POST | `/doc_loss` | Создание страхового полиса |
| POST | `/accident` | Создание страхового полиса |
| GET | `/accident_calc` | Расчет страховой премии |
| POST | `/doc_loss_calc` | Создание страхового полиса |
| POST | `/kasko_gaz` | Создание страхового полиса |
| GET | `/kaskogaz_calc` | Расчет страховой премии |

## Key resources

- **Accident** — Operations for accident
- **Accident_Calc** — Operations for accident_calc
- **Area_Types** — Operations for area_types
- **Athlete** — Operations for athlete
- **Athlete_Calc** — Operations for athlete_calc

## Why Jentic

- **Setup:** Wiring the Apex_Box API by hand means setting up its HTTP basic auth, choosing between the online.aic.uz and rest.aic.uz hosts, and formatting each insurance contract and calculation POST yourself. Through Jentic you install once, import the Apex_Box 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 an OSAGO quote, and leave others out. You choose the operations it may call, so ones like creating an accident record stay unavailable unless you add them.
- **Credential handling:** Your Apex_Box 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 an OSAGO insurance quote' or 'create an insurance contract', 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_Box API use?

The Apex_Box 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 создание договора страхования with the Apex_Box API?

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

### What are the rate limits for the Apex_Box 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 создание договора страхования through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'создание договора страхования'. Jentic returns the matching Apex_Box API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

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

The Apex_Box API exposes 31 endpoints covering accident, accident_calc, area_types operations.

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

Yes. Because this API carries its targets in the request body rather than the URL path, you scope access by operation in your own self-hosted Jentic One instance, where your rules decide which operations and credentials the agent may use. You can allow only the calls it needs, such as calculating an OSAGO insurance quote, while leaving out operations you have not enabled, so creating an insurance contract or an accident record stays unavailable unless you add it. The operator, not the agent, controls which endpoints are callable.