canonical: https://jentic.com/apis/swaggerhub.assecogeorgia/billing-api

# Assecogeorgia Billing API

API for Thirdparty systems. The API exposes 7 endpoints.

## For AI agents

Programmatically returns vehicle categories, returns countries. Covers 7 operations.

## Scope

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

## Capabilities

- returns vehicle categories
- registers policy to GIA system
- checks if there is any vehicles in system which matched vin code or chassis numb
- Query and filter Billing API records by parameters
- Monitor Billing API operational status and events

## Use cases

### Payments Operations

Use the Billing API to perform payments operations programmatically. The API provides 7 endpoints covering core functionality including returns vehicle categories, returns countries, registers policy to gia system.

Example prompt: Call GET `/api/categories` to returns vehicle categories

### Automated API Management

Automate API operations by combining multiple Billing API endpoints. Agents can returns countries and then registers policy to gia system in a single workflow.

Example prompt: Call GET `/api/countries` to returns countries, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Billing 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 'returns vehicle categories', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/categories` | returns vehicle categories |
| GET | `/api/countries` | returns countries |
| POST | `/api/policies` | registers policy to GIA system |
| GET | `/api/policies` | returns policies |
| GET | `/api/vehicles` | checks if there is any vehicles in system which matched vin code or chassis numb |
| GET | `/api/vehicles/manufacturers` | returns manufacturers |
| GET | `/api/vehicles/manufacturers/{id}/models` | returns car models |

## Key resources

- **api** — Operations related to api

## Why Jentic

- **Setup:** This Billing API is published as a SwaggerHub mock server with no authentication, so wiring it by hand means pointing at the virtual host and coding your own request handling and retries. Through Jentic you install once, import the Billing API from the API Directory, and your agent calls it without any bespoke client code.
- **Permission scoping:** This API carries the vehicle manufacturer id in the URL path (`/api/vehicles/manufacturers/{id}/models`), so a rule can pin your agent to reading that manufacturer's models. You also choose which operations it may call, so you can allow the read endpoints for categories, countries, and vehicles while leaving policy creation out unless you add it.
- **Credential handling:** This API declares no authentication, so there is no secret to hand the agent. If you point it at a protected deployment, the credential is stored once, encrypted, by your own Jentic One instance and injected at execution time, never entering the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list vehicle categories' or 'create an insurance policy', and Jentic returns the matching Billing API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Stripe** — Alternative payments API
- **Adyen** — Alternative payments API
- **Square** — Complementary payments API
- **Paypal** — Complementary payments API

## FAQ

### What authentication does the Billing API use?

The Billing 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 returns vehicle categories with the Billing API?

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

### What are the rate limits for the Billing 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 returns vehicle categories through Jentic?

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

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

The Billing API exposes 7 endpoints covering API operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which of the Billing API operations the agent may call, so you can allow the read endpoints for categories, countries, and vehicles while leaving policy creation (POST `/api/policies`) out unless you choose to add it. Since the manufacturer id travels in the URL path (`/api/vehicles/manufacturers/{id}/models`), you can also pin the agent to reading a single manufacturer's models. The operator sets these boundaries, and any credentials for a protected deployment stay encrypted in your own instance and are injected only at execution time.