BPM detection API

Add BPM detection to your product without owning the audio worker stack.

Beatlyze estimates tempo from uploads or public audio URLs, returns a BPM value with confidence, and keeps the workflow predictable through job IDs.

Run demo track Get API key

BPM estimate and confidence value in the completed analysis resultUpload and URL submission paths for different ingestion modelsRate-limit and quota states that product teams can handle explicitly

Submit

Upload a file or send a public URL.

Poll

Use the returned job ID.

Store

Save structured JSON in your product.

Example Beatlyze API

curl -X POST https://api.beatlyze.dev/v1/analyze/upload \
  -H "X-API-Key: bz_your_api_key" \
  -F "[email protected]"

Best fit

Use Beatlyze when the job is clear.

Use this page when you need tempo detection for catalogs, DJ tools, playlist builders, sample libraries, or audio QA systems.

Tempo 127.8 BPM

Numeric tempo estimate for sorting and matching.

Confidence 0.94

A branchable signal for automation or manual review.

Lifecycle 202 + job_id

Async processing keeps larger files out of request timeouts.

Input Upload or URL

Use files for private assets and URLs for remote catalogs.

Workflows

Where this API earns its keep.

These are product workflows where Beatlyze can replace manual tagging, brittle scripts, or an internal audio worker backlog.

Workflow

Sort tracks by tempo

Use BPM to group audio into ranges for DJ libraries, sample browsers, or catalog filters.

Workflow

Power recommendation rules

Combine BPM with key, energy, and genre hints to avoid one-dimensional matching.

Workflow

Flag ambiguous results

Use BPM confidence to route half-time, double-time, or low-signal tracks into review.

Decision points

A practical API contract for product teams.

Beatlyze is intentionally explicit about lifecycle state, uncertainty, and integration boundaries.

Tempo plus confidence

A BPM number alone is brittle. Beatlyze exposes confidence so your product can decide how much to trust the estimate.

Part of a wider metadata payload

Tempo arrives with key, loudness, duration, and semantic hints so your app can make richer decisions.

Pricing

Start free, then choose a monthly quota.

Evaluate the response shape with the demo and a free key. Paid tiers are for teams that need predictable monthly analysis volume.

Free

€0 / month

Test the result shape and run low-volume experiments.

50 analysis jobs each month
Upload and public URL analysis
Polling workflow
Anonymous URL demo available before signup

Get API key

Most practical start

Starter

€19 / month

For a first production integration with predictable usage.

2,000 analysis jobs each month
Batch URL submissions up to 10 items
Webhook delivery support
Usage and billing status endpoints

Pro

€49 / month

For production apps and recurring catalog workflows.

10,000 analysis jobs each month
Higher-volume API usage
Webhook delivery logs
Self-serve billing portal when configured

FAQ

Common questions before integration.

Short answers for developers deciding whether Beatlyze fits the product they are building.

Does Beatlyze only detect BPM?

No. BPM is one field in a broader audio metadata response that also includes key, LUFS, duration, mood, genre hints, confidence, and sections.

Can BPM be wrong?

Yes. Some music is genuinely ambiguous at half-time or double-time. Beatlyze exposes confidence so you can handle those cases honestly.

Can I run BPM detection from a public audio URL?

Yes. Use POST /v1/analyze/url with a public audio URL, then poll GET /v1/analysis/{job_id}.

Related buyer pages

Compare adjacent Beatlyze use cases.

Each page maps the same API surface to a different developer job-to-be-done.