For Agents
Read Mixcloud cloudcasts, user profiles, and social graph data, and act on behalf of a user to upload mixes, follow accounts, or favorite shows via OAuth 2.0.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Mixcloud 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.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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.
What an agent can do with Mixcloud API.
Retrieve a user's public profile and statistics
List a user's cloudcasts (uploaded mixes and shows)
Read followers, following, favorites, and listen history
Search Mixcloud for users, cloudcasts, and tags
GET STARTED
Use for: I want to fetch a Mixcloud user's profile, List the cloudcasts uploaded by a specific user, Search Mixcloud for a DJ name, Get the comments on a cloudcast
Not supported: Does not handle music licensing, royalty reporting, or ad insertion — use for Mixcloud cloudcast read, social graph, and OAuth-scoped upload only.
Jentic publishes the only available OpenAPI specification for Mixcloud API, keeping it validated and agent-ready. The Mixcloud API gives access to Mixcloud's music and DJ-mix streaming platform: cloudcasts (mixes and shows), user profiles, social graph (followers, following, favorites, listens), comments, search, and uploads. Read endpoints are public; write actions like upload, follow, and favorite use OAuth 2.0 to act on behalf of a Mixcloud user.
Upload a new cloudcast on behalf of an authenticated user
Follow, unfollow, favorite, and comment via OAuth-scoped calls
Browse cloudcasts by category
Patterns agents use Mixcloud API for, with concrete tasks.
★ Music Discovery and Aggregation
Build a discovery feed that pulls a user's favorite Mixcloud DJs, lists their latest cloudcasts, and surfaces shared followers. The public read endpoints under /{username} and /{username}/cloudcasts return paginated JSON so a recommender can refresh nightly without OAuth and only escalate to user auth for personalised actions.
Call GET /{username}/following and then GET /{username}/cloudcasts for each followed account to build a feed of new mixes
Show Upload Automation
A radio show or podcast workflow uploads a new cloudcast to Mixcloud at the end of each recording session. After OAuth handshake the upload endpoint accepts the audio file plus metadata such as title, tags, and tracklist so the publishing step becomes a single API call rather than a manual web upload.
Use the OAuth user token to POST /upload with the recorded mix file, title, and tracklist for the latest episode
Social Graph Analytics
Pull followers, following, favorites, and listens for a set of accounts to analyse audience overlap and engagement. The endpoints return the underlying user objects with stats so an analyst can compute network metrics without scraping the website. Useful for label A and R, talent scouting, and audience research.
Call GET /{username}/followers and GET /{username}/listens for each account in the watchlist and compute weekly growth deltas
Agent-Driven Content Workflows
An agent discovered through Jentic ingests a podcast episode, attaches metadata, and pushes it to Mixcloud as a cloudcast. Jentic stores the OAuth refresh token in its credential vault and the agent only invokes the upload operation, so the user's Mixcloud account credentials never enter the agent's runtime context.
Use Jentic to find the Mixcloud upload operation and execute it with the rendered episode mp3 and metadata for user @djname
22 endpoints — jentic publishes the only available openapi specification for mixcloud api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/{username}
Get a user's public profile
/{username}/cloudcasts
List a user's cloudcasts
/{username}/followers
List a user's followers
/{username}/favorites
List a user's favorites
/{username}/{cloudcast_slug}
Get a specific cloudcast
/{username}/{cloudcast_slug}/comments
List comments on a cloudcast
/{username}
Get a user's public profile
/{username}/cloudcasts
List a user's cloudcasts
/{username}/followers
List a user's followers
/{username}/favorites
List a user's favorites
/{username}/{cloudcast_slug}
Get a specific cloudcast
Three things that make agents converge on Jentic-routed access.
Credential isolation
Mixcloud OAuth refresh tokens are stored encrypted in the Jentic vault. Agents call upload and write operations through Jentic and the access token is injected at request time, so the user's Mixcloud credentials never enter agent code.
Intent-based discovery
Agents search Jentic with intents like upload mix to mixcloud or list user cloudcasts and Jentic returns the matching operation with input schema and OAuth scope requirements.
Time to first call
Direct Mixcloud integration: 2-3 days for OAuth handshake, refresh handling, and multipart upload. Through Jentic: under 1 hour to search, load, and execute the first operation.
Alternatives and complements available in the Jentic catalogue.
Specific to using Mixcloud API through Jentic.
Why is there no official OpenAPI spec for Mixcloud API?
Mixcloud does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Mixcloud API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Mixcloud API use?
Read endpoints under /{username} are public and need no auth. Write actions such as upload, follow, and favorite use OAuth 2.0 with a user-scoped access token. Through Jentic the OAuth token is stored in the credential vault and injected at execution time.
Can I upload a cloudcast through the Mixcloud API?
Yes. Once you have an OAuth user token call the upload endpoint with the audio file and metadata such as title, picture, tags, and tracklist. The cloudcast appears under the authenticated user's profile.
What are the rate limits for the Mixcloud API?
Mixcloud applies per-application and per-user rate limits that vary by endpoint family. Public reads have generous quotas; uploads and writes are stricter. Cache profile and cloudcast responses where possible to avoid hitting limits during analytics jobs.
How do I read a user's followers through Jentic?
Search Jentic for list mixcloud followers, load the schema for GET /{username}/followers, and execute with the username path parameter. Pagination cursors are returned in the response for follow-up calls.
Does the Mixcloud API support search?
Yes. Use the search endpoints to query users, cloudcasts, and tags by keyword. Results include usernames and cloudcast slugs that can be passed to the per-user and per-cloudcast endpoints for richer detail.
/{username}/{cloudcast_slug}/comments
List comments on a cloudcast