canonical: https://jentic.com/apis/engagementbundle.com/engagementbundle

# Engagementbundle Distribution Partner API

The Distribution Partner API gives distribution partners programmatic access to content libraries, catalogs, collections, and records, plus live events, embed links, and Coro music content. Your agent browses a library hierarchy down to individual media, navigates Coro libraries through their category tree to the programs and media inside, and requests media playback. It also manages the partner accounts themselves, creating and updating the communities and individuals that content is distributed to.

## For AI agents

Browse content libraries, catalogs, collections, live events, and Coro music programs, request media playback, and manage distribution-partner communities and individuals.

## Scope

Does not handle video transcoding, payment processing, or digital rights enforcement. Use for distributing partner media libraries and content only.

## Capabilities

- Authenticate and open an API session through login
- Browse content libraries, catalogs, collections, and records by archetype
- Navigate Coro libraries through their category tree to programs and media
- Request media playback and fetch a random intro music program
- Retrieve embed bypass links for distributed content
- Create and update distribution-partner communities and individuals

## Use cases

### Agent-Driven Content Discovery

An AI agent connected through Jentic surfaces content by walking the Distribution Partner library hierarchy: it lists libraries, drills into catalogs and collections for an archetype, and reaches individual records. For Coro music it steps through the category tree to the programs and media inside, so the agent resolves a request like 'find a calm intro track' into a concrete playback request.

Example prompt: Browse a Coro library's categories to a program, then create a media playback request for one of its tracks

### Partner Account Management

A platform operator keeps its distribution-partner directory current by creating communities and individuals and updating their records. The API exposes community and individual resources with create, update, and lookup-by-email operations, so an agent provisions and maintains partner accounts without a manual admin console.

Example prompt: Create a community, add an individual to it, and confirm the individual resolves by email lookup

### Embeddable Content Delivery

A front end that embeds licensed content requests embed bypass links so viewers reach media without a separate sign-in. The Distribution Partner API returns embed links and live-event listings per archetype, letting an agent assemble an embeddable content block for a partner site.

Example prompt: Retrieve embed bypass links and the live events for an archetype and assemble an embeddable content block

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/login` | Log into the API |
| GET | `/libraries` | List content libraries |
| GET | `/{archetype}/catalogs` | List catalogs for an archetype |
| GET | `/{archetype}/records` | List content records for an archetype |
| GET | `/coro/Products` | List all Coro products |
| GET | `/coro/Libraries/{libraryId}` | Get a Coro library by ID |
| GET | `/distributionpartner/community` | List communities |
| POST | `/distributionpartner/community` | Create a community |

## Key resources

- **Libraries** — Content libraries with their catalogs, collections, and records
- **Coro content** — Coro products, libraries, category trees, programs, and media
- **Live events and embed** — Live-event listings and embed bypass links per archetype
- **Communities** — Create, update, and list distribution-partner communities
- **Individuals** — Create, update, and look up individuals by id or email

## 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:** 67 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 89 / 100
  - Developer Experience & Jentic Compatibility: 71 / 100
  - AI-Readiness & Agent Experience: 43 / 100
  - Agent Usability: 94 / 100
  - Security: 75 / 100
  - AI Discoverability: 73 / 100
- **View full report:** https://jentic.com/apis/engagementbundle.com/engagementbundle/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 Distribution Partner API by hand means running the login step, carrying a bearer JWT, and tracking the CoroApiAccess role for Coro endpoints. Through Jentic you install once, import the API from the API Directory, store the credential once, and your agent calls the operations.
- **Permission scoping:** The Distribution Partner API models content reads such as listing libraries and browsing Coro programs separately from partner-account writes such as creating and updating communities and individuals. A rule can allow only the content reads, leaving account writes out unless you add them.
- **Credential handling:** Your Distribution Partner credential is held by your own Jentic One instance, encrypted, and the bearer token is injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list content libraries' or 'get a Coro program's media', and Jentic returns the matching Distribution Partner operation with its input schema so the agent calls the right content endpoint.

## Related APIs

- **Contentful API** — A headless content platform for structured content, an alternative when you need a general CMS rather than partner distribution.
- **Mux API** — Video encoding and streaming that complements content distribution when media needs transcoding and delivery.
- **Vimeo API** — Video hosting and playback that pairs with partner content distribution for hosted media.

## FAQ

### What authentication does the Distribution Partner API use?

The Distribution Partner API uses a bearer JWT token in the Authorization header, per its OpenAPI spec, and Coro endpoints additionally require the CoroApiAccess role. Through Jentic the credential is held by your own Jentic One instance and the token is attached at execution time, so it never appears in your agent's prompt or logs.

### Can I browse Coro music content with the Distribution Partner API?

Yes. The API exposes Coro products and libraries, walks a library's category tree to its programs and media, and creates media playback requests. Your agent can step from a Coro product down to a specific track and request playback for it.

### What are the rate limits for the Distribution Partner API?

The OpenAPI spec does not specify rate limits. Check with the Distribution Partner API provider for the current limits before running high-volume content pulls, since none are declared in the specification.

### Is there a Distribution Partner MCP server?

You do not need an MCP server to give your agent the Distribution Partner API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent discovers the library and content operations it needs on demand without loading an extra server's tool definitions into its context.

### Can I limit what my agent is allowed to do with the Distribution Partner API?

Yes. Write a rule that allows only the content-read operations, such as listing libraries and browsing Coro programs, so the agent can surface and play content but cannot create or update communities and individuals, and every call it makes is logged.

### How do I browse distributed content through Jentic?

Install the Jentic One command line with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then add the Distribution Partner API from the Jentic directory and search by intent such as 'list content libraries'. Jentic returns the matching operation with its input schema so your agent builds a valid request. To run it on your own infrastructure, install Jentic One from its GitHub repo.