# Suno — API Agent Score

> Score: 58/100 (Grade: D) | Domain: suno.com | Rubric: 1.0.0 | Checked: July 24, 2026

Suno scored 58/100 (D), classified "not-ai-ready".

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

## Summary

- Overall: 58/100 (D)
- Classification: not-ai-ready

## Category Scores

- API Design: 75/100 (B)
- Developer Experience: 57/100 (D)
- Agent Discovery: 65/100 (C)
- Agent Understanding: 57/100 (D)
- Agent Usability: 45/100 (F)

## Check Results

### API Design

- [pass] Schema coverage & depth — 116/116 (100%) public params are fully typed (no any/**kwargs). Analyzer confirms all methods have a derivable input schema. Investigated: sdk 100%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, docs 0%.
- [fail] Security & governance hygiene — No security.txt at /.well-known/security.txt or /security.txt. Investigated: wellknown 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 — Signup page at https://suno.com/ (CSR-rendered — body classifier inconclusive); free tier / sandbox documented in pricing/docs. Investigated: docs 100%.
- [warn] Description completeness — 55/58 operations carry a description. Investigated: sdk 95%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [fail] Code samples in docs — No detectable code samples across 1 sampled docs pages. Investigated: docs 0%.
- [fail] Changelog published — Official SDKs stale: newest activity 704 days ago. Investigated: sdk 0%.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (websites/help_suno_en, 348 snippets). Investigated: docs 100%, sdk 67%, cli 0%, mcp 0%, wellknown 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/1 pages return markdown). Investigated: docs 75%.
- [warn] Crawlable / AEO — No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.
- [fail] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://help.suno.com/llms.txt, https://help.suno.com/docs/llms.txt). Investigated: docs 0%, sdk 0%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/1 tested). Investigated: docs 79%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [fail] Docs structured data — Neither JSON-LD nor OpenGraph/meta tags detected across 1 assessed pages (1 JS-rendered). 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 1 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%.
- [fail] Idempotency documented — No built-in retry machinery was found; transient failures are not retried. Investigated: sdk 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 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

Suno's API program shows strength in basic crawlability and doc reachability, but partners and their AI agents face serious friction in two critical areas: they cannot reliably discover, understand, or act on the API without guessing, and onboarding is slow due to missing quickstarts, code samples, and runnable examples. Prioritize making the API machine-readable and agent-ready first — adding structured discovery files, agent instruction context, and runnable collections — then close the onboarding and operational gaps that stall partners before they write a single line of integration code.