API Trip Plan

Name: API Trip Plan API
Brand: API Trip Plan
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controlnone5 EndpointsREST

For Agents

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

Use for: I need to создать путешествие, I want to добавить файл с билетами и ваучерами, Search for добавить достопримечательности для посещения, Find all добавить расходы для путешествия

Connect the API Trip Plan to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API Trip Plan, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# 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 instance

Jentic 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.

Capabilities

What an agent can do with API Trip Plan API.

Создать путешествие

Добавить файл с билетами и ваучерами

Получить информацию по итоговой стоимости

Query and filter API Trip Plan records by parameters

GET STARTED

Start building with API Trip Plan API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use API Trip Plan API for, with concrete tasks.

★ Developer Tools Operations

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

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.

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.

Search Jentic for 'создать путешествие', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

5 endpoints — документация на openapi trip plan.

METHOD

PATH

DESCRIPTION

POST

/client_base

Создать путешествие

POST

/client_base2

Добавить файл с билетами и ваучерами

POST

/client_base3

Добавить достопримечательности для посещения

POST

/client_base4

Добавить расходы для путешествия

GET

/client_base4

Получить информацию по итоговой стоимости

POST

/client_base

Создать путешествие

POST

/client_base2

Добавить файл с билетами и ваучерами

POST

/client_base3

Добавить достопримечательности для посещения

POST

/client_base4

Добавить расходы для путешествия

GET

/client_base4

Получить информацию по итоговой стоимости

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

API Trip Plan none 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 API Trip Plan operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct API Trip Plan integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using API Trip Plan API through Jentic.

What authentication does the API Trip Plan use?

The API Trip Plan uses no authentication. 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 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 at https://app.jentic.com/sign-up, 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.