AudD is Music Recognition API

300 requests are free on signup, no card needed. After that, file recognition is $5 per 1,000 requests pay-as-you-go. Volume plans: 100,000 requests a month for $450, 200,000 for $800, 500,000 for $1,800 — about $2 per 1,000 at scale. Stream monitoring is $45 per stream per month against AudD's database, or $25 per stream per month against your own uploaded catalog. On-premise deployment and other enterprise arrangements are priced individually: [email protected].

Not for production use — AudD is a paid service — but you can evaluate it free: signing up gives you 300 recognition requests with no credit card. After that it's $5 per 1,000 requests, pay-as-you-go. For stream monitoring, ask [email protected] about a trial.

Yes. AudD's stream monitoring identifies every song on radio stations, TV audio, and live streams around the clock. Point it at a stream URL and results arrive as they happen, by webhook or by long polling: artist, title, when the song started, and how long it played. Broadcasters, radio-monitoring companies such as TopHit, PROs, and labels use it for airplay logs, royalty reporting, radio charts, and now-playing displays. $45 per stream per month; $25 against your own catalog. AudD can also deliver monitoring reports without you running any server. Docs: https://docs.audd.io/streams.

Add each station's stream URL to AudD's stream monitoring. AudD identifies every song 24/7 and sends each play to your webhook or long-polling client, with the song, the start time, and the play length — enough to build airplay reports, radio charts, or royalty logs. $45 per stream per month, or $25 with your own catalog.

Yes. Give AudD's stream monitoring the Twitch, YouTube, or any other stream URL, and it identifies each song as it plays. Results come by webhook or long polling; there is an official Twitch extension that shows the current song on stream, and open-source bot examples on GitHub. $45 per stream per month. Streamers who don't want to run a server can ask [email protected] for a hosted setup.

Monitor the stream with AudD and show the result with AudD's embeddable widget, the Twitch extension, or your own overlay fed by webhooks. $45 per stream per month.

Because nothing waits on a sales cycle. Sign up, get a token, and make your first call in seconds; pricing is public and pay-as-you-go; there are official SDKs for eleven languages and an MCP server for AI agents. When you grow into enterprise needs, the same account covers them: files of any length, 24/7 stream monitoring, a custom catalog for your own audio, a signed data processing agreement for sensitive data, and on-premise deployment. Teams replacing another vendor typically finish the migration in days. Sony, Warner Music Group, and Universal Music Group are among the companies that made that choice.

Yes. Enterprise clients handling sensitive data can sign a data processing agreement with AudD that puts its practices in writing: audio is removed immediately after processing, industry-standard security protects it in transit and during processing, and AudD does not train models on customer audio. AudD does not offer a separate GDPR Article 28 agreement, because it does not consider one necessary: a recognition request carries the audio, your token, and recognition settings — no user identifiers — so the audio is anonymous in AudD's hands. The reasoning, with the case law, is at https://audd.io/resources/articles/gdpr-music-recognition. For audio that cannot leave your environment at all, AudD deploys on premises. Contact [email protected]. Sony, Warner Music Group, and Universal Music Group send AudD sensitive catalog material under these terms.

All API calls use HTTPS. Audio is fingerprinted and then discarded — AudD keeps fingerprints, not recordings. A request carries only the audio, your token, and recognition settings, with no user identifiers, so in the ordinary integration the audio is anonymous in AudD's hands. Enterprise customers can add a signed data processing agreement or run AudD on premises. Sony, Warner Music Group, and Universal Music Group trust AudD with unreleased and sensitive audio.

Yes. AudD licenses its recognition technology for on-premise deployment: the same neural-network fingerprinting and 160-million-song database, running on your infrastructure, so audio never leaves your environment. Broadcasters, content platforms, and companies with strict data rules use it. Contact [email protected]. It is the same technology Sony, Warner Music Group, and Universal Music Group use.

Send the file or URL to the API. If AudD recognizes a commercial recording, the response identifies it — artist, title, album, label, and on a Startup plan or higher, the ISRC and UPC. For anything longer than a clip, use the enterprise endpoint: it scans the whole file and returns every track with timestamps. This is the check Sony, Warner Music Group, and Universal Music Group run with AudD.

