ART19 Content API
✓ 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.
Use for: I need to list episodes from an ART19 network, Fetch the media asset for a specific episode, Get the next episode in the same series, List classifications applied to my podcast catalog
Not supported: Does not host audio playback, ingest new episodes, or manage advertising — use for reading ART19 podcast catalog content only.
The ART19 Content API is the JSON:API-compliant content interface for the ART19 podcast platform. It exposes the editorial entities that make a podcast catalog: episodes, media assets, classifications, classification inclusions, credits, images, networks, and series. Twenty-two endpoints cover listing and fetching each entity, plus episode siblings (next and previous episode in a series). Requests must use the Accept: application/vnd.api+json header and an Authorization token, and responses follow the JSON:API specification.
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.
1
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 | sh2
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 instanceJentic 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
Retrieve credits, images, and network metadata
Page through large result sets using JSON:API pagination
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
GET
/classifications
List classifications
GET
/credits
List episode credits
GET
/networks
List networks
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
ART19 API tokens are stored encrypted in the Jentic vault and injected into the Authorization header at execution. The Accept: application/vnd.api+json header is added automatically, so the agent never has to remember JSON:API content negotiation rules.
Intent-based discovery
Agents search Jentic by intent (e.g., 'list ART19 episodes', 'fetch next episode in series') and Jentic returns the matching ART19 operation with its JSON:API parameters described in schema.
Time to first call
Direct ART19 integration: 1-2 days to handle JSON:API parsing, the unusual Authorization header format, and pagination. Through Jentic: under an hour — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
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.
GET STARTED