# SoundCloud API (/api/soundcloud)

SoundCloud profiles, a profile's tracks, and single tracks.

## When To Use This API [#when-to-use-this-api]

The SoundCloud API is for agent workflows that need public, platform-native data without writing a custom collector for every task. Use it when a prompt needs evidence from live public records, when a Skill needs repeatable enrichment, or when product code needs the same contract an agent discovered through MCP.

This section lists 3 live SoundCloud operations from the canonical OpenAPI spec. Each operation page documents the route, method, parameters, response envelope, pagination behavior when available, and the error vocabulary shared across UnifAPI.

- Discover emerging artists on SoundCloud by followers, track count and recent uploads.
- Compare tracks by plays, likes, reposts and comments to spot breakout releases.
- Read track metadata such as genre, tags, label and ISRC for catalog and rights research.

## Agent Contract Notes [#agent-contract-notes]

Agents usually discover these endpoints with the hosted UnifAPI MCP server, inspect the operation schema, then call only the records needed for the current task. Developers can call the same endpoints over HTTP with an API key, which makes the path from exploratory agent run to production integration direct.

Every successful response uses a stable envelope with a request id, data payload, optional pagination cursor, and billing metadata. Errors use the same closed vocabulary across platforms, so retry logic, user-facing explanations, and cost reporting can stay consistent even when a workflow spans multiple public-data sources.

When you are choosing an operation, start from the public identifier the user already has: a profile username, post id, channel id, subreddit name, search term, or URL-derived slug. Prefer the narrowest endpoint that answers the question, then expand only when the agent needs more evidence. This keeps record usage predictable, makes citations easier to explain, and avoids turning a focused research task into an expensive crawl.

## Operations [#operations]

### Users [#users]

- [`GET /soundcloud/users/{username}`](/api/soundcloud/users/username/get) — Get a SoundCloud profile — Returns a public SoundCloud profile: display name, bio, location, follower, following and track counts.
- [`GET /soundcloud/users/{username}/tracks/{track}`](/api/soundcloud/users/username/tracks/track/get) — Get a SoundCloud track — Returns one SoundCloud track by artist username and track slug: title, duration, genre, artwork and play, like, comment and repost counts.
- [`GET /soundcloud/users/{username}/tracks`](/api/soundcloud/users/username/tracks/get) — List a SoundCloud profile's tracks — Returns a SoundCloud profile's tracks, newest first, with play, like, comment and repost counts.