Music Catalog Enrichment API for Practical Audio Metadata

What Pulse returns

tempo metadata
harmonic metadata
waveform preview data
analysis status and cost breakdown

Example workflow

Estimate and analyze authorized catalog assets, store the resulting BPM/key/waveform metadata with each track, and let humans make the final creative calls.

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, key, waveform example16 tokens$0.08

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

For audio of at least 30 seconds whose type is unconfirmed, strong BPM or key readings may be shown as Audio detection candidate with Review manually. These unverified tags require a listening check; detector confidence is not a calibrated probability of accuracy.

BPM is an estimate with confidence metadata. For DJ, loop, and edit workflows, verify whether the useful working tempo is the detected BPM, half-time, or double-time.

Key detection is harmonic context, not a guarantee. Low-confidence, atonal, noisy, modulating, or very short audio should be checked by ear before committing catalog tags or DJ transitions.

For DJ planning, convert the detected key into your preferred harmonic-mixing notation, including Camelot-compatible labels, then use adjacent and relative keys as candidates rather than rules.

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.