Install Jentic One Beta

Connect the webOS TV API to your agent

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

List apps

Play media

Get DRM license

Query and filter webOS TV API records by parameters

Monitor webOS TV API operational status and events

Use Cases

GET STARTED

Start building with webOS TV API

Explore with Jentic One

View OpenAPI Document

Automated Apps Management

Automate apps operations by combining multiple webOS TV API endpoints. Agents can play media and then get drm license in a single workflow.

Call POST /media/play to play media, then verify the result

AI Agent Integration via Jentic

AI agents discover and call webOS TV 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 tokens manually.

Search Jentic for 'list apps', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

3 endpoints — lg webos tv developer api including drm and media services.

METHOD

PATH

DESCRIPTION

GET

/apps

List apps

POST

/media/play

Play media

POST

/drm/license

Get DRM license

GET

/apps

List apps

POST

/media/play

Play media

POST

/drm/license

Get DRM license

Why Jentic?

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

Setup

Wiring the webOS TV API by hand means learning its API key header, pointing at api.webostv.lge.com, and handling responses yourself. Through Jentic you install once, import the webOS TV API from the API Directory, store the key once, and your agent calls it.

Permission scoping

This API groups its work into operations rather than putting a resource id in the URL path, so limit the agent to the operations it needs, such as listing apps. You choose the operations it may call, so state-changing ones like playing media or requesting a DRM license are not included unless you add them.

Credential isolation

Your webOS TV API key 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 'list apps' or 'play media', and Jentic returns the matching webOS TV operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using webOS TV API through Jentic.

What authentication does the webOS TV API use?

The webOS TV API uses an API key passed in the `Authorization` header. 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 list apps with the webOS TV API?

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

What are the rate limits for the webOS TV 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 list apps through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list apps'. Jentic returns the matching webOS TV API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the webOS TV API have?

The webOS TV API exposes 3 endpoints covering apps, drm, media operations.

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

Yes. Because Jentic One is self-hosted, you decide which webOS TV API operations your agent may call and which credentials it may use. This API groups its work into distinct operations rather than resource IDs in the path, so you can grant only read access such as listing apps with GET /apps and withhold state-changing ones like playing media or requesting a DRM license. State-changing operations run only when you explicitly add them to the agent's allowed set.

Webostv Lge webOS TV API

AI ReadinessAI-Aware (B)65/100

See full scorecard

Official vendor OpenAPI document · agent-readyDeveloper ToolsSource ControlapiKey3 EndpointsREST

For Agents

Programmatically list apps, play media. Covers 3 operations with apiKey authentication.

Use for: I need to apps, I want to play media, Search for drm license, List all records from webOS TV API

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

LG webOS TV developer API including DRM and media services. The API exposes 3 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

99%

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

35%

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.

50%

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

42%

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.

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

50%

Authentication Strength

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

100

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A+Signals: 1

100%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the webOS TV API to your agent

Capabilities

Use Cases

Start building with webOS TV API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Webostv Lge webOS TV API

Jentic AI Readiness Score

webOS TV 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