Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Billing 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.assecogeorgia%2Fbilling-api" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.assecogeorgia%2Fbilling-api" | 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 Billing API.
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
GET STARTED
Patterns agents use Billing API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'returns vehicle categories', load the operation schema, and execute with Jentic-managed credentials
7 endpoints — api for thirdparty systems.
METHOD
PATH
DESCRIPTION
/api/categories
returns vehicle categories
/api/countries
returns countries
/api/policies
registers policy to GIA system
/api/policies
returns policies
/api/vehicles
checks if there is any vehicles in system which matched vin code or chassis numb
/api/vehicles/manufacturers
returns manufacturers
/api/vehicles/manufacturers/{id}/models
returns car models
/api/categories
returns vehicle categories
/api/countries
returns countries
/api/policies
registers policy to GIA system
/api/policies
returns policies
/api/vehicles
checks if there is any vehicles in system which matched vin code or chassis numb
/api/vehicles/manufacturers
returns manufacturers
/api/vehicles/manufacturers/{id}/models
returns car models
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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.
Alternatives and complements available in the Jentic catalogue.
Stripe
Alternative payments API
Choose Stripe when you need a different approach to payments operations
Specific to using Billing API through Jentic.
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.
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically returns vehicle categories, returns countries. Covers 7 operations.
Use for: I need to returns vehicle categories, I want to returns countries, Search for registers policy to gia system, Find all returns policies
Not supported: Does not handle communications, crm, or developer tools - use for payments only.
API for Thirdparty systems. The API exposes 7 endpoints.