Install Jentic One Beta

Connect the Bookaway supply api to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Bookaway supply 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.bookaway%2Fbookaway-supply-api" | sh

Step 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.bookaway%2Fbookaway-supply-api" | 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 Bookaway supply api.

Get all routes

Manage identity auth data programmatically

Integrate Bookaway supply API into automated workflows

Query and filter Bookaway supply API records by parameters

Monitor Bookaway supply API operational status and events

GET STARTED

Start building with Bookaway supply api

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Bookaway supply api for, with concrete tasks.

★ Identity and Authentication Operations

Use the Bookaway supply API to perform identity auth operations programmatically. The API provides 13 endpoints covering core functionality including get all routes, get all routes, get all trips for specific date.

Call GET /routes to get all routes

Automated partners Management

Automate partners operations by combining multiple Bookaway supply API endpoints. Agents can get all routes and then get all trips for specific date in a single workflow.

Call GET /routes.json to get all routes, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Bookaway supply 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 bearer tokens manually.

Search Jentic for 'get all routes', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

13 endpoints — bookaway supply api - every request should have a bearer authorization header as "bearer xxxxxxxxxxxxxx".

METHOD

PATH

DESCRIPTION

GET

/routes

Get all routes

GET

/routes.json

Get all routes

POST

/trips

get all trips for specific date

GET

/trips

get all trips for specific date

GET

/stations

get all stations

GET

/stations.json

get all stations

GET

/stations/{stationId}

get specific station

GET

/cities

get all cities

GET

/routes

Get all routes

GET

/routes.json

Get all routes

POST

/trips

get all trips for specific date

GET

/trips

get all trips for specific date

GET

/stations

get all stations

GET

/stations.json

get all stations

GET

/stations/{stationId}

get specific station

GET

/cities

get all cities

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Bookaway supply API by hand means learning its bearer-token auth, targeting the Bookaway supply host, and handling the routes, trips, and stations calls with retries yourself. Through Jentic you install once, import the Bookaway supply API from the API Directory, store the token once, and your agent calls it.

Permission scoping

The API puts the station id in the URL path (/stations/{stationId}), so a rule can pin your agent to reading one station. You choose the operations it may call, so creating trips with POST /trips is not included unless you add it.

Credential isolation

Your Bookaway bearer token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list transfer routes' or 'look up a station', and Jentic returns the matching Bookaway supply operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Bookaway supply api through Jentic.

What authentication does the Bookaway supply API use?

The Bookaway supply API uses a Bearer token in the Authorization header. 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 get all routes with the Bookaway supply API?

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

What are the rate limits for the Bookaway supply 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 get all routes through Jentic?

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

How many endpoints does the Bookaway supply API have?

The Bookaway supply API exposes 13 endpoints covering partners operations.

Can I limit what my agent is allowed to do with the Bookaway Supply API?

Yes. Because you run Jentic One yourself, your own rules decide which Bookaway Supply operations and credentials the agent can use. You can restrict it to read-only calls like GET /routes, GET /trips, and GET /stations, and because the station id lives in the URL path (/stations/{stationId}) a rule can pin the agent to reading a single station. Write operations such as POST /trips are excluded unless you explicitly grant them.

Bookaway supply api

Name: Bookaway supply api
Brand: Bookaway supply API
Availability: InStock

Browse all Swaggerhub Bookaway APIs

Community OpenAPI document · agent-readyIdentity AuthAuthorizationbearer13 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically get all routes, get all routes. Covers 13 operations with bearer authentication.

Use for: I need to all routes, I want to all routes, Search for all trips for specific date, Find all all trips for specific date

Not supported: Does not handle payments, communications, or crm - use for identity and authentication only.

Bookaway supply API - every request should have a bearer authorization header as "bearer xxxxxxxxxxxxxx". The API exposes 13 endpoints secured with bearer authentication.

Jentic One on Github View OpenAPI Document

Connect the Bookaway supply api to your agent

Capabilities

Start building with Bookaway supply api

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Bookaway supply api