# T Mobile — API Agent Score

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

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

[View full report](https://www.postman.com/ai/ai-ready-apis/company/t-mobile)
[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: 87/100 (A)
- Developer Experience: 40/100 (F)
- Agent Discovery: 65/100 (C)
- Agent Understanding: 67/100 (C)
- Agent Usability: 45/100 (F)

## Check Results

### API Design

- [pass] Schema coverage & depth — package.json "types" → ./dist/react-mobile-picker.d.ts. Investigated: sdk 100%.
- [pass] Example coverage — README is present and includes a runnable quickstart. Investigated: sdk 100%.
- [warn] Security & governance hygiene — security.txt present but missing Contact; missing or expired Expires. Investigated: wellknown 50%.
- [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

- [fail] Self-service developer portal — No signup page detected across conventional paths (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free). Investigated: docs 0%.
- [fail] Quickstart present — No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.
- [fail] Changelog published — Official SDKs stale: newest activity 811 days ago. Investigated: sdk 0%.
- [skip] Code samples in docs — No surface produced evidence for this capability in this run.
- [skip] Description completeness — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Registry & SDK presence — Indexed on Context7 (spruceid/sprucekit-mobile, 58 snippets). Investigated: docs 100%, sdk 33%, cli 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://devedge.t-mobile.com/llms.txt, https://devedge.t-mobile.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 86%.
- [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] Docs structured data — 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

T-Mobile's API Design and Auth posture are strong — partners and agents can trust the security foundation. However, the partner program has critical gaps in two areas that determine whether partners ever get off the ground: there is no self-service onboarding path (no developer portal, no quickstart, no changelog), and agents have none of the machine-readable context they need to discover, understand, or reliably execute against T-Mobile's APIs. Prioritize building a self-service front door with runnable examples first, then layer in agent-specific discoverability and reliability signals so both human partners and AI-driven integrations can succeed without a sales or support conversation.