Install Jentic One Beta

Connect the Rephonic Podcast API to your agent

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

Search for podcasts

Autocomplete search

Get podcast details

Query and filter Rephonic Podcast API records by parameters

Monitor Rephonic Podcast API operational status and events

GET STARTED

Start building with Rephonic Podcast API

Explore with Jentic One

View OpenAPI Document

Automated Search Management

Automate search operations by combining multiple Rephonic Podcast API endpoints. Agents can search for episodes and then autocomplete search in a single workflow.

Call GET /api/search/episodes/ to search for episodes, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Rephonic Podcast 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.

Search Jentic for 'search for podcasts', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

25 endpoints — rephonic's podcast api provides comprehensive podcast data including search, demographics, social metrics, episode transcripts, charts, and audience analytics.

METHOD

PATH

DESCRIPTION

GET

/api/search/podcasts/

Search for podcasts

GET

/api/search/episodes/

Search for episodes

GET

/api/search/autocomplete/

Autocomplete search

GET

/api/podcasts/{id}/

Get podcast details

GET

/api/podcasts/{id}/people/

Get podcast people

GET

/api/podcasts/{id}/demographics/

Get podcast listener demographics

GET

/api/podcasts/{id}/promotions/

Get podcast promotions

GET

/api/episodes/

List episodes

GET

/api/search/podcasts/

Search for podcasts

GET

/api/search/episodes/

Search for episodes

GET

/api/search/autocomplete/

Autocomplete search

GET

/api/podcasts/{id}/

Get podcast details

GET

/api/podcasts/{id}/people/

Get podcast people

GET

/api/podcasts/{id}/demographics/

Get podcast listener demographics

GET

/api/podcasts/{id}/promotions/

Get podcast promotions

GET

/api/episodes/

List episodes

Why Jentic?

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

Setup

Wiring Rephonic by hand means setting its X-Rephonic-API-key header on every request, tracking podcast and episode ids across search and detail calls, and handling paging yourself. Through Jentic you install once, import the Rephonic Podcast API from the API Directory, store the key once, and your agent calls it.

Permission scoping

Rephonic puts the podcast id in the URL path (/api/podcasts/{id}/...), so a rule can pin your agent to one podcast: it can read that podcast's people, demographics, and promotions and nothing else. You choose the operations it may call, so if you only grant search and read the agent never touches anything beyond lookups.

Credential isolation

Your Rephonic 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 'search for podcasts' or 'get a podcast's demographics', and Jentic returns the matching Rephonic operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Rephonic Podcast API through Jentic.

What authentication does the Rephonic Podcast API use?

The Rephonic Podcast API uses an API key passed in the `X-Rephonic-Api-Key` 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 search for podcasts with the Rephonic Podcast API?

Yes. Use the GET /api/search/podcasts/ endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Rephonic Podcast 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 search for podcasts through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'search for podcasts'. Jentic returns the matching Rephonic Podcast API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Rephonic Podcast API have?

The Rephonic Podcast API exposes 25 endpoints covering search, podcasts, episodes operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which Rephonic operations and credentials your agent may use. Because Rephonic puts the podcast id in the URL path (/api/podcasts/{id}/...), a rule can pin the agent to a single podcast so it reads only that podcast's people, demographics, and promotions and nothing else. You also choose which operations it may call, so granting just search and read means the agent never goes beyond lookups.

Rephonic Podcast API

Name: Rephonic Podcast API
Brand: Rephonic Podcast API
Availability: InStock

Official vendor OpenAPI document · agent-readyAnalyticsData PipelinesapiKey25 EndpointsREST

For Agents

Programmatically search for podcasts, search for episodes. Covers 25 operations with apiKey authentication.

Use for: I need to for podcasts, I want to for episodes, Search for autocomplete search, Find all podcast details

Not supported: Does not handle payments, communications, or crm - use for analytics only.

Rephonic's Podcast API provides comprehensive podcast data including search, demographics, social metrics, episode transcripts, charts, and audience analytics. The API exposes 25 endpoints secured with apiKey authentication.

Jentic One on Github View OpenAPI Document

Connect the Rephonic Podcast API to your agent

Capabilities

Start building with Rephonic Podcast API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Rephonic Podcast API