Install Jentic One Beta

Connect the Aggregators API Service to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Aggregators API Service, 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%2Fzeno.fm%2Fzeno-fm" | 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%2Fzeno.fm%2Fzeno-fm" | 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 Aggregators API Service API.

getPodcast

updatePodcast

deletePodcast

Retrieve total numer of live stats for a specific mount

Monitor Aggregators API Service operational status and events

GET STARTED

Start building with Aggregators API Service API

Explore with Jentic One

View OpenAPI Document

Automated Healthcheck Management

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

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.

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

Key Endpoints

29 endpoints — aggregators api service provides programmatic access to developer tools functionality.

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

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

Why Jentic?

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

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 isolation

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.

Intent-based discovery

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

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Aggregators API Service API through Jentic.

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.

Zeno Fm Aggregators API Service

Name: Aggregators API Service API
Brand: Aggregators API Service
Availability: InStock

Developer ToolsSource ControlapiKey, basic29 EndpointsREST

For Agents

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

Use for: I need to getpodcast, I want to updatepodcast, Search for deletepodcast, Find all getpodcastepisode

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

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

Jentic One on Github View OpenAPI Document

Connect the Aggregators API Service to your agent

Capabilities

Start building with Aggregators API Service API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Zeno Fm Aggregators API Service