Crompton Network vs Url

crompton_lyrics

Get time-aligned lyrics for a track. Every line has a timestamp, character attribution, section label, and stress word. Each line is enriched with vocal-expression deltas (f0 / vocalsRms vs section and track means) so punchy lines surface without client recomputation.

crompton_moment

Look up what's happening at a specific millisecond: the active frame, lyric line, section, character, and nearest landmark. For 'remember that part where...' queries.

crompton_digest

Get the hand-authored editorial digest for a track. Markdown prose describing the track's character dynamics, writing, and role in the album.

crompton_cookbook

Get the Stage API cookbook. Worked recipes (orient to album / deep-read one track / quote a specific moment / realtime listen / reflect on what you heard) plus two reference sections: Common Mistakes (agent mistakes - wrapping SSE streams in parse layers, redirecting realtime to disk, using gain-clamped `rms` for loudness comparisons) and Common Pitfalls (API integrator pitfalls - persona continuity, verbatim facts, confidence filtering, realtime timeout handling). Read this first if you're new to the API. Pass `section` to slice a single part if you only need one.

crompton_listen

Sample a track's realtime stream (up to 100 frames ≈ 6.7s at 15fps). Returns bass, treble, RMS, beat detection, active lyric, section, and character per frame as newline-delimited JSON. Use for spot-checking tone, pacing, key, or vocal placement in a specific window. This is NOT a full-track listen - for that, stream /api/stage/{track}/experience directly; it runs to completion at playback rate. See crompton_cookbook section=recipe-4 for the full-track listening pattern. Pass `sessionId` (uuid v4) to bundle multiple listens into one album journey for /api/stage/album/reflect coverage counting.

crompton_version

Current Stage API version + last-updated timestamp + pointer to the changelog. Use to detect API drift across sessions when you can't reach git history. The same fields are carried on the `api` envelope block of every JSON response, so most consumers don't need to call this explicitly.

crompton_changelog

The Stage API changelog (Markdown). Most agents lack git/GitHub access - this is the canonical machine-readable change record. Call after `crompton_version` if you spot drift since you last listened.