canonical: https://jentic.com/apis/zeno.fm/zeno-fm

# Zeno Fm Aggregators API Service

Aggregators API Service provides programmatic access to developer tools functionality. The API exposes 29 endpoints secured with apiKey, basic authentication.

## For AI agents

Programmatically getpodcast, updatepodcast. Covers 29 operations with apiKey, basic authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- getPodcast
- updatePodcast
- deletePodcast
- Retrieve total numer of live stats for a specific mount
- Monitor Aggregators API Service operational status and events

## Use cases

### Developer Tools Operations

Use the Aggregators API Service to perform developer tools operations programmatically. The API provides 29 endpoints covering core functionality including getpodcast, updatepodcast, deletepodcast.

Example prompt: Call GET `/api/v2/podcasts/{podcastKey}` to getpodcast

### Automated Healthcheck Management

Automate healthcheck operations by combining multiple Aggregators API Service endpoints. Agents can updatepodcast and then deletepodcast in a single workflow.

Example prompt: Call PUT `/api/v2/podcasts/{podcastKey}` to updatepodcast, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Aggregators API Service 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, basic tokens manually.

Example prompt: Search Jentic for 'getpodcast', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/api/v2/podcasts/{podcastKey}` | getPodcast |
| PUT | `/api/v2/podcasts/{podcastKey}` | updatePodcast |
| DELETE | `/api/v2/podcasts/{podcastKey}` | deletePodcast |
| GET | `/api/v2/podcasts/{podcastKey}/episodes/{episodeKey}` | getPodcastEpisode |
| PUT | `/api/v2/podcasts/{podcastKey}/episodes/{episodeKey}` | updatePodcastEpisode |
| DELETE | `/api/v2/podcasts/{podcastKey}/episodes/{episodeKey}` | deletePodcast_1 |
| POST | `/stats/mounts/{mount}/auth-cache/reload` | Retrieve total numer of live stats for a specific mount |
| POST | `/stats/mounts/{mount}/auth-cache/reload/all` | Retrieve total numer of live stats for a specific mount |

## Key resources

- **Healthcheck** — Operations for healthcheck
- **Partners** — Operations for partners
- **Podcasts** — Operations for podcasts
- **Stations** — Operations for stations
- **Stats** — Operations for stats

## 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:** 45 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 73 / 100
  - Developer Experience & Jentic Compatibility: 56 / 100
  - AI-Readiness & Agent Experience: 29 / 100
  - Agent Usability: 94 / 100
  - Security: 30 / 100
  - AI Discoverability: 39 / 100
- **View full report:** https://jentic.com/apis/zeno.fm/zeno-fm/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 <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Aggregators API Service by hand means choosing between its x-zeno-api-key header and basic auth, working through podcast, episode, and stats paths on api.zeno.fm, and coding request handling yourself. Through Jentic you install once, import Aggregators API Service from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** The Aggregators API Service puts the podcast and episode keys in the URL path (`/podcasts/{podcastKey}/episodes/{episodeKey}`), so a rule can pin your agent to one podcast and its episodes. You choose the operations it may call, so deleting a podcast or episode is not included unless you add it.
- **Credential handling:** Your Zeno credential 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 'get a podcast' or 'update an episode', and Jentic returns the matching Aggregators API Service operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the Aggregators API Service use?

The Aggregators API Service uses apiKey, basic authentication. 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 getpodcast with the Aggregators API Service?

Yes. Use the GET `/api/v2/podcasts/{podcastKey}` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Aggregators API Service?

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 getpodcast through Jentic?

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

### How many endpoints does the Aggregators API Service have?

The Aggregators API Service exposes 29 endpoints covering healthcheck, partners, podcasts operations.

### Can I limit what my agent is allowed to do with the Zeno.fm API?

Yes. Because you run Jentic One yourself, your own rules decide which Zeno.fm operations and credentials the agent can use. Since the podcast and episode keys sit in the URL path (`/podcasts/{podcastKey}/episodes/{episodeKey}`), you can pin the agent to a single podcast and its episodes, and you choose which operations it may call. That means a destructive call like deletePodcast or a broad updatePodcast is off limits unless you explicitly allow it.