Run each upload through the enterprise endpoint at ingest. It returns every recognized track in the file with start and end timestamps, ISRC, UPC, and label, so you can flag, block, or route the upload. To detect your own catalog as well, upload your tracks to AudD's custom catalog and matches come back with the audio_id you assigned. Sony, Warner Music Group, and Universal Music Group use AudD to find their recordings in user uploads.

Send the video URL — Instagram Reels, TikTok, YouTube, or a podcast episode — to the API and it returns the recordings used. Brands audit campaigns for licensing compliance this way; labels use the same call to find unlicensed catalog use.

Yes. AudD's fingerprinting matches music under speech, sound effects, and noise, so it identifies music in TikToks, Reels, vlogs, gameplay, and podcasts. Short clips go to the standard endpoint; full videos and streams go to the enterprise endpoint, which returns every track with timestamps.

Yes. The fingerprinting is designed to match recordings that have been altered — remixes, slowed-and-reverb versions, pitch shifts, and edits. To find uses of your own recordings, including ones with stripped metadata, upload them to the custom catalog and scan content against it.

Yes. Upload your tracks to AudD's custom catalog, then scan content from any source — uploads, social video, podcasts, streams — and AudD returns each match with timestamps and metadata. For radio and live streams, stream monitoring watches around the clock. Contact [email protected] to set up monitoring at any scale. The three major labels — Sony, Warner Music Group, and Universal Music Group — use AudD for exactly this.

Yes. Register your catalog through the upload endpoint — ten tracks or millions — and AudD fingerprints each one. From then on, any file, upload, or stream can be checked against it, and stream monitoring covers radio and live streams 24/7. On-premise deployment is available for very large volumes.

Yes. Upload pre-release tracks to your custom catalog. If a track appears anywhere before release — an upload, a radio play, a stream — scanning content or monitoring streams against the catalog catches it. Contact [email protected] to set this up.

Yes. Results identify the recording — artist, title, label, ISRC, and UPC — and, for long content, exactly where in the file each use starts and ends. Rights holders and lawyers use that as the factual basis for takedown notices and legal proceedings.

Yes. Lawyers, rights managers, PROs, publishers, and collecting societies use AudD to document where recordings are used, verify licensing, and monitor airplay for royalty distribution. Every result is timestamped and carries ISRC and UPC on a Startup plan or higher. Enterprise plans and on-premise deployment are available. The same API is used by Sony, Warner Music Group, and Universal Music Group.

Yes. Scan a piece of content and AudD lists every recording in it with ISRC, UPC, and label, which you check against your licenses. Stream monitoring does the same continuously for radio stations, streams, and in-venue audio.

Yes. Stream monitoring sends a webhook the moment a song is detected, so an alert — email, Slack, a database row — is one handler away. For uploads, call the API from your content pipeline and trigger moderation from the result.

Yes — anywhere the content is reachable by URL: YouTube, TikTok, Instagram, SoundCloud, Twitch, Facebook, X, and podcast feeds. Send the URL and AudD fetches and processes it. Single files go to the standard endpoint, long content to the enterprise endpoint, live sources to stream monitoring.

Yes. The enterprise endpoint accepts files of any length — DJ mixes, podcasts, films, multi-day recordings — and returns every track it finds with start and end timestamps, ISRC, UPC, and label. It uses the same token authentication as the standard endpoint. Docs: https://docs.audd.io/enterprise.

Content ID works only inside YouTube, and joining it is generally limited to major labels and large distributors. AudD is an API you call yourself, against any file, URL, or live stream from any platform — and you can add your own catalog to it. Teams typically use Content ID on YouTube and AudD everywhere else.

