Install Jentic One Beta

Connect the Opago API Documentation to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Opago API Documentation, 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%2Fdrive.api.cityrelaysolutions.com%2Fdrive-api-cityrelaysolutions" | 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%2Fdrive.api.cityrelaysolutions.com%2Fdrive-api-cityrelaysolutions" | 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 Opago API Documentation API.

Create and update guest bookings against specific flats, including check-in and check-out information

Check whether new booking dates overlap an existing reservation for a flat

Schedule housekeeping and maintenance services for a flat and assign tasks to employees

Log and update maintenance issues against a property using typed issue categories

GET STARTED

Start building with Opago API Documentation API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Opago API Documentation API for, with concrete tasks.

★ AI Agent Booking Operations

Let an AI agent manage short-term rental bookings end to end: it creates a booking against a flat, checks that the dates do not overlap an existing reservation, and updates check-in and check-out information as guests arrive and leave. Through Jentic the agent discovers the Opago operation it needs by intent and calls it with the right flat and booking identifiers, so reservation handling runs without a developer wiring each endpoint by hand.

Create a booking for flat 1024 with check-in 2026-11-01 and check-out 2026-11-05, confirm it does not overlap an existing booking, then set the check-in information

Housekeeping and Service Scheduling

Property operations teams schedule cleaning and maintenance services for each flat and assign them to staff. The Opago API creates a service for a flat, assigns a task to an employee at the schedule level, and updates scheduled tasks or overtime requests as the day changes. Services attach to a flat and a service type drawn from the service-type and extra-service-type reference endpoints.

Create a cleaning service for flat 1024 due 2026-11-05, then assign the task to an available employee at the schedule level

Maintenance Issue Tracking

When something breaks in a unit, the API logs a typed issue against the property and tracks it to resolution. Agents retrieve the list of issue types, create an issue with the relevant type, fetch an issue by ID, and update its details as the repair progresses. This keeps maintenance records attached to the specific flat rather than in a separate ticketing tool.

Retrieve the issue-types, create an issue for flat 1024 using the matching type, then update the issue with repair notes and status

Flat and Reference Data Lookup

Before booking or servicing a unit, agents resolve the right property and location. The API lists flats by host or external ID, returns available promoted flats for rent, and exposes reference data for cities, buildings, neighborhoods, areas, and hosts. Flat notes capture unit-specific context, with typed note categories and editable comments.

Retrieve flats for host 55, pick an available promoted flat, and read its flat-notes before creating a booking

Key Endpoints

50 endpoints — the opago api manages short-term rental operations for city relay's property portfolio, handling guest bookings, flat records, housekeeping and maintenance services, and property issues.

METHOD

PATH

DESCRIPTION

POST

/createBooking

Create a new booking

PATCH

/updateBooking

Update an existing booking

DELETE

/cancelBooking

Cancel a booking

POST

/checkIfBookingOverlaps

Check if booking dates overlap existing bookings

POST

/createService

Create a new service

POST

/createIssue

Create a new issue

GET

/getUpcomingBookings

Retrieve upcoming bookings

POST

/createFlat

Create a new flat

POST

/createBooking

Create a new booking

PATCH

/updateBooking

Update an existing booking

DELETE

/cancelBooking

Cancel a booking

POST

/checkIfBookingOverlaps

Check if booking dates overlap existing bookings

POST

/createService

Create a new service

POST

/createIssue

Create a new issue

GET

/getUpcomingBookings

Retrieve upcoming bookings

POST

/createFlat

Create a new flat

Why Jentic?

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

Setup

Wiring Opago by hand means handling its bearer-token login and refresh flow, choosing the production or sandbox host, and threading access tokens through every call. Through Jentic you install once, import Opago from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Opago carries flat and booking ids in the request body and query, not the URL path, so rules bound which operations your agent may call rather than which flat it touches. You choose the operations it needs, such as reading bookings and creating services, so destructive ones like cancelling a booking or deleting a flat-note are not included unless you add them.

Credential isolation

Your Opago access 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 'create a booking' or 'schedule a cleaning service', and Jentic returns the matching Opago operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Opago API Documentation API through Jentic.

What authentication does the Opago API use?

The Opago API authenticates with a bearer access token per its OpenAPI spec. You retrieve an access_token and refresh_token from the login endpoint, send the access token as `Authorization: Bearer {access_token}` on every other call, and use the refresh endpoint to get a new token when it expires. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's context.

Can I check booking availability with the Opago API?

Yes. The check-overlap operation tells you whether a flat's requested dates overlap an existing reservation, and the booking query operations return upcoming bookings and bookings within check-in or check-out date ranges. Agents use these to confirm a unit is free before creating a booking.

What are the rate limits for the Opago API?

The OpenAPI spec does not specify rate limits. Contact City Relay API support at antanas@cityrelay.com for current limits before running high-volume booking or service operations.

Is there an Opago MCP server?

You don't need an MCP server to give your agent the Opago API. Jentic connects it directly from the API Directory: import it, store your access token once, and your agent calls operations like creating a booking or scheduling a service. Operations are discovered on demand, so no extra server's tool definitions sit in your agent's context.

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

Yes. Write a rule that allows only the operations the agent needs, such as reading bookings and creating services, so it can check availability and schedule work but cannot cancel bookings or delete flat-notes. Opago passes flat and booking ids in the request body, so rules bound which operations run rather than which flat, and every call the agent makes is logged.

How do I create a booking with the Opago API through Jentic?

Search Jentic for 'create a short-term rental booking' to find the create-booking operation, then call it with the flat id and check-in and check-out dates after confirming the dates do not overlap an existing reservation. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Drive Api Cityrelaysolutions Opago API Documentation

AI ReadinessAI-Aware (B)63/100

See full scorecard

Community OpenAPI document · agent-readyE CommerceOrder Managementbearer50 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Create and update guest bookings, schedule housekeeping and maintenance services, and log property issues for short-term rental flats. Covers 50 operations across bookings, flats, services, and issues.

Use for: Create a booking for a flat with specific check-in and check-out dates, Check whether a booking overlaps with existing reservations, Retrieve all upcoming bookings for a host, Schedule a housekeeping service for a flat

Not supported: Does not handle payment processing, guest messaging, or channel distribution to listing sites. Use for short-term rental booking, service, and property operations only.

The Opago API manages short-term rental operations for City Relay's property portfolio, handling guest bookings, flat records, housekeeping and maintenance services, and property issues. Agents can create and update bookings against individual flats, check whether dates overlap an existing reservation, schedule services and assign tasks to employees, and track issues by type. Reference-data endpoints return available cities, buildings, neighborhoods, hosts, and service types so bookings and services attach to the right location. Authentication uses a bearer access token retrieved from a login endpoint, with a separate refresh flow for expired tokens.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

93%

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

31%

Example Density

How richly the API is illustrated with examples.

91%

Example Validity

Percentage of examples that conform to their schemas.

25%

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: DSignals: 4

40%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

96%

OperationId Quality

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

50%

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: B-Signals: 1

60%

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: A-Signals: 1

73%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Opago API Documentation to your agent

Capabilities

Start building with Opago API Documentation API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Drive Api Cityrelaysolutions Opago API Documentation

Jentic AI Readiness Score

Opago API Documentation

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