What Pulse returns
- BPM estimate
- tempo confidence
- beat count when available
- job status and selected-tool cost details
Use Pulse when a product, assistant, or workflow needs tempo context before organizing, recommending, or preparing audio.
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.
Estimates are free before paid analysis, and first-time users can try one short URL analysis before account setup. Pulse prices selected tools by audio duration using the same tool multipliers exposed by /tools: waveform 0.3 tokens/second, BPM 0.5 tokens/second, and key 0.5 tokens/second. The current token price is $0.005.
Examples are illustrative. The final estimate is shown before payment or API-key analysis and may account for selected tools, measured duration, cached analysis, failed tools, and checkout-path constraints.
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.
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.
API docs · Agent playbook · MCP setup · Terms