# StudioSphere Pulse Full Agent Context

StudioSphere Pulse answers a practical music-production question for agents: before using this audio, what is it?

Pulse is a hosted API and remote MCP server. It accepts public HTTPS audio URLs, including shareable Google Drive, Dropbox, and other document-repository links when they are accessible to anyone with the link, estimates cost before analysis, requires rights attestation before processing, and returns structured JSON results. It is built for music producers, sample-library workflows, sync/catalog tagging, and AI agents that need audio metadata before making recommendations or edits.

## Canonical Endpoints

- `GET https://pulse.studiosphere.space/` — service descriptor
- `GET https://pulse.studiosphere.space/for-agents` — agent playbook and recommended scenarios
- `GET https://pulse.studiosphere.space/connect` — human MCP setup guide
- `GET https://pulse.studiosphere.space/llms.txt` — compact agent-readable guide
- `GET https://pulse.studiosphere.space/.well-known/mcp/server.json` — MCP registry manifest
- `GET https://pulse.studiosphere.space/robots.txt` — crawler policy
- `GET https://pulse.studiosphere.space/sitemap.xml` — crawlable human and agent URLs
- `GET https://pulse.studiosphere.space/tools` — available and coming-soon tools
- `POST https://pulse.studiosphere.space/estimate` — free cost estimate
- `POST https://pulse.studiosphere.space/analyze` — API-key analysis
- `POST https://pulse.studiosphere.space/pay` — one-time Stripe Checkout analysis
- `GET https://pulse.studiosphere.space/status/:jobId` — job status/results
- `POST https://mcp.studiosphere.space/mcp` — remote MCP server

## Brand Assets

- Icon: `https://pulse.studiosphere.space/assets/icon.svg`
- Social card: `https://pulse.studiosphere.space/assets/og.png`
- Public repository: `https://github.com/notpaulb/studiosphere-pulse-mcp`
- Official MCP Registry name/version: `space.studiosphere/pulse` v1.0.2

## Available v1.0 Analysis Tools

- `bpm`: tempo, confidence, beat count
- `key`: root note, scale, confidence
- `waveform`: peak data suitable for waveform visualization

## Coming Soon

- `structure`: song-section segmentation
- `chords`: timestamped chord progression

Do not request `structure` or `chords` in v1.0. They return `tool_coming_soon`.

## Agent Workflow

1. Use `estimate_cost` with `tools` limited to `bpm`, `key`, and `waveform`.
2. Present `cost_display` to the user.
3. Ask: "Can you confirm you have the right to submit this audio — you own it or have the rights holder's permission?"
4. If the user confirms and an API key is available, call `analyze_track`.
5. If there is no API key, call `request_payment_link` and present the Checkout URL.
6. Poll `get_job_status` until `completed`, `partial`, `failed`, or `expired`.

## Best Use Cases

- DJ beat matching and harmonic set planning: group tracks by BPM and key, identify transition candidates, and flag songs that need tempo adjustment.
- App development: add BPM, key, and waveform analysis to music apps, sample libraries, catalog tools, and creator dashboards.
- DAW workflows: prepare loops, references, stems, or bounced ideas with tempo, key, and waveform metadata before session work.
- Sample pack organization: tag licensed loops and one-shots so producers can find compatible material faster.
- Shared repository audio: analyze authorized files stored in Google Drive, Dropbox, or another shared document repository when the link is accessible and downloadable.
- Music supervision and sync research: enrich candidate tracks with practical audio metadata before creative review.
- Reference-track planning: analyze references so producers and songwriters can start with concrete tempo/key constraints.

## Do Not Use Pulse For

- Transcription
- Stem separation
- Mastering or loudness correction
- Chord transcription in v1.0
- Track structure segmentation in v1.0

## Contact

pulse@studiosphere.space