canonical: https://jentic.com/apis/rephonic.com/rephonic # Rephonic Podcast API 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. ## For AI agents Programmatically search for podcasts, search for episodes. Covers 25 operations with apiKey authentication. ## Scope Does not handle payments, communications, or crm - use for analytics only. ## Capabilities - 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 ## Use cases ### Analytics Operations Use the Rephonic Podcast API to perform analytics operations programmatically. The API provides 25 endpoints covering core functionality including search for podcasts, search for episodes, autocomplete search. Example prompt: Call GET `/api/search/podcasts`/ to search for podcasts ### 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. Example prompt: 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. Example prompt: Search Jentic for 'search for podcasts', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | 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 | ## Key resources - **Search** — Search for podcasts and episodes - **Podcasts** — Podcast metadata and analytics - **Episodes** — Episode data and transcripts - **Social** — Social media and engagement data - **Charts** — Podcast chart rankings ## AI readiness 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. - **Score:** 58 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 47 / 100 - Developer Experience & Jentic Compatibility: 63 / 100 - AI-Readiness & Agent Experience: 48 / 100 - Agent Usability: 94 / 100 - Security: 50 / 100 - AI Discoverability: 74 / 100 - **View full report:** https://jentic.com/apis/rephonic.com/rephonic/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **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 handling:** 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. - **Discovery method:** 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. ## Related APIs - **Mixpanel** — Alternative analytics API - **Amplitude** — Alternative analytics API - **Segment** — Complementary analytics API - **Pendo** — Complementary analytics API ## FAQ ### 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.