# Unity — API Agent Score

> Score: 53/100 (Grade: D) | Domain: unity.com | Rubric: 1.0.0 | Checked: August 27, 2026

Unity scored 53/100 (D), classified "not-ai-ready".

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

## Summary

- Overall: 53/100 (D)
- Classification: not-ai-ready

## Category Scores

- API Design: 50/100 (D)
- Developer Experience: 50/100 (D)
- Agent Discovery: 96/100 (A+)
- Agent Understanding: 49/100 (F)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [pass] Security & governance hygiene — Code is formatter-clean with zero linter errors and zero style warnings. Investigated: sdk 100%, wellknown 0%.
- [fail] Schema coverage & depth — no .d.ts found. Investigated: sdk 0%.
- [fail] Example coverage — No code samples detected across 20 sampled docs pages, so a coding agent gets no ready-to-use examples. Investigated: docs 0%, sdk 0%.
- [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

- [pass] Changelog published — Newest official SDK activity 0 day(s) ago. Investigated: sdk 100%.
- [warn] Quickstart present — Quickstart page is reachable at https://docs.unity.com/en-us/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] Self-service developer portal — No self-service signup detected — no signup link on the homepage or docs, and no conventional signup path (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free, /join, /create-account, /account/signup, /auth/signup, /users/sign_up) resolved — so an agent can't onboard on its own. Investigated: docs 0%.
- [fail] Code samples in docs — No code samples detected across 20 sampled docs pages, so a coding agent gets no ready-to-use examples. Investigated: docs 0%.
- [skip] Description completeness — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] llms.txt present, valid & comprehensive — A full-corpus llms-full.txt is published at https://docs.unity.com/en-us/llms-full.txt, so agents can ingest all your docs in one fetch. Investigated: docs 100%.
- [pass] Registry & SDK presence — Indexed on Context7 (websites/unity_en-us, 50998 snippets). Investigated: docs 100%, sdk 13%, cli 0%.
- [warn] Crawlable / AEO — Sitemap has 124 entries but no lastmod values, so crawlers can't tell what changed recently. Investigated: wellknown 75%.
- [skip] Docs reachable, not hard auth-gated — No surface produced evidence for this capability in this run.

### Agent Understanding

- [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%.
- [fail] Docs structured data — No JSON-LD or OpenGraph/meta tags found across 3 assessed pages (3 JS-rendered), so answer engines have nothing to cite. Investigated: docs 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] Agent-navigable, token-efficient docs — No surface produced evidence for this capability in this run.
- [skip] Description consistency across surfaces — Only 0 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [fail] Runnable collection with test scripts — No README found. Investigated: sdk 0%, platform 0%.
- [skip] Idempotency documented — No surface produced evidence for this capability in this run.
- [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.
- [skip] Sandbox separation — No surface produced evidence for this capability in this run.

## Executive Summary

Unity's API crawlability is a genuine strength — agents and search engines can reach the surface without friction. However, the partner program has two critical gaps that are limiting real-world adoption: partners and their AI agents encounter raw, untyped endpoints with no code samples, no structured metadata for answer engines to cite, and no runnable examples to build against — making the first integration experience slow and error-prone. Closing the schema, example, and discoverability gaps should be the immediate priority, followed by reducing the friction to a partner's first successful call.