Install Jentic One Beta

Connect the TV API to your agent

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

Retrieve broadcast schedules with programme slots for specific channels and dates

Browse catalogues of programme assets with filtering by genre and category

Look up contributor credits including actors, directors, and presenters per programme

Query channel metadata across platforms and regional availability

Filter programme assets by feature type for targeted content discovery

GET STARTED

Start building with TV API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use TV API for, with concrete tasks.

★ Electronic Programme Guide

Build electronic programme guides (EPGs) by querying the schedule endpoint for specific channels and date ranges. The TV API returns time-slotted programme entries with titles, descriptions, and broadcast metadata. This powers TV guide applications, set-top box interfaces, and second-screen companion apps that display what is currently airing and upcoming across hundreds of channels.

Query the /schedule endpoint for BBC One channel listings for today's date and parse the returned time slots with programme titles

Programme Metadata Enrichment

Enrich content catalogues with detailed programme metadata including cast and crew credits, genre classifications, and feature attributes. The TV API links assets to contributors with role information, enabling rich programme detail pages. Media companies use this to populate content management systems with authoritative metadata sourced from Press Association's editorial team.

Retrieve asset details via GET /asset/{assetId} and then fetch contributor credits via GET /asset/{assetId}/contributor for a specific programme

Multi-Platform Channel Discovery

Discover which channels are available on specific platforms (Freeview, Sky, Virgin Media) and in which regions. The platform and region endpoints provide the data needed to show users only the channels they can actually receive, avoiding confusion from irrelevant listings. This is essential for personalised TV guide experiences that adapt to the viewer's actual platform and location.

List all platforms via GET /platform, select a platform ID, then query GET /platform/{platformId}/region to see regional channel availability

AI Agent TV Data Integration

AI agents use the TV API through Jentic to answer questions about broadcast schedules, look up programme details, and build content recommendation features. The agent searches for schedule or programme operations, loads the endpoint schema with required parameters like channel ID and date, and retrieves structured TV data for further processing or user display.

Search Jentic for 'get TV schedule for channel', load the schedule operation schema, and execute with a channel ID and date parameter to retrieve today's listings

Key Endpoints

18 endpoints — the press association tv api provides structured access to television programming metadata including schedules, channels, assets, catalogues, contributors, features, and platform-specific regional data.

METHOD

PATH

DESCRIPTION

GET

/schedule

Get broadcast schedule for channels and dates

GET

/asset/{assetId}

Get detailed programme asset information

GET

/asset/{assetId}/contributor

Get contributors for a programme

GET

/channel

List all available channels

GET

/catalogue

List programme catalogues

GET

/platform

List available TV platforms

GET

/platform/{platformId}/region

Get regions for a platform

GET

/contributor/{contributorId}

Get contributor details

GET

/schedule

Get broadcast schedule for channels and dates

GET

/asset/{assetId}

Get detailed programme asset information

GET

/asset/{assetId}/contributor

Get contributors for a programme

GET

/channel

List all available channels

GET

/catalogue

List programme catalogues

GET

/platform

List available TV platforms

GET

/platform/{platformId}/region

Get regions for a platform

GET

/contributor/{contributorId}

Get contributor details

Why Jentic?

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

Setup

Wiring the TV API by hand means setting the apikey header against tv.api.pressassociation.io/v2 and threading channel, date, asset, and platform parameters across schedule lookups yourself. Through Jentic you install once, import the TV API from the API Directory, store the API key once, and your agent calls it.

Permission scoping

The TV API takes asset, platform, and contributor ids as lookup path segments and exposes only read operations, so scoping is by operation: you limit the agent to the operations it needs, such as fetching a schedule or reading channel metadata. Contributor and platform-region lookups are included only if you add those operations.

Credential isolation

Your Press Association 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 'get the TV schedule for a channel' or 'look up programme metadata by asset', and Jentic returns the matching TV API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using TV API through Jentic.

What authentication does the TV API use?

The TV API uses API key authentication passed in the apikey header. Through Jentic, your Press Association API key is stored encrypted in your Jentic One instance and agents receive requests with the apikey header pre-configured.

Can I get TV schedules for a specific channel and date?

Yes. The GET /schedule endpoint accepts channel and date parameters to return broadcast schedule entries with programme titles, descriptions, start times, and durations for that specific channel and date combination.

What are the rate limits for the TV API?

The specification does not document explicit rate limits. Contact Press Association for your plan's throughput allowance. For high-volume schedule polling, cache responses locally and refresh on a schedule rather than querying in real time for every user request.

How do I retrieve programme cast and crew information through Jentic?

Search Jentic for 'get programme contributors', load the asset contributor operation schema, and execute with an asset ID. The response includes contributor names, roles, and identifiers. Install the SDK with pip install jentic and set JENTIC_AGENT_API_KEY to get started.

Does the TV API cover international channels or only UK?

The API primarily covers UK broadcast content through Press Association's editorial team. Channel availability varies by platform - query GET /platform to see available platforms and GET /platform/{platformId}/region to check regional coverage for each.

Can I filter programmes by genre or feature type?

Yes. The GET /feature-type endpoint lists available feature classifications, and GET /feature/{featureId} retrieves details for a specific feature. Assets within catalogues can be filtered using the catalogue and feature endpoints to narrow results by content type.

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

Yes. Because you run Jentic One yourself, your own rules decide which TV API operations and credentials the agent may use, and the TV API exposes only read operations, so you scope access by operation. You can allow just the calls the agent needs, such as GET /schedule for broadcast listings or GET /channel for channel metadata, while leaving out GET /asset/{assetId}/contributor or GET /platform/{platformId}/region unless you add them. Your Press Association API key stays with your instance and is injected at execution time, never entering the agent's prompt or logs.

Pressassociation TV API

Name: TV API
Brand: TV API
Availability: InStock

AI ReadinessFoundational (D+)49/100

See full scorecard

Official vendor OpenAPI document · agent-readyMediaVideo ProcessingapiKey18 EndpointsREST

For Agents

Query TV schedules, browse channel listings, retrieve programme metadata with contributor credits, and filter content by platform and region.

Use for: I need to get the TV schedule for a specific channel and date, Find all programmes featuring a specific contributor, List available channels on a given platform, Retrieve detailed metadata for a specific programme asset

Not supported: Does not handle video streaming, content delivery, or programme recording - use for schedule metadata and programme information lookup only.

The Press Association TV API provides structured access to television programming metadata including schedules, channels, assets, catalogues, contributors, features, and platform-specific regional data. It serves 18 endpoints for browsing and querying UK and international TV listings, retrieving programme details with contributor credits, and filtering content by platform and region. The API is designed for media applications that need authoritative broadcast schedule data.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: D+Signals: 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).

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

15%

Example Density

How richly the API is illustrated with examples.

Example Validity

Percentage of examples that conform to their schemas.

25%

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

45%

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.

33%

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

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: CSignals: 1

55%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the TV API to your agent

Capabilities

Start building with TV API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Pressassociation TV API

Jentic AI Readiness Score

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