# Deezer — API Agent Score

> Score: 67/100 (Grade: C) | Domain: deezer.com | Rubric: 1.0.0 | Checked: September 22, 2026

Deezer scored 67/100 (C), classified "partially-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/deezer)
[All organizations](https://www.postman.com/ai/ai-ready-apis/llms.txt)

## Summary

- Overall: 67/100 (C)
- Classification: partially-ready

## Category Scores

- API Design: 91/100 (A+)
- Developer Experience: 66/100 (C)
- Agent Discovery: 73/100 (B)
- Agent Understanding: 65/100 (C)
- Agent Usability: 48/100 (F)

## Check Results

### API Design

- [pass] Schema coverage & depth — package.json "types" → index.d.ts. Investigated: sdk 100%.
- [pass] Security & governance hygiene — Code is formatter-clean with zero linter errors and zero style warnings. Investigated: sdk 100%, wellknown 50%.
- [warn] Example coverage — README is present but has no runnable quickstart. Investigated: sdk 50%, docs 0%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Auth declared & discoverable — No surface produced evidence for this capability in this run.

### Developer Experience

- [pass] Self-service developer portal — Self-service signup available at https://account.deezer.com/en-us/signup/, but no free tier or sandbox is documented, so an agent may hit a paywall before the first call. Investigated: docs 100%.
- [warn] Quickstart present — Quickstart page is reachable at https://developers.deezer.com/login?redirect=/api/quickstart (1 variants scanned) but has no runnable code sample in its HTML or .md variant, so there's nothing to copy and run. Investigated: docs 50%.
- [fail] Code samples in docs — No code samples detected across 1 sampled docs pages, so a coding agent gets no ready-to-use examples. Investigated: docs 0%.
- [skip] Description completeness — No surface produced evidence for this capability in this run.
- [skip] Changelog published — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/deezer-python_readthedocs_io_en_stable_api_reference, 93 snippets). Investigated: docs 100%, sdk 58%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/1 pages return markdown). Investigated: docs 75%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://developers.deezer.com/llms.txt, https://developers.deezer.com/docs/llms.txt). Investigated: docs 33%, sdk 0%.
- [warn] Crawlable / AEO — No sitemap found via robots.txt or /sitemap.xml on the docs host, so AI search engines have no crawl map for your docs. Investigated: wellknown 50%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/1 tested). Investigated: docs 79%.
- [warn] Agent instructions file (AGENTS.md) — No agents.md or skill.md context file found (nice-to-have for agent operation). Investigated: sdk 50%, wellknown 0%.
- [fail] Docs structured data — No JSON-LD or OpenGraph/meta tags found across 1 assessed pages (1 JS-rendered), so answer engines have nothing to cite. Investigated: docs 0%.
- [skip] Machine-readable errors (RFC 9457) — No surface produced evidence for this capability in this run.
- [skip] Operation purpose clarity — No surface produced evidence for this capability in this run.
- [skip] Description consistency across surfaces — Only 0 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%.
- [warn] Runnable collection with test scripts — README is present but has no runnable quickstart. Investigated: sdk 50%, platform 0%.
- [fail] Idempotency documented — No built-in retry machinery was found; transient failures are not retried. Investigated: sdk 0%.
- [skip] Rate-limit signaling — No surface produced evidence for this capability in this run.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Deezer's API Design is a clear strength — partners get a well-shaped, machine-readable contract to build against. The two areas that most threaten partner and agent adoption are Agent Understanding (docs are invisible to answer engines and AI crawlers) and Agent Usability (no retry or idempotency guidance leaves partners exposed to transient failures at integration time). Fixing structured data and code sample gaps will unlock self-serve onboarding; adding idempotency and retry documentation will make production integrations trustworthy for both human partners and their AI agents.