Install Jentic One Beta

Connect the ContentDepot to your agent

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

Get the service information document.

Upload a file.

UNDER DEVELOPMENT - Download a file.

Delete a file.

Use Cases

Patterns agents use ContentDepot API for, with concrete tasks.

GET STARTED

Start building with ContentDepot API

Explore with Jentic One

View OpenAPI Document

Automated RadioDNS Management

Automate radiodns operations by combining multiple ContentDepot endpoints. Agents can get the group information document. and then get the program information document. in a single workflow.

Call GET /radiodns/spi/3.1/GI.xml to get the group information document., then verify the result

AI Agent Integration via Jentic

AI agents discover and call ContentDepot 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 oauth2 tokens manually.

Search Jentic for 'get the service information document.', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

39 endpoints — contentdepot hosts a range of api’s that allow clients to manage, discover, and obtain content.

METHOD

PATH

DESCRIPTION

GET

/radiodns/spi/3.1/SI.xml

Get the service information document.

GET

/radiodns/spi/3.1/GI.xml

Get the group information document.

GET

/radiodns/spi/3.1/id/{fqdn}/{sid}/{date}_PI.xml

Get the program information document.

POST

/api/v2/cddrive/files/content

Upload a file.

GET

/api/v2/cddrive/files/{file-id}/content

UNDER DEVELOPMENT - Download a file.

GET

/api/v2/cddrive/files/{file-id}

Get file information.

DELETE

/api/v2/cddrive/files/{file-id}

Delete a file.

POST

/api/v2/cddrive/folders

Create a folder.

GET

/radiodns/spi/3.1/SI.xml

Get the service information document.

GET

/radiodns/spi/3.1/GI.xml

Get the group information document.

GET

/radiodns/spi/3.1/id/{fqdn}/{sid}/{date}_PI.xml

Get the program information document.

POST

/api/v2/cddrive/files/content

Upload a file.

GET

/api/v2/cddrive/files/{file-id}/content

UNDER DEVELOPMENT - Download a file.

GET

/api/v2/cddrive/files/{file-id}

Get file information.

DELETE

/api/v2/cddrive/files/{file-id}

Delete a file.

POST

/api/v2/cddrive/folders

Why Jentic?

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

Setup

Wiring ContentDepot by hand means running its OAuth2 flow, keeping tokens fresh, and tracking file and folder ids across the CD Drive yourself. Through Jentic you install once, import ContentDepot from the API Directory, store the credential once, and your agent calls it.

Permission scoping

ContentDepot puts the file id in the URL path (/api/v2/cddrive/files/{file-id}), so a rule can pin your agent to reading a specific file. You choose the operations it may call, so destructive ones like deleting a file are not included unless you add them.

Credential isolation

Your ContentDepot 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 'read a CD Drive file' or 'fetch the service information document', and Jentic returns the matching ContentDepot operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using ContentDepot API through Jentic.

What authentication does the ContentDepot use?

The ContentDepot uses OAuth 2.0 for authorization. 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 get the service information document. with the ContentDepot?

Yes. Use the GET /radiodns/spi/3.1/SI.xml endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the ContentDepot?

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 get the service information document. through Jentic?

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

How many endpoints does the ContentDepot have?

The ContentDepot exposes 39 endpoints covering radiodns, cd drive, broadcast services operations.

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

Yes. Jentic One runs self-hosted, so your own rules decide which ContentDepot operations and credentials the agent may use. You pick the exact endpoints it can call, so a destructive operation like DELETE /api/v2/cddrive/files/{file-id} stays out of reach unless you add it. Because ContentDepot carries the file id in the URL path, such as GET /api/v2/cddrive/files/{file-id}, a rule can pin the agent to reading one specific file rather than the whole CD Drive.

Prss ContentDepot

Name: ContentDepot API
Brand: ContentDepot
Availability: InStock

AI ReadinessAI-Aware (B)64/100

See full scorecard

MarketingContent Managementoauth239 EndpointsREST

For Agents

Programmatically get the service information document., get the group information document.. Covers 39 operations with oauth2 authentication.

Use for: I need to the service information document., I want to the group information document., Search for the program information document., Find all upload a file.

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

ContentDepot hosts a range of API’s that allow clients to manage, discover, and obtain content. The API spans many parts of the ContentDepot functionality including MetaPub (a.k.a. metadata distribution) and content management. MetaPub MetaPub collects, normalizes and distributes publicly available program, episode, and piece metadata through the public radio system. Backed by ContentDepot and its. The API exposes 39 endpoints secured with oauth2 authentication.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: B+Signals: 4

75%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

49%

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.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

71%

Description Coverage

Coverage of descriptions across API elements.

46%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

57%

Summary Coverage

Coverage of summaries across operations/tags/info.

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.

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1

90%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: BSignals: 1

65%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the ContentDepot to your agent

Capabilities

Use Cases

Start building with ContentDepot API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Prss ContentDepot

Jentic AI Readiness Score

ContentDepot

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness