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 /signup for an API key, 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

Core REST endpoints

HealthGET /health

Tool pricingGET /tools

Estimate costPOST /estimate

Analyze by URLPOST /analyze

Upload and analyzePOST /upload

Job statusGET /status/:jobId

Status streamGET /status/:jobId/stream

Waveform SVG/PNGGET /status/:jobId/waveform.svg

Agent brief

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

Full agent brief

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

MCP manifest

/.well-known/mcp/server.json exposes the machine-readable server descriptor.

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.