Install Jentic One Beta

Connect the BE-WS to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the BE-WS, 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.bookingexpertapi%2Fbe-ws" | 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.bookingexpertapi%2Fbe-ws" | 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 BE-WS API.

getRoom

getOffer

Integrate BE-WS into automated workflows

Query and filter BE-WS records by parameters

Monitor BE-WS operational status and events

Use Cases

GET STARTED

Start building with BE-WS API

Explore with Jentic One

View OpenAPI Document

Data Retrieval and Monitoring

Query BE-WS resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Poll the primary BE-WS endpoint, compare response to last known state, and alert if changed

AI Agent Integration via Jentic

AI agents discover and call BE-WS 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 'getroom', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

2 endpoints — api to retrieve information about the booking engine configuration.

METHOD

PATH

DESCRIPTION

GET

/rooms

getRoom

GET

/offers

getOffer

GET

/rooms

getRoom

GET

/offers

getOffer

Why Jentic?

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

Setup

Wiring the BE-WS API by hand means mapping its rooms and offers endpoints, choosing among the BookingExpert booking hosts, and handling retries yourself. Through Jentic you install once, import the BE-WS API from the API Directory, and your agent calls it without you writing that plumbing.

Permission scoping

The rooms and offers reads carry their filters in the request rather than a resource id in the URL path, so scope the agent to the operations it needs, such as listing rooms with GET /rooms and offers with GET /offers. The agent runs only the operations you allow.

Credential isolation

This spec defines no authentication, so there is no credential to store. If you point it at a host that adds a key later, that key 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 available rooms' or 'get current offers', and Jentic returns the matching BE-WS operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Shopify

Alternative e commerce API

Choose Shopify when you need a different approach to e commerce operations

Alternative

Stripe

Alternative e commerce API

Choose Stripe when you need a different approach to e commerce operations

FAQs

Specific to using BE-WS API through Jentic.

What authentication does the BE-WS use?

The BE-WS 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 getroom with the BE-WS?

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

What are the rate limits for the BE-WS?

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 getroom through Jentic?

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

How many endpoints does the BE-WS have?

The BE-WS exposes 2 endpoints covering offers, rooms operations.

Can I limit what my agent is allowed to do with the BE-WS?

Yes. Jentic One is self-hosted, so your own rules decide which BE-WS operations and credentials the agent may use. You can scope it to just the reads it needs, such as listing rooms with GET /rooms or fetching offers with GET /offers, and leave everything else off. The agent runs only the operations you allow.

Bookingexpertapi BE-WS

Name: BE-WS API
Brand: BE-WS
Availability: InStock

Browse all Swaggerhub Bookingexpertapi APIs

Community OpenAPI document · agent-readyE CommerceStorefrontnone2 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Programmatically getroom, getoffer. Covers 2 operations.

Use for: I need to getroom, I want to getoffer, Get the current status of BE-WS resources, List all records from BE-WS

Not supported: Does not handle payments, communications, or crm - use for e-commerce only.

API to retrieve information about the booking engine configuration. The API exposes 2 endpoints.

Jentic One on Github View OpenAPI Document