canonical: https://jentic.com/apis/swaggerhub.tomhatch/api-demojuyo-intracom

# Tomhatch api-demo.juyo-intra.com

API documentation for the embed endpoints. The API exposes 3 endpoints.

## For AI agents

Programmatically access api-demo.juyo-intra.com resources. Covers 3 operations.

## Scope

Does not handle payments, communications, or crm - use for ai and machine learning only.

## Capabilities

- Access api-demo.juyo-intra.com resources via REST API
- Manage ai ml data programmatically
- Integrate api-demo.juyo-intra.com into automated workflows
- Query and filter api-demo.juyo-intra.com records by parameters
- Monitor api-demo.juyo-intra.com operational status and events

## Use cases

### AI and Machine Learning Operations

The API provides 3 endpoints for ai ml operations.

Example prompt: Execute a primary operation against the api-demo.juyo-intra.com

### Data Retrieval and Monitoring

Query api-demo.juyo-intra.com 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.

Example prompt: Poll the primary api-demo.juyo-intra.com endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call api-demo.juyo-intra.com 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.

Example prompt: Search Jentic for 'api-demo.juyo-intra.com', load the operation schema, and execute with Jentic-managed credentials

## Key resources

- **private** — Secured, only Juyo can access this.
- **public** — Anyone with a valid host token can access these.

## Why Jentic

- **Setup:** Wiring the Juyo demo embed API by hand means pointing at its api-demo.juyo-intra.com host, threading the host token through each embed path, and building your own retries even though it exposes no auth scheme. Through Jentic you install once, import this API from the API Directory, store the connection details once, and your agent calls it.
- **Permission scoping:** Target the operations the agent needs, such as fetching a hotel's dashboards or requesting an embed token, rather than the whole surface. Because you pick the allowed operations, the agent only ever runs the embed calls you authorize and no others.
- **Credential handling:** Any connection details for this API are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get embed dashboards for a hotel' or 'request an embed token', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Openai** — Alternative ai ml API
- **Anthropic** — Alternative ai ml API
- **Cohere** — Complementary ai ml API
- **Huggingface** — Complementary ai ml API

## FAQ

### What authentication does the api-demo.juyo-intra.com use?

The api-demo.juyo-intra.com 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.

### What are the rate limits for the api-demo.juyo-intra.com?

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 use api-demo.juyo-intra.com through Jentic?

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

### How many endpoints does the api-demo.juyo-intra.com have?

The api-demo.juyo-intra.com exposes 3 endpoints covering private, public operations.

### Does the api-demo.juyo-intra.com support pagination?

Pagination support depends on the specific endpoint. Check the endpoint parameters for page, limit, or offset fields. Through Jentic, the operation schema exposes all available parameters so agents can paginate automatically.

### Can I limit what my agent is allowed to do with the Juyo Embed API?

Yes. Jentic One is self-hosted, so your own rules decide which operations and credentials the agent may use. You can authorize only the specific calls it needs, such as fetching a hotel's embed dashboards or requesting an embed token, rather than the whole API surface. The agent runs only the embed operations you allow and cannot invoke any others.