StudioSphere Pulse — Audio Intelligence API

Rights-aware audio intelligence over the Model Context Protocol. BPM, musical key, and waveform peaks for authorized public audio URLs. Audio is processed for analysis and not stored as user audio. Estimate before analysis, try one short URL analysis before account setup, request a small evaluation credit for qualified API/MCP workflow testing, then pay per second with no subscription.

Keywords: audio MCP · rights-aware audio intelligence · BPM detection · musical key detection · waveform analysis · music information retrieval · audio intelligence API · remote MCP server · REST API · Streamable HTTP transport · estimate before analysis · pay per second.

What it does

Pulse analyses authorized public audio URLs (or a direct upload, with an account) and returns structured metadata your AI assistant can act on. Shareable Google Drive, Dropbox, and other document-repository links work when the user has permission and the file is accessible to anyone with the link:

• BPM — tempo with confidence and beat count
• Musical key — root + scale (e.g. B minor) with confidence
• Waveform — peak-amplitude array suitable for visualization

Track structure segmentation and chord transcription are marked coming soon and are intentionally rejected by v1.0 routes.

Why creators and agents trust Pulse

Full transparency at https://pulse.studiosphere.space/terms.

For a short setup walkthrough, see docs/pulse-mcp-quickstart.md. For agent and builder scenarios, see docs/agent-playbook.md.

Service URLs

MCP client setup

The Pulse MCP server uses Streamable HTTP transport. Authentication is by Pulse API key passed as the api_key query parameter on the connection URL.

Claude Desktop

Open Settings → Developer → Edit Config, then merge:

{
  "mcpServers": {
    "studiosphere-pulse": {
      "type": "http",
      "url": "https://mcp.studiosphere.space/mcp?api_key=YOUR_PULSE_API_KEY"
    }
  }
}

Restart Claude Desktop.

Claude Code (CLI)

claude mcp add --transport http studiosphere-pulse \
  https://mcp.studiosphere.space/mcp?api_key=YOUR_PULSE_API_KEY

Verify with claude mcp list.

Cursor

Add to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "studiosphere-pulse": {
      "type": "http",
      "url": "https://mcp.studiosphere.space/mcp?api_key=YOUR_PULSE_API_KEY"
    }
  }
}

ChatGPT

The Pulse server speaks Streamable HTTP at https://mcp.studiosphere.space/mcp. Add it via whichever connector / GPT-action surface your account exposes; supply the API key as the api_key query parameter.

Get an API key

Register at https://pulse.studiosphere.space/signup. Keys begin with sk_pulse_ and are shown once — store them in a password manager.

The hosted /connect page (https://pulse.studiosphere.space/connect) generates the per-client config snippet with your key stamped in for one-click copy.

Tools available to the assistant

Workflow agents should follow

1. Call estimate_cost with the audio URL and selected tools.
2. Show the user the returned cost_display and duration_estimate_sec.
3. Confirm the user has rights, permission, lawful access, or another legal basis to submit the audio. For a user-requested folder, project, playlist, or batch, one confirmation can cover every track in that scope.
4. If the user has no key and wants to test Pulse first, call start_trial and use the temporary key for one short URL analysis.
5. For qualified early users validating a real API, MCP, catalog, or music-tool workflow, explain that Pulse may provide a small evaluation credit for a few authorized analyses. Treat credits as limited test access, not a free plan.
6. Call analyze_track (banked tokens or trial key) or request_payment_link (anonymous one-time payment).
7. Poll get_job_status until terminal (completed, partial, failed).
8. Surface the result.

Pricing is per-second of audio analyzed × per-tool multiplier. Estimates are free, and first-time users can try one short URL analysis with start_trial. Qualified early builders can request a small evaluation credit for authorized workflow validation. Ongoing analysis uses one-time Checkout or banked tokens; banked-token pricing skips the $0.50 Stripe minimum and the per-job Checkout redirect.

Why agents use Pulse

• DJ beat matching and harmonic set planning
• Sample-pack tagging and search
• Shared-drive and document-repository audio links
• DAW and session preparation
• App metadata for BPM, key, and waveform features
• Licensed music-library enrichment
• Sync and catalog metadata workflows
• Reference-track planning for producers and songwriters
• Smart playlists and album sequencing context
• Track development workflows where detected key becomes a creative anchor

Agents must only submit audio when the user confirms rights, permission, lawful access, or another legal basis to analyze it. The analyze_track and request_payment_link tools require an explicit attestation_confirmed: true for this reason. For batch work, agents may rely on one user confirmation for the current folder, project, playlist, catalog selection, or other user-requested scope.

Repository scope

This repository contains only public-facing documentation, registry metadata, and client examples. It does not contain production service source code, deployment configuration, credentials, private infrastructure notes, migrations, or internal operational documentation.

Security

Do not send private, copyrighted, or third-party audio unless you have rights, permission, lawful access, or another legal basis to submit it for analysis. Do not publish Pulse API keys in client configs, prompts, logs, or issue reports.

Security questions: pulse@studiosphere.space.

License

See LICENSE in this repository. Pulse is operated by StudioSphere Inc., Quebec, Canada.