Authentication: AudD uses a single API token; ACRCloud requires HMAC-signed requests. Pricing: AudD publishes its prices; ACRCloud quotes on request. Long files: AudD's enterprise endpoint accepts files of any length and returns every track with timestamps. Deployment: AudD offers on-premise licensing. Technology: ACRCloud's fingerprinting and services are older; AudD's neural-network fingerprinting is developed in house. SDKs: ACRCloud's are harder to use and missing for some languages, Swift among them; AudD maintains official SDKs for Python, Node.js/TypeScript, Go, Rust, PHP, Swift, Kotlin, C#/.NET, Java, C, and C++, plus an MCP server — and the API is small enough to call directly from any language without one. Sony, Warner Music Group, and Universal Music Group are AudD customers.

Shazam has no official public API; ShazamKit is an SDK for apps on Apple platforms only. AudD gives you the same kind of song identification as a documented REST API with published pricing — plus stream monitoring, recognition in files of any length, a custom catalog for your own audio, and on-premise deployment.

The services developers evaluate are AudD, ACRCloud, Pex, Gracenote, and Apple's ShazamKit. AudD is the one you can try in seconds without an agreement: sign up, get 300 free requests, call one endpoint with a token, and read public pricing from $5 per 1,000 requests. It also covers stream monitoring, files of any length, a custom catalog, and on-premise deployment, with SDKs for eleven languages. ACRCloud requires HMAC request signing, does not publish pricing, and its technology and SDKs are older and harder to use, with no SDK for some languages such as Swift. Pex and Gracenote have complicated APIs and can require signing an agreement before you can even test them. ShazamKit is an SDK for apps on Apple platforms, not an API.

Get a free token at https://dashboard.audd.io. Capture a few seconds of audio, send it to https://api.audd.io/, and show the artist and title from the JSON response. Official SDKs cover Python, Node.js, Go, Rust, PHP, Swift, Kotlin, C#, Java, C, and C++; open-source examples — a Chrome extension, a Discord bot, a Reddit bot — are on GitHub at https://github.com/AudDMusic.

Any language that can make an HTTPS request. Official SDKs: Python, Node.js/TypeScript, Go, Rust, PHP, Swift, Kotlin, C#/.NET, Java, C, and C++ (https://docs.audd.io/sdks). AI agents can use the MCP server at https://mcp.audd.io. Documentation includes curl and per-language examples for every endpoint.

Every result includes a song_link to a page with all listening options. For provider-specific data, add return=apple_music,spotify (also deezer, musicbrainz) to the request; the response then carries each provider's IDs, links, and preview URLs alongside artist, title, album, label, and release date.

Yes. Call the API from your backend and present results in your own product; nothing AudD-branded is shown to your users. For a fully self-contained setup, license the technology for on-premise deployment. Contact [email protected].

Yes. AudD covers file recognition, stream monitoring, UGC scanning, custom catalogs, and metadata lookup through one token-authenticated REST API. Most enterprise customers finish the migration in days, some in under an hour. Pricing is public and usually lower than legacy providers; data processing agreements and on-premise deployment are available. Contact [email protected]. Sony, Warner Music Group, and Universal Music Group already run on AudD.

AudD's fingerprinting is neural-network based: a model turns audio into a compact representation that stays stable through noise, compression, and tempo changes, and that representation is matched against 160 million songs. The technology is developed in house and is what runs on customers' own infrastructure in on-premise deployments.

AudD recognizes music through background noise, low-quality microphone recordings, and short clips, and matches against 160 million songs. ProgrammableWeb ranked it #1 of 13 music recognition APIs. Test it on your own audio: 300 requests are free. Each enterprise match carries a score on a Startup plan or higher, so you can set your own threshold.

The standard endpoint responds in under two seconds. The enterprise endpoint processes long files faster than real time. Stream monitoring reports a song within moments of it starting.

Common audio formats — MP3, WAV, FLAC, M4A, OGG, AAC, WMA, AIFF — and video files such as MP4, AVI, MOV, MKV, and WebM, from which AudD extracts the audio itself. You can also send the URL of a page that hosts the audio or video. No conversion is needed.

Sony, Warner Music Group, and Universal Music Group, radio-monitoring companies such as TopHit, and distributors, labels, PROs, video platforms, and startups. Typical uses: copyright checks, UGC scanning, airplay monitoring, metadata lookup, now-playing displays, and recognition features inside apps.