canonical: https://jentic.com/apis/webostv.lge.com/webostv-lge

# Webostv Lge webOS TV API

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

## For AI agents

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

## Scope

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

## Capabilities

- 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

### Developer Tools Operations

Use the webOS TV API to perform developer tools operations programmatically. The API provides 3 endpoints covering core functionality including list apps, play media, get drm license.

Example prompt: Call GET /apps to list apps

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

Example prompt: 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.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/apps` | List apps |
| POST | `/media/play` | Play media |
| POST | `/drm/license` | Get DRM license |

## Key resources

- **Apps** — Operations related to Apps
- **DRM** — Operations related to DRM
- **Media** — Operations related to Media

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 65 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 84 / 100
  - Developer Experience & Jentic Compatibility: 63 / 100
  - AI-Readiness & Agent Experience: 48 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/webostv.lge.com/webostv-lge/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

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