Install Jentic One Beta

Connect the DiscVision Internal REST API for Hotel to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DiscVision Internal REST API for Hotel, 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%2Fdiscvision.de%2Fdiscvision" | 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%2Fdiscvision.de%2Fdiscvision" | 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 DiscVision Internal REST API for Hotel API.

Provision and configure in-room voice endpoints: wake word, locale, timezone, max volume, do-not-disturb, and connectivity status

Manage each endpoint's Wi-Fi networks and enable or remove Alexa skills on a unit

Organise the property hierarchy of properties, room types, and rooms with per-level settings

Build meal plans with meals, options, orders, and food restrictions and export order statistics

GET STARTED

Start building with DiscVision Internal REST API for Hotel API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use DiscVision Internal REST API for Hotel API for, with concrete tasks.

★ An Agent Configuring In-Room Devices

An AI agent connected to DiscVision through Jentic can set up and adjust a room's voice endpoint without a technician: set the wake word, locale, timezone, and maximum volume, toggle do-not-disturb, connect Wi-Fi, and check connectivity status. Because each endpoint is addressed by its own id, the agent configures exactly one device at a time across a property.

Set the wake word and locale for one endpoint, connect its Wi-Fi network, and read its connectivity status to confirm it is online

Meal Planning and Ordering

DiscVision manages the dining side of a stay: define meals and meal options, build a meal plan for a room type, capture meal orders and food restrictions per room, and export the orders and option counts for the kitchen. This lets a property run room-level dining from the same platform that drives the in-room devices.

Create a meal plan for a room type, add meal options, and export the current meal orders for the kitchen

Guest Notifications and Proactive Campaigns

Properties can reach guests through their in-room devices by sending a notification to a single room or broadcasting to a room type, and by scheduling proactive campaigns. This turns the device fleet into a messaging channel for service updates and promotions without a separate system.

Send a notification to one room, then create a proactive campaign for a room type

Property and Role Administration

DiscVision organises hotels as properties containing room types and rooms, each with its own settings, and it administers who can do what: groups, invitations, roles, and per-unit admin and experience-admin rights for users. An operator can stand up a property, place its rooms, and grant staff the access they need.

Add a property, create its room types and rooms, and grant a staff user admin rights for a unit

Key Endpoints

212 endpoints — the discvision internal rest api for hotel runs an in-room voice-assistant hospitality platform built on alexa for hospitality.

METHOD

PATH

DESCRIPTION

GET

/endpoints

Get the list of voice endpoints

PUT

/endpoints/{endpointId}/wakeWord

Set the wake word of an endpoint

POST

/wifi

Set the Wi-Fi for an endpoint

POST

/skills/{skillId}/enablements

Enable an Alexa skill on a unit

GET

/rooms

Get the room list

PUT

/mealplan

Add or update a meal plan

POST

/notification

Send a notification to a room

GET

/properties

Get the property list

GET

/endpoints

Get the list of voice endpoints

PUT

/endpoints/{endpointId}/wakeWord

Set the wake word of an endpoint

POST

/wifi

Set the Wi-Fi for an endpoint

POST

/skills/{skillId}/enablements

Enable an Alexa skill on a unit

GET

/rooms

Get the room list

PUT

/mealplan

Add or update a meal plan

POST

/notification

Send a notification to a room

GET

/properties

Get the property list

Why Jentic?

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

Setup

Wiring DiscVision by hand means running its OAuth 2.0 authorization-code flow through Amazon login, managing the Alexa enterprise and Wi-Fi management scopes, and keeping tokens fresh across a large surface. Through Jentic you install once, import DiscVision from the API Directory, store the credential once, and your agent calls it.

Permission scoping

DiscVision keys most operations to a property, room, or endpoint id in the URL path (/properties/{propertyId}, /endpoints/{endpointId}, /rooms/{roomId}), so a rule can pin your agent to one property or a single endpoint and the operations you pick. It can read and configure device settings for that scope while property deletion, role grants, and user admin changes stay out of reach unless you add them.

Credential isolation

Your DiscVision OAuth 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 'configure an in-room device' or 'send a notification to a room', and Jentic returns the matching DiscVision operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using DiscVision Internal REST API for Hotel API through Jentic.

Is there a DiscVision MCP server?

You don't need an MCP server to give your agent DiscVision. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the endpoint-configuration, property, meal, and notification operations. Operations are discovered on demand, so no extra server's tool definitions sit in the agent's context.

Can I limit what my agent is allowed to do with DiscVision?

Yes. Write a rule that allows the endpoint configuration and room read operations for one property id but not property deletion, role assignment, or granting unit admin rights, so the agent can manage devices and rooms while account administration stays with you, and every call it makes is logged.

What authentication does the DiscVision API use?

Per its OpenAPI spec, the DiscVision API uses OAuth 2.0 with the authorization-code flow through Amazon login, reflecting its Alexa for Hospitality basis, and requests the Alexa enterprise management, Wi-Fi management, and user profile scopes. Through Jentic the resulting token is stored encrypted by your own Jentic One instance and injected only at call time.

Can I configure in-room voice devices with the DiscVision API?

Yes. Each endpoint is addressed by its id, and dedicated operations set its wake word, locale, timezone, maximum volume, do-not-disturb state, and distance and temperature units, connect or forget Wi-Fi networks, and report connectivity status. Skills can be enabled on or removed from a unit as well.

What are the rate limits for the DiscVision API?

The OpenAPI spec does not specify rate limits, and this spec is published through a third-party aggregator rather than by DiscVision directly. Check discvision.de for current limits and the production base URL before relying on the development server listed in the spec.

How do I set up an in-room device with the DiscVision API through Jentic?

Read the property's endpoints, then set the wake word, locale, and Wi-Fi for the target endpoint and confirm its connectivity status. In Jentic, search for 'configure an in-room voice device', store your credential once, and the agent runs the sequence. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Discvision De DiscVision Internal REST API for Hotel

AI ReadinessFoundational (D-)42/100

See full scorecard

Community OpenAPI document · agent-readyIOTDevice Managementoauth2212 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Provision and configure in-room Alexa voice endpoints, organise properties, room types, and rooms, and manage meal plans, notifications, and guest services. Administers groups, roles, and users across 212 endpoints.

Use for: List the voice endpoints in a property, Set the wake word for an in-room device, Configure the Wi-Fi network for an endpoint, Enable an Alexa skill on a room's unit

Not supported: Does not process payments, handle reservations and PMS billing, or run a booking engine. Use for managing in-room voice devices and hotel guest-experience services only.

The DiscVision Internal REST API for Hotel runs an in-room voice-assistant hospitality platform built on Alexa for Hospitality. It provisions and configures the voice endpoints in each room, covering wake word, locale, timezone, maximum volume, do-not-disturb, Wi-Fi, and enabled skills, and it organises the property hierarchy of properties, room types, and rooms with per-level settings. On top of the devices it manages guest services such as meal plans, orders, food restrictions, reminders, and proactive campaigns, and it handles communication address books, inbound calls, room notifications, questionnaires, media libraries, and group, role, and user administration.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: CSignals: 4

88%

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

25%

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

23%

Example Density

How richly the API is illustrated with examples.

99%

Example Validity

Percentage of examples that conform to their schemas.

72%

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

38%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

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

60%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: D-Signals: 1

43%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

90%

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: FSignals: 1

39%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the DiscVision Internal REST API for Hotel to your agent

Capabilities

Start building with DiscVision Internal REST API for Hotel API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Discvision De DiscVision Internal REST API for Hotel

Jentic AI Readiness Score

DiscVision Internal REST API for Hotel

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