Skip to content
AudioLab .tools
Sign in
/labs / signallab
Audio intelligence Beta API · MCP

SignalLab

Tags, QA flags, and search for audio at scale.

Less about creativity, more about structure. SignalLab turns piles of audio files into searchable, taggable, QA-checked assets that downstream tools can actually use.

Try the demo Read the docs
SignalLab — abstract brand imagery
Flagship
SignalLab Indexer
MVP
Indexer demo + JSON-out + one integration recipe.
Audience
Audio-heavy SaaS teams · Archives and broadcasters · Developers building on audio
Monetization
API · usage-based pricing · developer plans.
01 Live demo · indexer

SignalLab Indexer

Drop in audio, get back technical tags, semantic hints, risk flags, and a metadata schema your stack can ingest.

Files are decoded in your browser. JSON output is download-only.

How this is measured
02 Use cases
01

Archive enrichment

Drop 50 hours of unstructured recordings, get back tags, speaker turns, silence regions, and a searchable schema.

02

QA gates for ingest

Block files at upload time when they fail silence, clipping, or noise-floor thresholds.

03

Semantic audio search

Find every clip with "outdoor crowd noise + male speech" across a content library without listening to anything twice.

03 What makes it different

SignalLab treats audio like data. Schema-first, API-first, and built so the people downstream (editors, ML teams, archive managers) can actually use the output.

Also in SignalLab

  • Silence/clipping detector

    Catch the bad parts before your editor does.

  • Speaker/event marker

    Auto-mark turns, silences, and scene changes.

04 Roadmap
Now 01
  • Indexer demo concept
  • Tag schema draft
  • Silence/clipping detector
Next 02
  • REST API
  • Webhooks
  • Speaker diarisation MVP
Later 03
  • Semantic search beta
  • Custom tag training
  • On-prem option
05 Docs · tutorials

Read the system, not the marketing.

Free in the browser · API + MCP at scale

Run SignalLab from your own code or any AI agent.

The demo above runs free, on your device. The same analysis is a hosted REST API and an MCP server — one key, EBU R128 / BS.1770-4 verified. SignalLab exposes 1 endpoint / 1 MCP tool.

REST · POST

  • /v1/signallab/index content tagging + metadata

MCP tools · https://audiolab.tools/mcp

  • index_signal

Quick start

curl -X POST https://audiolab.tools/v1/signallab/index \
  -H "Authorization: Bearer $AUDIOLAB_KEY" \
  -H "content-type: application/json" \
  -d '{"url":"https://your-audio.wav"}'
Get a key · Add to Claude API docs OpenAPI spec

Continue the workflow

Where this leads.

MixLab

Master a region

Send the full file to MixLab for BS.1770-4 LUFS analysis, true-peak, and tonal balance on the program feed.
VoiceLab

QA the voice regions

When SignalLab finds voice content, push the same audio to VoiceLab for sibilance and noise-floor scoring.
HearLab

Plan caption coverage

Region timestamps from SignalLab make it explicit which sections need accessibility attention in HearLab.
CueLab

Build a cue sheet from regions

Indexed regions translate naturally into broadcast cue triggers. Plan the sequence in CueLab.
SkillLab

Train the classifier in your head

SkillLab includes drills on voice-vs-music-vs-noise classification, the same task SignalLab automates.

MixLab, VoiceLab, and SignalLab hand audio off to one another without re-uploading. When you finish an analysis in one of those, the → Lab buttons in the demo chrome carry your decoded audio directly into the next lab’s analysis flow. The other labs open fresh.