ART19 Content API

Name: ART19 Content API
Brand: ART19 Content API
Availability: InStock

✓ Official Vendor SpecMediaAudio ProcessingapiKey22 EndpointsREST

For Agents

Read podcast catalog data from ART19 - episodes, media assets, series, networks, credits, and classifications - for downstream distribution and reporting.

Install Jentic One Beta

Connect the ART19 Content API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ART19 Content 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 ART19 Content API.

List and fetch podcast episodes from an ART19 network

Walk between episodes in a series via next and previous sibling endpoints

Retrieve media assets attached to an episode

Fetch classification taxonomies and their inclusions

GET STARTED

Start building with ART19 Content API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use ART19 Content API for, with concrete tasks.

★ Podcast Distribution Pipeline

Sync episode metadata and media assets from ART19 into a distribution pipeline that pushes to a website, RSS feed, or partner platform. The /episodes and /media_assets endpoints expose everything needed to render a podcast detail page or generate a feed entry, and JSON:API includes/relationships keep the data graph compact.

Fetch /episodes with a filter for a given series, include media_assets, and write the resulting episode list into a static site generator's data layer

Episode Navigation and Recommendations

Render previous and next episode links for a podcast player using /episodes/{id}/previous_sibling and /episodes/{id}/next_sibling. This makes it straightforward to give listeners in-series navigation without computing ordering client-side.

For episode id 'abc123', call /episodes/abc123/previous_sibling and /episodes/abc123/next_sibling and surface both links on the player UI

Editorial Catalog Reporting

Build editorial reports across an ART19 network - total episode counts, classifications coverage, credits attribution - by paginating through /episodes, /classifications, and /credits and aggregating the JSON:API responses. Useful for editorial leads tracking catalog hygiene across multiple shows.

Page through /episodes for the network, group by series, and produce a CSV of episode counts and credited contributors per series

Agent-Driven Catalog Lookup via Jentic

Let an editorial assistant agent answer questions like 'what was the latest episode of show X?' by calling the ART19 Content API through Jentic. The agent searches Jentic for 'list ART19 episodes', loads the schema, and executes - credentials never enter the agent context.

Search Jentic for 'list ART19 episodes', load the schema, and fetch the most recent episode for a given series id

Key Endpoints

22 endpoints — the art19 content api is the json:api-compliant content interface for the art19 podcast platform.

METHOD

PATH

DESCRIPTION

GET

/episodes

List episodes

GET

/episodes/{id}

Fetch a single episode

GET

/episodes/{id}/next_sibling

Fetch next episode in series

GET

/episodes/{id}/previous_sibling

Fetch previous episode in series

GET

/media_assets

List media assets

GET

/classifications

List classifications

GET

/credits

List episode credits

GET

/networks

List networks

GET

/episodes

List episodes

GET

/episodes/{id}

Fetch a single episode

GET

/episodes/{id}/next_sibling

Fetch next episode in series

GET

/episodes/{id}/previous_sibling

Fetch previous episode in series

GET

/media_assets

List media assets

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your ART19 token is stored once, encrypted, by your own Jentic One instance and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list ART19 episodes' or 'fetch the next episode in a series', and Jentic returns the matching ART19 operation with its JSON:API parameters in schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using ART19 Content API through Jentic.

What authentication does the ART19 Content API use?

ART19 uses an API key passed in the Authorization header in the form Authorization: Token token="your-token", credential="...". Requests must also send Accept: application/vnd.api+json. Through Jentic the token is stored encrypted in the vault and injected at execution, so the agent never holds the raw secret.

Can I list episodes from a specific series with the ART19 Content API?

Yes. GET /episodes accepts JSON:API filter parameters and includes; pass the filter for the series and request includes for media_assets to return the related audio in the same response.

How do I get the next or previous episode in a series?

Use GET /episodes/{id}/next_sibling or GET /episodes/{id}/previous_sibling. These endpoints return the adjacent episode in the same series ordering, so a player UI doesn't need to compute it client-side.

What are the rate limits for the ART19 Content API?

ART19 does not publish a hard public rate limit; in practice the Content API is intended for catalog reads rather than per-listener traffic. Cache responses where possible and use JSON:API page size to reduce the number of requests.

How do I list episodes through Jentic?

Run pip install jentic, then search Jentic with 'list ART19 episodes', load the schema for GET /episodes, and execute with the JSON:API filter for your series. Jentic adds the Authorization and Accept headers automatically.

Can I retrieve media asset URLs through the ART19 Content API?

Yes. GET /media_assets and GET /media_assets/{id} return media asset records that include the URL and metadata for the audio file attached to an episode.

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

Yes. Because you run Jentic One yourself, your own rules decide which ART19 operations and credentials the agent may use. Since ART19 puts the episode id in the URL path at /episodes/{id}, you can pin the agent to reads for a single episode plus its next and previous siblings and its media assets. The spec exposes only GET reads, so no write operation is available regardless of which operations you allow.