canonical: https://jentic.com/apis/prss.org/prss

# Prss ContentDepot

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.

## For AI agents

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

## Scope

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

## Capabilities

- Get the service information document.
- Upload a file.
- UNDER DEVELOPMENT - Download a file.
- Delete a file.

## Use cases

### Marketing Operations

Use the ContentDepot to perform marketing operations programmatically. The API provides 39 endpoints covering core functionality including get the service information document., get the group information document., get the program information document..

Example prompt: Call GET `/radiodns/spi/3.1/SI.xml` to get the service information 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.

Example prompt: 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.

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

## Key endpoints

| 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. |

## Key resources

- **RadioDNS** — Endpoints to access the RadioDNS formatted national program information (SI and PI documents) for st
- **CD Drive** — ContentDepot Drive functionality for uploading and stating content files for use in other API operat
- **Broadcast Services** — Broadcast services can subscribe to content for multiple destinations.
- **Spot Insertions** — Spot insertions define spots to play when a cue is received.
- **Programs** — Program information including searching for existing programs or fetching a specific program. A prog

## 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:** 64 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 69 / 100
  - Developer Experience & Jentic Compatibility: 62 / 100
  - AI-Readiness & Agent Experience: 44 / 100
  - Agent Usability: 94 / 100
  - Security: 90 / 100
  - AI Discoverability: 65 / 100
- **View full report:** https://jentic.com/apis/prss.org/prss/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 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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Mailchimp** — Alternative marketing API
- **Hubspot** — Alternative marketing API

## FAQ

### 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.