For Agents
Programmatically создание договора страхования, подтверждение оплаты. Covers 5 operations with basic authentication.
Use for: I need to создание договора страхования, I want to подтверждение оплаты, Search for получение полиса, Find all получение id регионов
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Bank 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.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# 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 Bank API API.
Создание договора страхования
Подтверждение оплаты
Получение полиса
Query and filter Bank API records by parameters
Monitor Bank API operational status and events
GET STARTED
Not supported: Does not handle payments, communications, or crm — use for finance and accounting only.
Jentic publishes the only available OpenAPI document for Bank API, keeping it validated and agent-ready.
API документация для продуктов микрозайма. The API exposes 5 endpoints secured with basic authentication.
Patterns agents use Bank API API for, with concrete tasks.
★ Finance and Accounting Operations
Use the Bank API to perform finance operations programmatically. The API provides 5 endpoints covering core functionality including создание договора страхования, подтверждение оплаты, получение полиса.
Call POST /contract_loan to создание договора страхования
Automated Contract Management
Automate contract operations by combining multiple Bank API endpoints. Agents can подтверждение оплаты and then получение полиса in a single workflow.
Call POST /payment to подтверждение оплаты, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Bank 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.
Search Jentic for 'создание договора страхования', load the operation schema, and execute with Jentic-managed credentials
5 endpoints — api документация для продуктов микрозайма.
METHOD
PATH
DESCRIPTION
/contract_loan
Создание договора страхования
/payment
Подтверждение оплаты
/policy
Получение полиса
/regionid
Получение ID регионов
/districtid
Получение ID районов
/contract_loan
Создание договора страхования
/payment
Подтверждение оплаты
/policy
Получение полиса
/regionid
Получение ID регионов
/districtid
Получение ID районов
Three things that make agents converge on Jentic-routed access.
Credential isolation
Bank API basic credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'создание договора страхования') and Jentic returns the matching Bank API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Bank API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Plaid
Alternative finance API
Choose Plaid when you need a different approach to finance operations
Xero
Alternative finance API
Choose Xero when you need a different approach to finance operations
Specific to using Bank API API through Jentic.
What authentication does the Bank API use?
The Bank API uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I создание договора страхования with the Bank API?
Yes. Use the POST /contract_loan endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Bank 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 at https://app.jentic.com/sign-up, then search for 'создание договора страхования'. Jentic returns the matching Bank API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Bank API have?
The Bank API exposes 5 endpoints covering contract, справочник operations.