# World — API Agent Score

> Score: 85/100 (Grade: A) | Domain: world.org | Rubric: 1.0.0 | Checked: November 12, 2026

World scored 85/100 (A), classified "ai-ready".

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

## Summary

- Overall: 85/100 (A)
- Classification: ai-ready

## Category Scores

- API Design: 98/100 (A+)
- Developer Experience: 89/100 (A)
- Agent Discovery: 99/100 (A+)
- Agent Understanding: 76/100 (B)
- Agent Usability: 70/100 (B)

## Check Results

### API Design

- [pass] Schema coverage & depth — .d.ts present on disk but not declared in package.json. Investigated: sdk 100%, spec 72%.
- [pass] Auth declared & discoverable — authentication is documented on the docs site at https://docs.world.org/mini-apps/commands/wallet-auth, even though it isn't declared in the API spec. Investigated: spec 100%, docs 100%, cli 50%.
- [warn] Machine-readable, versioned contract — The API sets a version ("0.1.4") but exposes no versioning scheme in the URL, a header, or the media type, so an agent can't pin to a specific version. Investigated: spec 92%, docs 83%, cli 25%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, sdk 100%, wellknown 100%.
- [pass] Example coverage — Only 0% of parameters and responses (0 of 29) include example values, so an agent has little grounding in real payload shapes. Investigated: spec 100%, docs 100%, sdk 50%, cli 0%.

### Developer Experience

- [pass] Self-service developer portal — Signup page found at https://join.world.org/index, but no free tier or sandbox is documented in docs/pricing, so an agent may hit a paywall. Investigated: docs 100%.
- [pass] Quickstart present — Quickstart at https://docs.world.org/mini-apps/quick-start/installing includes a runnable first-call code sample. Investigated: docs 100%.
- [pass] Code samples in docs — Docs show code samples in 4 language(s) (top: typescript, shell, javascript), and 3 of 20 sampled pages offer ≥ 2 languages side by side. Investigated: docs 100%.
- [pass] Description completeness — Only 36% of operations and parameters have descriptions (34 of 47 ops, 0 of 5 params), leaving an agent to guess what most endpoints do. Investigated: spec 100%.
- [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 50 sampled pages are publicly accessible. Investigated: docs 100%.
- [warn] llms.txt present, valid & comprehensive — llms.txt contains parseable links but doesn't fully follow the proposed structure: https://docs.world.org/llms.txt: No blockquote summary found. Investigated: docs 97%, sdk 0%.
- [pass] Registry & SDK presence — Indexed on Context7 (llmstxt/world_llms-full_txt, 4861 snippets). Investigated: docs 100%, sdk 50%, wellknown 50%, cli 0%, mcp 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) — error codes is documented on the docs site at https://docs.world.org/world-id/idkit/error-codes, even though it isn't declared in the API spec. Investigated: docs 100%, spec 50%, cli 0%.
- [warn] Agent-navigable, token-efficient docs — 3 of 49 pages have substantive content differences between markdown and HTML (avg 3% missing). Investigated: docs 99%.
- [warn] Operation purpose clarity — Only 0% of operations (0 of 12) have a clear summary plus descriptive name, so an agent must guess purpose from the URL path for most. Investigated: spec 33%.
- [pass] Docs structured data — Machine-readable JSON-LD Article markup on 20 of 20 assessed pages (100%), with dateModified present. 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%, cli 0%, wellknown 0%.
- [warn] Description consistency across surfaces — Mean pairwise description similarity across 2 surfaces (spec, docs) is 1% (threshold 35% for full credit).

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%, spec 0%, docs 0%, cli 0%.
- [pass] Sandbox separation — sandbox is documented on the docs site at https://docs.world.org/world-id/sandbox/what-is-sandbox, even though it isn't declared in the API spec. Investigated: spec 100%, docs 100%, sdk 100%.
- [warn] Pagination documented & consistent — The 1 list endpoint(s) expose no pagination parameters, forcing an agent into all-or-nothing reads. Investigated: docs 50%, spec 38%.
- [warn] Runnable collection with test scripts — README is present but has no runnable quickstart. Investigated: sdk 50%, platform 50%.
- [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%.

## Executive Summary

World's API program shows strong fundamentals in contract quality and documentation discovery, but two gaps are creating real friction for partners and their AI agents: the absence of a published changelog leaves partners flying blind through API changes, and undocumented rate-limit signaling means agents will hit throttling walls without warning. Closing these two gaps — changelog visibility and rate-limit transparency — should be the immediate priority to protect partner integrations and enable reliable automated workflows.