Public docs

Build with Pulse audio intelligence.

Use this page as the human-facing map for the Pulse REST API, remote MCP server, token/payment paths, and agent-readable discovery files.

Connect the MCP server Get an API key Read the agent playbook

Start here

MCP clients

Use /connect for copy-ready Claude, Cursor, ChatGPT, VS Code, and raw Streamable HTTP setup.

Agents

Use /for-agents when deciding whether Pulse fits a DJ, DAW, catalog, app, or automation workflow.

API users

Use POST /trial/start for an email-free URL analysis within the current trial limits, or /signup for an API key with banked tokens, then call /estimate, /analyze, /upload, and /status/:jobId.

Remote MCP endpoint

Pulse speaks Streamable HTTP. Add your API key as the api_key query parameter on the connection URL.

https://mcp.studiosphere.space/mcp?api_key=YOUR_PULSE_API_KEY

StudioSphere Pulse product facts

Product nameStudioSphere Pulse
CategoryAudio intelligence API / MCP server
Registry namespace.studiosphere/pulse
Product APIhttps://pulse.studiosphere.space
MCP endpointhttps://mcp.studiosphere.space/mcp

Core REST endpoints

HealthGET /health
Tool pricingGET /tools
Start free trialPOST /trial/start
Estimate costPOST /estimate

Costs and duration are estimates. duration_source distinguishes a prior worker measurement, declared WAV sample frames, a format byte-rate assumption, or a placeholder. Supported WAV metadata is read from a bounded prefix; Pulse measures actual audio during processing and applies the pricing and refund terms.

Analyze by URLPOST /analyze
Upload and analyzePOST /upload
Job statusGET /status/:jobId
Status streamGET /status/:jobId/stream
Waveform SVG/PNGGET /status/:jobId/waveform.svg

Focused API and workflow guides

Use these pages when a builder, crawler, or agent is asking about a specific audio-intelligence job rather than the whole Pulse product.

BPM detection APITempo metadata for apps, samples, DJs, and agents.
Musical key detection APIHarmonic metadata for mixing, catalogs, and track development.
Waveform analysis APIPeak extraction for previews, dashboards, and timelines.
Audio MCP serverRemote MCP setup for Claude, Cursor, ChatGPT-style clients, and agents.
Sample library taggingBPM, key, and waveform metadata for authorized loops and one-shots.
DJ BPM and key workflowSet planning and harmonic grouping for authorized tracks.
Music catalog enrichment APIPractical metadata for sync, catalog, and media tools.
Predictable audio analysis pricingEstimate-first pricing with current tool multipliers.

Agent brief

/llms.txt is the concise agent-readable operating context.

Full agent brief

/llms-full.txt is the expanded API and MCP reference.

Available tools

Available now: BPM detection, musical key detection, and waveform peak data. Chord progression and structure detection are planned, but they are not part of the v1.0 available toolset.

Responsible-use boundary

Pulse is built for audio the user has rights, permission, lawful access, or another legal basis to submit. Results should be presented as structured audio analysis, not definitive legal, mastering, or musicology conclusions.

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.

Trial limits and demo

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.

Try the original CC0 Copper Step demo (180 seconds) when it fits your returned trial allowance. Check trial_allowance in /account/balance before retrying; remaining tokens do not grant another free track. Keep keys private.