# Modal — API Agent Score

> Score: 76/100 (Grade: B) | Domain: modal.com | Rubric: 1.0.0 | Checked: July 24, 2026

Modal scored 76/100 (B), classified "partially-ready".

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

## Summary

- Overall: 76/100 (B)
- Classification: partially-ready

## Category Scores

- API Design: 72/100 (B)
- Developer Experience: 64/100 (C)
- Agent Discovery: 87/100 (A)
- Agent Understanding: 69/100 (C)
- Agent Usability: 86/100 (A)

## Check Results

### API Design

- [warn] Schema coverage & depth — 47 of 672 public signatures use loose types (anyTypeRatio=0.070). Investigated: sdk 92%.
- [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://modal.com/signup (CSR-rendered — body classifier inconclusive); free tier / sandbox documented in pricing/docs. Investigated: docs 100%.
- [pass] Changelog published — Newest official SDK activity 0 day(s) ago. Investigated: sdk 100%.
- [warn] Description completeness — 82/97 operations carry a description. Investigated: sdk 85%.
- [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 20 sampled docs pages. Investigated: docs 0%.

### Agent Discovery

- [pass] Docs reachable, not hard auth-gated — All 50 sampled pages are publicly accessible. Investigated: docs 100%.
- [pass] Registry & SDK presence — Indexed on Context7 (websites/modal, 4003 snippets). Investigated: docs 100%, sdk 100%, cli 100%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 50 sampled pages. Investigated: docs 71%, sdk 0%.
- [warn] Crawlable / AEO — No sitemap discoverable via robots.txt or /sitemap.xml on the docs host. Investigated: wellknown 50%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Single base error "ModalError" with 53 subclasses. Investigated: sdk 100%.
- [warn] Agent-navigable, token-efficient docs — 23 of 50 sampled pages have content starting past 50% (worst 78%). Investigated: docs 65%.
- [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 3 assessed pages (3 JS-rendered). Investigated: docs 0%.
- [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

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%.
- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%.
- [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

Modal's API program shows real strength in agent discoverability and usability — both graded A — but partners and their AI agents face meaningful friction in two areas that matter most for adoption: the documentation lacks the structured signals and machine-readable context that agents need to act without guessing, and onboarding is missing the quickstart and code samples that get partners to a first successful call in minutes. Closing these gaps — agent-readable docs with structured instructions, plus runnable onboarding assets — should be the immediate priority to unlock self-serve partner growth.