# Scale — API Agent Score

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

Scale scored 79/100 (B), classified "partially-ready".

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

## Summary

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

## Category Scores

- API Design: 96/100 (A+)
- Developer Experience: 79/100 (B)
- Agent Discovery: 93/100 (A+)
- Agent Understanding: 86/100 (A)
- Agent Usability: 51/100 (D)

## Check Results

### API Design

- [pass] Machine-readable, versioned contract — API versioning documented in the docs site at https://api-reference.scale.com/docs/api-compatibility-policy. Investigated: spec 100%, docs 100%.
- [pass] Auth declared & discoverable — authentication documented in the docs site at https://docs.gp.scale.com/docs/authentication. Investigated: docs 100%, spec 50%.
- [warn] Schema coverage & depth — Medium parameter complexity (avg 1.8 params/op; nested/body schemas present). Investigated: spec 83%, sdk 25%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 50%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%, spec 0%, docs 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://scale.com/demo; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [pass] Quickstart present — Quickstart at https://docs.gp.scale.com/docs/getting-started with a runnable first-call sample. Investigated: docs 100%.
- [pass] Changelog published — changelog documented in the docs site at https://docs.gp.scale.com/changelog/release-notes. Investigated: spec 100%, docs 100%, sdk 100%.
- [warn] Description completeness — 5/10 operations lack a description. Investigated: sdk 50%, spec 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 (telekom/scale, 1614 snippets). Investigated: docs 100%, sdk 67%, cli 0%.
- [warn] llms.txt present, valid & comprehensive — llms.txt covers 356/658 sitemap doc pages (54%); 302 missing. Investigated: docs 75%, sdk 0%.
- [pass] Crawlable / AEO — Docs paths crawlable by all monitored AI agents. Investigated: wellknown 100%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Only 1 distinct 4xx/5xx codes documented (plus 0 "default" catch-all responses). Investigated: docs 100%, spec 50%.
- [pass] Operation purpose clarity — 97% of operations have a clear summary + operationId an agent can select on. Investigated: spec 100%.
- [warn] Agent-navigable, token-efficient docs — 5 of 50 pages have substantive content differences between markdown and HTML (avg 4% missing). Investigated: docs 78%.
- [pass] Docs structured data — JSON-LD Article markup on 19/19 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] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Pagination documented & consistent — Pagination params detected on 11 list endpoint(s). Investigated: spec 100%, docs 100%.
- [warn] Sandbox separation — No test-mode flag or sandbox environment is exposed. Investigated: sdk 50%, spec 0%, docs 0%.
- [fail] Idempotency documented — 2% of mutating operations document idempotency. Investigated: spec 0%, docs 0%, sdk 0%.
- [fail] Rate-limit signaling — No rate-limit response headers documented. Investigated: spec 0%, docs 0%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.

## Executive Summary

Scale's API program shows strong foundations in API design and agent discovery, but partners and their AI agents face meaningful friction in two areas: they lack the runnable, verifiable context needed to integrate confidently, and they're missing the operational guardrails — idempotency guidance, rate-limit signaling, and an agent instructions file — that allow agents to operate safely and autonomously. Prioritize making the API executable and operationally reliable first, then layer in the agent-readable context that lets AI agents act on your API without human intervention.