Long-form publications from the engineering and rights teams. Whitepapers on architecture, annual industry reports, methodology notes, and API reference for partners building on the platform. Free; request via the contact form.
Multi-scale derivative detection architecture and benchmarks. Covers the four-detector design, the agreement rule, the indexing pipeline, false-positive analysis across genre boundaries, and the production performance envelope.
// Published 2026-01 · Bay Wu, Marius Aoki
Request copy →Aggregate findings from eight reconciled catalogues during 2025. Median 5.1% recovered, range 3.4–9.7%. Detailed breakdown of where money goes missing — neighbouring rights, mechanicals, derivative attribution, sync — with per-territory analysis.
// Published 2026-02 · Marius Aoki, Reni Wexford
Request copy →Endpoints for usage normalisation, works matching and claim management. REST + GraphQL. Includes the OpenAPI spec, an authentication guide, and reference implementations in Python, TypeScript and Go.
// Updated quarterly · API team
Request access →How sub-genre embeddings are trained, calibrated and used in production. Contrastive training objective, calibration against twelve working A&R teams, re-ranking layer design, recall analysis by genre, honest documentation of failure modes.
// Published 2025-11 · Reni Wexford
Request copy →Our whitepapers and reports use anonymised, aggregate-only data. We do not publish per-artist streams, per-artist royalty figures, or per-track derivative counts — even for acts on partner rosters who have consented to be named publicly. The discipline keeps the partnership trust intact.
You will not find a Nomad whitepaper that says "vs Shazam" or "vs Pex." Our published benchmarks are against open academic baselines and against our own internal predecessor systems. Competitive benchmarks against named commercial systems are not informative; they're rhetoric.
We don't publish "Where AI in music is going" essays. Other people do that well; we don't need to. The reports we do publish describe what we and our partners have already done — not what anyone might do next year.
Use the contact form, tell us which publications you'd like and a bit about your context — we usually respond within one business day.