Tempo metadata

BPM Detection API for Music Apps and Agents

Use Pulse when a product, assistant, or workflow needs tempo context before organizing, recommending, or preparing audio.

Who this is for

What Pulse returns

  • BPM estimate
  • tempo confidence
  • beat count when available
  • job status and selected-tool cost details

Example workflow

Estimate the cost for a public or shared audio URL, confirm the user has rights or lawful access, run BPM analysis, then store or present the tempo result alongside confidence and a half-time/double-time verification note.

From a sound to your own song

Start a DAW project at a kit’s documented tempo, then estimate BPM analysis for the track you build. Pulse Open Loops offers free original CC0 synthesis kits: drums, bass, chords and percussion. Play the parts together, mute roles and download four WAVs for your DAW, without an account. Automated checks are not listening review.

Build and export your track, then use a public downloadable audio link for a free Pulse estimate. Submit only audio you have rights, permission, lawful access or another legal basis to process. Analysis uses an eligible one-track trial, Checkout or banked tokens.

Pricing and estimates

Estimates are free before paid analysis. One analysis up to 5 minutes. URL only; BPM, key and waveform. Up to two queued attempts if the first fails. Rights, permission, lawful access, or another legal basis required. Pulse prices selected tools by audio duration using the same tool multipliers exposed by /tools: waveform 0.06 tokens/second, BPM 0.1 tokens/second, and key 0.1 tokens/second. The current token price is $0.005.

60 second bpm example6 tokens$0.03
3 minute full v1.0 suite47 tokens$0.24
Cached resultMay cost less$0.001 current cache-hit price

Examples are estimates. Review the returned estimate before payment or API-key analysis. Final charges depend on measured duration, completed tools, cached analysis and checkout-path constraints.

Result guidance

Pulse helps discovery and utility by making analysis explicit: result, confidence, selected tools, and job status. Human listening judgment remains the final check for release, performance, or catalog commitments.

Rights-aware analysis boundary

Pulse is designed for audio the user has rights, permission, lawful access, or another legal basis to submit. Agents and apps should confirm that before analysis. Pulse does not provide transcription, stem separation, mastering, loudness correction, chord transcription, or track structure segmentation in v1.0.

Pulse is designed to make audio analysis auditable. Each analysis flow should make clear which URL was submitted, which tools were selected, what the estimate was, when rights confirmation was given, and whether the job completed, partially completed, failed, or expired.

Related Pulse resources

API docs · Agent playbook · MCP setup · Terms