# Retell AI — API Agent Score

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

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

[View full report](https://www.postman.com/ai/ai-ready-apis/company/retellai)
[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: 40/100 (F)
- Developer Experience: 71/100 (B)
- Agent Discovery: 93/100 (A+)
- Agent Understanding: 79/100 (B)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [fail] Schema coverage & depth — no .d.ts found. Investigated: sdk 0%.
- [fail] Security & governance hygiene — No security.txt at /.well-known/security.txt or /security.txt. Investigated: wellknown 0%.
- [fail] Example coverage — No detectable code samples across 20 sampled docs pages. Investigated: docs 0%, sdk 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 at https://www.retellai.com/sign-up; no free tier or sandbox language detected. Investigated: docs 100%.
- [pass] Changelog published — Newest official SDK activity 0 day(s) ago. Investigated: sdk 100%.
- [warn] Quickstart present — Quickstart page reachable (1 variants scanned starting at https://docs.retellai.com/get-started/quick-start) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [fail] Code samples in docs — No detectable code samples across 20 sampled docs pages. Investigated: docs 0%.
- [skip] Description completeness — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Docs reachable, not hard auth-gated — All 1 pages are publicly accessible. Investigated: docs 100%.
- [pass] Registry & SDK presence — Indexed on Context7 (websites/retellai, 2093 snippets). Investigated: docs 100%, cli 100%, sdk 63%.
- [warn] llms.txt present, valid & comprehensive — No /llms-full.txt found at the candidate origins. Investigated: docs 75%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.

### Agent Understanding

- [pass] Agent-navigable, token-efficient docs — All 1 pages contain server-rendered content. Investigated: docs 100%.
- [pass] Docs structured data — JSON-LD Article markup on 16/16 assessed pages (100%) with dateModified present. Investigated: docs 100%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 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

- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Idempotency documented — No surface produced evidence for this capability in this run.
- [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.
- [skip] Sandbox separation — No surface produced evidence for this capability in this run.

## Executive Summary

Retellai's agent discovery posture is a genuine strength — partners and agents can find your APIs without friction. However, the API contract itself is the critical weak point: missing schema depth, incomplete security hygiene, and absent examples mean partners and their AI agents are building against an underspecified surface, increasing integration failure and support burden. The immediate priority is hardening the OpenAPI contract and adding runnable, executable context so partners can reach a confident first integration — then close the remaining agent-readability gaps to make the program fully AI-agent ready.