Install Jentic One Beta

Connect the Beatport API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Beatport 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fbeatport.com%2Fbeatport" | sh

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%2Fbeatport.com%2Fbeatport" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Beatport API.

Search the Beatport catalog for tracks by name, BPM, key, genre, or release date

Retrieve full track metadata including artists, remixers, label, BPM, and musical key

List releases for a label or artist with cover art and release date filters

Look up an artist profile with associated tracks and releases

Pull a curated chart's track list for a given chart ID

GET STARTED

Start building with Beatport API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Beatport API for, with concrete tasks.

★ DJ tooling and harmonic mixing apps

DJ software pulls BPM and Camelot key data from Beatport so users can build harmonically compatible sets and filter by tempo. Tracks endpoints return BPM, key, genre, and length per track, and releases endpoints supply cover art and label context. The catalog is the de facto reference for electronic music metadata, so integrators get cleaner harmonic data than from general streaming APIs.

Fetch the Beatport track 19287321 and return its BPM, key, genre, and label so a DJ tool can place it in a harmonic-mix queue

Label and artist discovery dashboards

A&R teams and label managers use the Beatport API to monitor releases, label rosters, and chart positions for their roster and competitors. The Releases and Labels endpoints support paged queries with release-date filters, and the Charts endpoint returns the canonical Beatport Top 100 lists per genre so teams can track week-over-week movement.

List the past 7 days of releases on label ID 33421 sorted by release date and report any that entered a Beatport Top 100 chart

Genre-aware music recommendation feeds

Streaming and discovery apps generate genre-specific recommendation feeds by combining Beatport's genre taxonomy with track-level filters. The /catalog/genres endpoint returns the canonical genre list, and /catalog/tracks supports filtering by genre slug, BPM range, and date so apps can surface fresh tech house, drum and bass, or melodic techno picks without manual curation.

Build a feed of new tech-house tracks released in the past 14 days between 122 and 128 BPM and return the top 25 results

AI agent integration for music research

Music journalists, label scouts, and creator-tool builders use AI agents through Jentic to pull Beatport data on demand without writing API code. The agent searches Jentic for the right operation, loads the schema, and executes with a bearer token held in your Jentic One instance, returning structured catalog data the agent can summarise or chart.

Through Jentic, find Beatport's track search operation and return the 10 most-charting tech house tracks of the past month with BPM and key

Key Endpoints

11 endpoints — jentic publishes the only available openapi specification for beatport api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/catalog/tracks

Search the track catalog with filters

GET

/catalog/tracks/{trackId}

Retrieve full metadata for a track

GET

/catalog/releases

Search releases with date and label filters

GET

/catalog/artists/{artistId}

Look up an artist profile

GET

/catalog/labels/{labelId}

Look up a label and its roster

GET

/catalog/charts

List Beatport charts

GET

/catalog/charts/{chartId}

Get a chart's full track list

GET

/catalog/genres

Browse the genre taxonomy

GET

/catalog/tracks

Search the track catalog with filters

GET

/catalog/tracks/{trackId}

Retrieve full metadata for a track

GET

/catalog/releases

Search releases with date and label filters

GET

/catalog/artists/{artistId}

Look up an artist profile

GET

/catalog/labels/{labelId}

Look up a label and its roster

GET

/catalog/charts

List Beatport charts

GET

/catalog/charts/{chartId}

Get a chart's full track list

GET

/catalog/genres

Browse the genre taxonomy

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Beatport API by hand means carrying a bearer token, learning the catalog track, release, artist, and chart endpoints, and threading catalog ids through the read calls yourself. Through Jentic you install once, import the Beatport API from the API Directory, store the token once, and your agent calls it.

Permission scoping

Beatport is read-only catalog metadata with its track, artist, and chart ids in the URL path (/catalog/tracks/{trackId}), so scope the agent to the operations it needs, such as searching tracks or fetching a chart. You choose that operation set, and there are no write operations to add.

Credential isolation

Your Beatport bearer token is stored once, encrypted, by your own Jentic One instance and injected as the Authorization header at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'find tech house tracks released this week' or 'get a Beatport chart', and Jentic returns the matching catalog operation with its input schema so the agent calls /catalog/tracks or /catalog/charts/{chartId} without browsing the reference docs.

FAQs

Specific to using Beatport API through Jentic.

Why is there no official OpenAPI spec for Beatport API?

Beatport does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Beatport API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Beatport API use?

Beatport uses HTTP bearer authentication. You obtain a bearer token from Beatport's developer programme and pass it as Authorization: Bearer <token> on every catalog request. Jentic stores the token in its vault and injects the header at execution time so it never enters agent context.

Can I get BPM and musical key for a track via the Beatport API?

Yes. GET /catalog/tracks/{trackId} returns the full track object including BPM and musical key, alongside genre, label, length, and credited artists or remixers. The /catalog/tracks search endpoint also supports BPM-range filtering for harmonic-mix workflows.

How do I retrieve a Beatport chart through Jentic?

Search Jentic for get a Beatport chart track list to find GET /catalog/charts/{chartId}. Load the schema and execute with the chart ID returned by GET /catalog/charts. The response contains the ordered track list and chart metadata.

Does the Beatport API support pagination and date filters on releases?

Yes. GET /catalog/releases accepts page, per_page, and release-date range query parameters, plus filters by label and artist. Use these together to paginate through a label's recent releases or a date-bound new-music feed.

What are the rate limits for the Beatport API?

Beatport does not publish rate limits in the spec; they are governed by your developer agreement. If you receive HTTP 429 responses, back off and retry with exponential delay, and contact Beatport's developer programme to confirm headroom for production use.

Is the Beatport API only for read operations on the catalog?

This spec exposes read-only catalog endpoints across tracks, releases, artists, labels, charts, and genres. There are no write or commerce endpoints in this surface; purchase, library, and account features are not available through this API.

Can I limit what my agent is allowed to do with the Beatport API?

Yes. Because you run Jentic One yourself, your own rules decide which Beatport operations and credentials the agent may use. Since this API is read-only catalog metadata, you can scope the agent to just the operations it needs, such as searching tracks with GET /catalog/tracks or fetching a chart with GET /catalog/charts/{chartId}, and leave the rest unavailable. There are no write operations to grant, so the agent can only read the track, release, artist, label, and chart data you allow.

Beatport API

Name: Beatport API
Brand: Beatport API
Availability: InStock

Agent-ready OpenAPI document · curated by JenticMediaAudio Processingbearer11 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

Search and retrieve dance and electronic music catalog data from Beatport including tracks, releases, artists, labels, and DJ charts across 11 endpoints.

Use for: Search for tech house tracks released in the last 30 days, Find all releases on the Anjunadeep label sorted by release date, Get the BPM and musical key for a specific Beatport track, Look up an artist by ID and list their recent releases

Not supported: Does not handle music streaming, purchase or download flows, user accounts, or playlist management - use for read-only catalog metadata about tracks, releases, artists, labels, charts, and genres only.

Jentic publishes the only available OpenAPI specification for Beatport API, keeping it validated and agent-ready. Beatport is the leading dance and electronic music store for DJs, with a catalog API that exposes tracks, releases, artists, labels, charts, and genres. The API surfaces 11 read-only catalog endpoints under /catalog, letting integrators search, filter, and retrieve metadata such as BPM, key, genre, and release dates for music discovery, charting, and DJ tooling. Authentication uses an OAuth bearer token in the Authorization header.

Jentic One on Github View OpenAPI Document