Engagementbundle Distribution Partner API
67
AI ReadinessAI-Aware (B)67/100
Community OpenAPI document · agent-readyMediaContent Deliverybearer31 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Browse content libraries, catalogs, collections, live events, and Coro music programs, request media playback, and manage distribution-partner communities and individuals.
Use for: List the content libraries available to my distribution partner, Browse the catalogs and collections for a given archetype, Get the programs inside a Coro music library, Create a media playback request for a Coro program
Not supported: Does not handle video transcoding, payment processing, or digital rights enforcement. Use for distributing partner media libraries and content only.
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.
Install Jentic One Beta
Connect the Distribution Partner API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Distribution Partner API, 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.
1
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%2Fengagementbundle.com%2Fengagementbundle" | sh2
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%2Fengagementbundle.com%2Fengagementbundle" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Distribution Partner API.
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
Patterns agents use Distribution Partner API for, with concrete tasks.
★ 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.
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.
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.
Retrieve embed bypass links and the live events for an archetype and assemble an embeddable content block
Key Endpoints
31 endpoints — 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.
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
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
Jentic AI Readiness Score
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.
D
Distribution Partner API
- AI-Aware (B)67/100
89
Foundational Compliance71
Developer Experience & Jentic Compatibility43
AI-Readiness & Agent Experience94
Agent Usability75
Security73
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
89
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
97%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
60%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
71
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: A-Signals: 4
17%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
66%
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.
43
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: DSignals: 4
21%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
53%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
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.
75
Security
Trust, risk posture, and security compliance.
Grade: A-Signals: 1
75%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
73
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
73%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Distribution Partner API through Jentic.
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.
GET STARTED