Install Jentic One Beta

Connect the Hotelumo API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Hotelumo 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%2Fhotelumo.com%2Fhotelumo" | 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%2Fhotelumo.com%2Fhotelumo" | 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 Hotelumo API.

Find public room offers for a stay by hotel and dates

Request and create room reservations

Approve a requested reservation to confirm it

Create and update guest profiles

Manage room types and individual rooms

GET STARTED

Start building with Hotelumo API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Hotelumo API for, with concrete tasks.

★ Availability and Booking

Check a property's live room offers for a stay and request the booking in one flow, rather than integrating a channel feed by hand. The API returns public room offers for a hotel and dates, then takes a reservation request against that availability. Booking tools use this to turn an availability check into a confirmed request.

GET /api/hotels/{hotelId}/availability for the stay dates, then POST /api/hotels/{hotelId}/book-reservation to request the room.

Reservation Management

Create reservations and move requested ones to confirmed so a property's booking records stay accurate. The API creates a reservation and approves a requested reservation by id. Front-desk and operations tools use this to manage the reservation lifecycle programmatically.

POST /api/reservations to create a reservation, then POST /api/reservations/{reservationId}/approve to confirm a requested one.

Rate and Inventory Updates

Keep room rates and inventory current by setting rate plans and upserting daily rates for a date range. The API upserts daily rates and creates or updates rate plans and room types. Revenue teams use this to push pricing changes without logging into the property dashboard.

POST /api/dailyRates to upsert rates for a date range, then POST /api/ratePlans to update a rate plan.

Agent-Assisted Booking

An AI agent checks availability and books a room for a guest without a bespoke property integration. Through Jentic the agent discovers the availability, guest, and booking operations, loads their schemas, and chains them to complete a request. This lets a travel assistant book directly against a property's inventory.

Search Jentic for 'find hotel availability', call GET /api/hotels/{hotelId}/availability, create or reuse a guest with POST /api/guests, and book with POST /api/hotels/{hotelId}/book-reservation.

Key Endpoints

25 endpoints — the hotelumo api runs hotel room reservations end to end: it finds available room offers for a stay, requests and creates reservations, approves requested ones, and keeps guest profiles, room types, rate plans, and daily rates in sync.

METHOD

PATH

DESCRIPTION

GET

/api/hotels/{hotelId}/availability

Find public room offers for a stay

POST

/api/hotels/{hotelId}/book-reservation

Request a room reservation

GET

/api/reservations

List reservations

POST

/api/reservations

Create a reservation

GET

/api/guests

List guests

POST

/api/guests

Create a guest

GET

/api/rooms

List rooms

GET

/api/ratePlans

List rate plans

GET

/api/hotels/{hotelId}/availability

Find public room offers for a stay

POST

/api/hotels/{hotelId}/book-reservation

Request a room reservation

GET

/api/reservations

List reservations

POST

/api/reservations

Create a reservation

GET

/api/guests

List guests

POST

/api/guests

Create a guest

GET

/api/rooms

List rooms

GET

/api/ratePlans

List rate plans

Why Jentic?

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

Setup

Wiring Hotelumo by hand means handling either HTTP Basic or an access token, then checking availability and sequencing the guest and reservation calls yourself. Through Jentic you install once, import Hotelumo from the API Directory, store the credential once, and your agent calls those operations in order.

Permission scoping

Hotelumo puts the hotel, reservation, and guest id in the URL path, such as /api/hotels/{hotelId}/availability and /api/reservations/{reservationId}, so a rule can pin your agent to one hotel. You choose the operations it may call, so write operations like deleting a reservation or a guest are not included unless you add them.

Credential isolation

Your Hotelumo credential 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 'find hotel availability' or 'book a room', and Jentic returns the matching Hotelumo operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Hotelumo API through Jentic.

Is there a Hotelumo MCP server?

You do not need an MCP server to give your agent the Hotelumo API. Jentic connects it directly from the API Directory: import Hotelumo, store your credential once, and your agent calls the availability, reservation, and guest endpoints. Operations are discovered on demand, so no extra server's tool definitions load into the agent's context.

What authentication does the Hotelumo API use?

The Hotelumo API authenticates with HTTP Basic credentials or an access token passed in the Authorization header, per its OpenAPI spec. Through Jentic the credential is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt or logs.

Can I check availability and book a room with the Hotelumo API?

Yes. GET /api/hotels/{hotelId}/availability returns public room offers for a stay, and POST /api/hotels/{hotelId}/book-reservation requests a room against that availability. A requested reservation is then confirmed with POST /api/reservations/{reservationId}/approve.

What are the rate limits for the Hotelumo API?

The OpenAPI spec does not specify rate limits for the Hotelumo API. Check the Hotelumo documentation at https://www.hotelumo.com for the current limits that apply to your account.

How do I find hotel availability through Jentic?

Search Jentic with the query 'find hotel availability', load the schema for GET /api/hotels/{hotelId}/availability, and execute it with the hotel and stay dates to get room offers. To run it on your own infrastructure, install Jentic One from its GitHub repo.

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

Yes. Write a rule that allows only the read and booking operations for one hotel, such as GET /api/hotels/{hotelId}/availability and POST /api/hotels/{hotelId}/book-reservation, so the agent can check rooms and request bookings but cannot delete reservations or change rate plans, and every call it makes is logged. Because the hotel and reservation ids live in the URL path, you can pin it to a single property.

Hotelumo API

Name: Jentic
Address: 2 Grattan Court East, Dublin, Dublin, D02 VX86, IE

AI ReadinessFoundational (C+)58/100

See full scorecard

Official vendor OpenAPI document · agent-readyE CommerceOrder Managementbasic, apiKey25 EndpointsREST

For Agents

Check hotel room availability, request and create reservations, approve them, and manage guests, room types, rate plans, and daily rates for a property.

Use for: Find available rooms for a stay at a hotel, Create a reservation for a guest, Approve a requested reservation, Add a new guest profile

Not supported: Does not process card payments, sell flights, or publish reviews. Use for hotel availability, reservations, guests, and rate management only.

The Hotelumo API runs hotel room reservations end to end: it finds available room offers for a stay, requests and creates reservations, approves requested ones, and keeps guest profiles, room types, rate plans, and daily rates in sync. Webhook subscriptions push reservation events to your systems as they happen. Use it to let an app or an agent check availability and book rooms directly against a property's inventory and rates.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

92%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

71%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D+Signals: 4

28%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

66%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1

30%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: ASignals: 1

84%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Hotelumo API to your agent

Capabilities

Start building with Hotelumo API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Hotelumo API

Jentic AI Readiness Score

Hotelumo API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness