# SMS — API Agent Score

> Score: 65/100 (Grade: C) | Domain: sms.yoga | Rubric: 1.0.0 | Checked: November 2, 2026

SMS scored 65/100 (C), classified "partially-ready".

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

## Summary

- Overall: 65/100 (C)
- Classification: partially-ready

## Category Scores

- API Design: 93/100 (A+)
- Developer Experience: 56/100 (D)
- Agent Discovery: 87/100 (A)
- Agent Understanding: 67/100 (C)
- Agent Usability: 41/100 (F)

## Check Results

### API Design

- [pass] Machine-readable, versioned contract — The API declares version "1.0.0" and uses url-based versioning, so an agent can pin to a stable contract. Investigated: spec 100%, docs 100%.
- [pass] Auth declared & discoverable — Authentication is required across the API (declared globally or on every operation), so an agent knows credentials are needed. Investigated: spec 100%, docs 100%.
- [warn] Schema coverage & depth — Only 91% of the 23 operations document both request and response schemas (target 95%+), so an agent can't reliably call the rest. Investigated: spec 67%, sdk 0%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, sdk 100%, wellknown 50%.
- [pass] Example coverage — 100% of parameters and responses (57 of 57) include example values, grounding an agent in real payload shapes. Investigated: spec 100%, docs 0%, sdk 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page found at https://sms.yoga/signup, but no free tier or sandbox is documented in docs/pricing, so an agent may hit a paywall. Investigated: docs 100%.
- [warn] Quickstart present — Quickstart page is reachable at https://sms.yoga/docs-api/quickstart (24 variants scanned) but has no runnable code sample in its HTML or .md variant, so there's nothing to copy and run. Investigated: docs 50%.
- [fail] Code samples in docs — No code samples detected across 1 sampled docs pages, so a coding agent gets no ready-to-use examples. Investigated: docs 0%.
- [fail] Description completeness — Only 48% of operations and parameters have descriptions (22 of 23 ops, 0 of 4 params), leaving an agent to guess what most endpoints do. Investigated: spec 0%.
- [fail] Changelog published — No changelog link or mention appears in the spec, so an agent can't tell what changed before something breaks. Investigated: spec 0%, docs 0%.

### 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 (yunpian/sms, 63 snippets). Investigated: docs 100%, sdk 100%, cli 0%, mcp 0%, wellknown 0%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt found at any candidate location (https://sms.yoga/docs-api/llms.txt, https://sms.yoga/llms.txt, https://sms.yoga/docs/llms.txt). Investigated: docs 50%.
- [pass] Crawlable / AEO — robots.txt lets all monitored AI crawlers reach the docs paths. Investigated: wellknown 100%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — Documents 5 distinct 4xx/5xx error response codes, so an agent can branch on specific failures instead of guessing. Investigated: docs 100%, spec 50%.
- [pass] Agent-navigable, token-efficient docs — All 1 pages contain server-rendered content. Investigated: docs 100%.
- [warn] Agent instructions file (AGENTS.md) — No agents.md or skill.md context file found (nice-to-have for agent operation). Investigated: sdk 50%, wellknown 0%.
- [warn] Docs structured data — Only OpenGraph/meta tags across 1 assessed pages — no JSON-LD for AI answer engines to cite. Investigated: docs 50%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (spec, docs) is 1% (threshold 35% for full credit).
- [fail] Operation purpose clarity — Only 43% of operations (10 of 23) have a clear summary plus descriptive name, so an agent must guess purpose from the URL path for most. Investigated: spec 0%.

### Agent Usability

- [warn] Runnable collection with test scripts — No test scripts found in the workspace's public collections, so an agent can't use them to verify API behavior. Investigated: platform 50%, sdk 0%.
- [fail] Idempotency documented — Only 0% of mutating operations (0 of 17) document idempotency, so an agent's retries can create duplicate writes. Investigated: spec 0%, docs 0%.
- [fail] Rate-limit signaling — No rate-limit response headers are documented, so an agent can't tell when it is approaching a limit and will get throttled. Investigated: spec 0%, docs 0%.
- [fail] Sandbox separation — None of the 1 declared server(s) is a sandbox/test host, and no test-key prefixes are documented, so agents can only hit production. Investigated: spec 0%, docs 0%.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Sms (sms.yoga) has a solid API design foundation, but the partner program is being held back by two critical gaps: agents and partners cannot safely or reliably use the API in practice, and the documentation leaves most endpoints undescribed and without examples. The most urgent priorities are establishing a sandbox environment and documenting idempotency and rate-limit behavior so partners can integrate without risking production data, followed by filling in operation descriptions and code samples so partners and their AI agents can understand and use the API without guesswork.