ART19 Content API
49
AI ReadinessFoundational (D+)49/100
Official vendor OpenAPI document · agent-readyMediaAudio 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fart19.com%2Fart19" | sh2
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%2Fart19.com%2Fart19" | 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
Jentic AI Readiness Score
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.
A
ART19 Content API Documentation
- Foundational (D+)49/100
65
Foundational Compliance67
Developer Experience & Jentic Compatibility26
AI-Readiness & Agent Experience94
Agent Usability50
Security65
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
65
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: BSignals: 4
85%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
75%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
67
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: BSignals: 4
23%
Example Density
How richly the API is illustrated with examples.
94%
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.
26
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
56%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
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.
50
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).
65
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: BSignals: 1
65%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring ART19 by hand means handling its API-key auth and the JSON:API Accept header on every request to its podcast catalog. Through Jentic you install once, import the ART19 Content API from the API Directory, store the token once, and your agent calls it while Jentic adds the content-negotiation header.
Permission scoping
ART19 puts the episode id in the URL path (/episodes/{id}), so a rule can pin your agent to reads for one episode and its siblings and media assets. The spec exposes only GET reads, so no write operation is available regardless of the operations you allow.
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.
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.
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.
GET STARTED