# You — API Agent Score

> Score: 96/100 (Grade: A+) | Domain: you.com | Rubric: 1.0.0 | Checked: October 22, 2026

You scored 96/100 (A+), classified "ai-ready".

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

## Summary

- Overall: 96/100 (A+)
- Classification: ai-ready

## Category Scores

- API Design: 98/100 (A+)
- Developer Experience: 89/100 (A)
- Agent Discovery: 95/100 (A+)
- Agent Understanding: 96/100 (A+)
- Agent Usability: 100/100 (A+)

## 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%, mcp 100%.
- [warn] Schema coverage & depth — 7 of 151 public signatures use loose types (anyTypeRatio=0.046). Investigated: sdk 91%, spec 87%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, sdk 100%, wellknown 50%.
- [pass] Example coverage — Docs show code samples in 5 language(s) (top: shell, python, typescript), and 6 of 20 sampled pages offer ≥ 2 languages side by side. Investigated: docs 100%, sdk 100%, spec 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://you.com/signin?redirectUrl=%2Fplatform (client-rendered, so its contents couldn't be classified); free tier or sandbox is documented in pricing/docs. Investigated: docs 100%.
- [pass] Quickstart present — Quickstart at https://you.com/docs/quickstart includes a runnable first-call code sample. Investigated: docs 100%.
- [pass] Code samples in docs — Docs show code samples in 5 language(s) (top: shell, python, typescript), and 6 of 20 sampled pages offer ≥ 2 languages side by side. Investigated: docs 100%.
- [pass] Description completeness — 100% of operations and parameters carry substantive descriptions (1 of 1 ops, 0 of 0 params), the main semantic cue an agent relies on. Investigated: spec 100%, sdk 40%.
- [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 (websites/you, 1519 snippets). Investigated: docs 100%, cli 100%, wellknown 100%, sdk 58%, mcp 0%.
- [warn] llms.txt present, valid & comprehensive — llms.txt exists but contains no parseable links. Investigated: docs 80%, sdk 0%.
- [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%, sdk 100%, spec 50%.
- [pass] Operation purpose clarity — 100% of operations (1 of 1) have both a clear summary and a descriptive name, so an agent can pick the right endpoint. Investigated: spec 100%, sdk 63%.
- [pass] Agent-navigable, token-efficient docs — All 1 pages contain server-rendered content. Investigated: docs 100%.
- [pass] Agent instructions file (AGENTS.md) — Agent context file present: agents.md (root). Investigated: sdk 100%, wellknown 0%.
- [warn] Docs structured data — JSON-LD Article markup covers 20 of 20 assessed pages (100%), but no page carries dateModified, so answer engines can't tell how current the docs are. Investigated: docs 50%.
- [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%, spec 0%, docs 0%.
- [pass] Rate-limit signaling — rate-limit behavior is documented on the docs site at https://you.com/signin?redirectUrl=%2Frate-limits, even though it isn't declared in the API spec. Investigated: spec 100%, docs 100%.
- [pass] Pagination documented & consistent — pagination is documented on the docs site at https://you.com/docs/agents/plugins, even though it isn't declared in the API spec. Investigated: docs 100%, spec 50%.
- [pass] Sandbox separation — sandbox is documented on the docs site at https://you.com/docs/integrations/daytona, even though it isn't declared in the API spec. Investigated: spec 100%, docs 100%, sdk 100%.
- [pass] Runnable collection with test scripts — README is present and includes a runnable quickstart. Investigated: sdk 100%, platform 0%.

## Executive Summary

You's API program scores strongly across design, discovery, and agent understanding — partners and their agents can find and build against your API surface with confidence. The one meaningful gap is changelog visibility: without a published record of API changes, partners and the agents they rely on have no way to anticipate breaking changes before they cause failures. Closing this single gap will complete an already strong partner-readiness foundation.