canonical: https://jentic.com/apis/swaggerhub.igorbach/api-trip-plan

# Igorbach API Trip Plan

Документация на OpenAPI Trip Plan. The API exposes 5 endpoints.

## For AI agents

Programmatically создать путешествие, добавить файл с билетами и ваучерами. Covers 5 operations.

## Scope

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

## Capabilities

- Создать путешествие
- Добавить файл с билетами и ваучерами
- Получить информацию по итоговой стоимости
- Query and filter API Trip Plan records by parameters
- Monitor API Trip Plan operational status and events

## Use cases

### Developer Tools Operations

Use the API Trip Plan to perform developer tools operations programmatically. The API provides 5 endpoints covering core functionality including создать путешествие, добавить файл с билетами и ваучерами, добавить достопримечательности для посещения.

Example prompt: Call POST /client_base to создать путешествие

### Automated Client_Base Management

Automate client_base operations by combining multiple API Trip Plan endpoints. Agents can добавить файл с билетами и ваучерами and then добавить достопримечательности для посещения in a single workflow.

Example prompt: Call POST /client_base2 to добавить файл с билетами и ваучерами, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call API Trip Plan 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 'создать путешествие', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/client_base` | Создать путешествие |
| POST | `/client_base2` | Добавить файл с билетами и ваучерами |
| POST | `/client_base3` | Добавить достопримечательности для посещения |
| POST | `/client_base4` | Добавить расходы для путешествия |
| GET | `/client_base4` | Получить информацию по итоговой стоимости |

## Key resources

- **Client_Base** — Operations for client_base
- **Client_Base2** — Operations for client_base2
- **Client_Base3** — Operations for client_base3
- **Client_Base4** — Operations for client_base4

## Why Jentic

- **Setup:** Wiring API Trip Plan by hand means pointing at its SwaggerHub-hosted mock server, tracking the version in the base path, and handling the client-base request shapes yourself. Through Jentic you install once, import API Trip Plan from the API Directory, and your agent calls it.
- **Permission scoping:** The client-base targets travel in the request body against paths like /client_base and /client_base4 rather than a resource named in the URL path, so scope the agent to the operations it needs, such as reading a client base. You choose the operations it may call, so the write operations are not included unless you add them.
- **Credential handling:** API Trip Plan declares no authentication, so there is no secret to pass. If the live endpoint later requires a credential, it 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 'read a client base for trip planning', and Jentic returns the matching API Trip Plan 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 API Trip Plan use?

The API Trip Plan 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 создать путешествие with the API Trip Plan?

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

### What are the rate limits for the API Trip Plan?

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 API Trip Plan operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the API Trip Plan have?

The API Trip Plan exposes 5 endpoints covering client_base, client_base2, client_base3 operations.

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

Yes. Because you run Jentic One yourself, you decide which API Trip Plan operations your agent may call, so you can grant read access to a client base through GET /client_base4 while leaving the write operations out. The client-base targets travel in the request body against paths like /client_base and /client_base4 rather than in the URL, so you scope access at the operation level: the agent can only invoke the endpoints you import for it. Any credential a live endpoint needs is stored by your own instance and injected at execution time, so it never reaches the agent's prompt or logs.