Install Jentic One Beta

Connect the Revel Digital REST API to your agent

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

Gets account details.

Updates an account.

Returns AdHawk dataset based on the provided post parameters. This is a legacy

Query and filter Revel Digital REST API records by parameters

Monitor Revel Digital REST API operational status and events

GET STARTED

Start building with Revel Digital REST API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Revel Digital REST API for, with concrete tasks.

★ Developer Tools Operations

Use the Revel Digital REST API to perform developer tools operations programmatically. The API provides 101 endpoints covering core functionality including gets account details., updates an account., gets organizations..

Call GET /account to gets account details.

Automated Account Management

Automate account operations by combining multiple Revel Digital REST API endpoints. Agents can updates an account. and then gets organizations. in a single workflow.

Call PUT /account to updates an account., then verify the result

AI Agent Integration via Jentic

AI agents discover and call Revel Digital REST API 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 apiKey, oauth2 tokens manually.

Search Jentic for 'gets account details.', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

101 endpoints — rest api for managing digital signage devices, media, playlists, schedules, templates, analytics, alerts, data tables, and user accounts in the revel digital platform.

METHOD

PATH

DESCRIPTION

GET

/account

Gets account details.

PUT

/account

Updates an account.

GET

/account/organizations

Gets organizations.

GET

/account/auditevents

Gets audit events for the account.

GET

/account/auditevents/{eventId}

Gets a single audit event by ID.

POST

/adhawk/dataset

Returns AdHawk dataset based on the provided post parameters. This is a legacy

GET

/adhawk/playlogs

Gets play logs for the account.

GET

/adhawk/pinglogs

Gets ping/heartbeat logs for the account.

GET

/account

Gets account details.

PUT

/account

Updates an account.

GET

/account/organizations

Gets organizations.

GET

/account/auditevents

Gets audit events for the account.

GET

/account/auditevents/{eventId}

Gets a single audit event by ID.

POST

/adhawk/dataset

Returns AdHawk dataset based on the provided post parameters. This is a legacy

GET

/adhawk/playlogs

Gets play logs for the account.

GET

/adhawk/pinglogs

Gets ping/heartbeat logs for the account.

Why Jentic?

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

Setup

Wiring the Revel Digital REST API by hand means handling two auth paths, an X-RevelDigital-ApiKey header and an OAuth 2.0 authorization-code flow, targeting the api.reveldigital.com host, and managing account and audit-event calls yourself. Through Jentic you install once, import Revel Digital REST API from the API Directory, store the credentials once, and your agent calls it.

Permission scoping

Revel Digital REST API puts the event id in the URL path (/account/auditevents/{eventId}), so a rule can pin your agent to one audit event: it can read that event and nothing else. You choose the operations it may call, so writes like updating the account are not included unless you add them.

Credential isolation

Your Revel Digital REST API credentials 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.

Intent-based discovery

Agents search Jentic by intent such as 'get account details' or 'read an audit event', and Jentic returns the matching Revel Digital REST API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Revel Digital REST API through Jentic.

What authentication does the Revel Digital REST API use?

The Revel Digital REST API uses apiKey, oauth2 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 gets account details. with the Revel Digital REST API?

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

What are the rate limits for the Revel Digital REST API?

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 gets account details. through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'gets account details.'. Jentic returns the matching Revel Digital REST API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Revel Digital REST API have?

The Revel Digital REST API exposes 101 endpoints covering account, adhawk, alerts operations.

Can I limit what my agent is allowed to do with the Revel Digital REST API?

Yes. Because you self-host Jentic One, your own rules decide which Revel Digital REST API operations and credentials the agent may use. You can restrict it to read-only calls such as GET /account or GET /account/auditevents while leaving out writes like PUT /account that updates the account. Since the event id sits in the URL path at /account/auditevents/{eventId}, a rule can even pin the agent to a single audit event so it reads that one record and nothing else.

Revel Digital REST API

Name: Revel Digital REST API
Brand: Revel Digital REST API
Availability: InStock

AI ReadinessAI-Aware (B)64/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey, oauth2101 EndpointsREST

For Agents

Programmatically gets account details., updates an account.. Covers 101 operations with apiKey, oauth2 authentication.

Use for: I need to gets account details., I want to updates an account., Search for gets organizations., Find all gets audit events for the account.

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

REST API for managing digital signage devices, media, playlists, schedules, templates, analytics, alerts, data tables, and user accounts in the Revel Digital platform. The API exposes 101 endpoints secured with apiKey, oauth2 authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

95%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

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

75%

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: C+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

37%

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

56%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

98%

OperationId Quality

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

61%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: ASignals: 1

84%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

52%

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

56%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Revel Digital REST API to your agent

Capabilities

Start building with Revel Digital REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Revel Digital REST API

Jentic AI Readiness Score

Revel Digital REST 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