resources / concepts

Concepts

How the API works and how to choose between its parts.

Concept

Audio formats and quality for music recognition

Which audio and video formats AudD accepts, the 10 MB standard-endpoint cap, and practical guidance on clip length, sample rate, channels, and compression for reliable matches.

read →
Concept

Controlling enterprise endpoint cost

How the AudD enterprise endpoint bills per 12 seconds of audio, and how limit, every, skip, and skip_first_seconds trade cost against completeness.

read →
Concept

Interpreting the recognition score

Every AudD match carries a confidence score. How to read it and how to set application-specific thresholds for auto-accept, blocking, and human review.

read →
Concept

Public database vs your custom catalog

When AudD recognition matches against the public 160-million-song database versus a private custom catalog you upload, and how to tell the two apart in a response.

read →
Concept

Retries: what's safe to retry and what consumes a request

Which AudD API failures are safe to retry, which consume a request, and how to configure the SDK's retry budget without double-billing or duplicating catalog entries.

read →
Concept

Standard, enterprise, or streams: how to choose

Pick the right AudD recognition surface for your input: standard for a short clip, enterprise for long files, streams for continuous live audio.

read →
Concept

The song_link (lis.tn) universal music link

Every AudD match includes a song_link on the lis.tn domain; how its ?thumb and ?provider conventions and the SDK helpers let you build cover-art and 'open in your service' UIs without requesting provider metadata.

read →
Concept

Webhook callbacks vs longpoll for stream results

Choose how to receive AudD stream recognition events: webhook callbacks when you can host a public HTTPS endpoint, longpoll when you can't.

read →