# Ubiquiti — API Agent Score

> Score: 70/100 (Grade: B) | Domain: ubiquiti.com | Rubric: 1.0.0 | Checked: August 19, 2026

Ubiquiti scored 70/100 (B), classified "partially-ready".

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

## Summary

- Overall: 70/100 (B)
- Classification: partially-ready

## Category Scores

- API Design: 83/100 (A)
- Developer Experience: 55/100 (D)
- Agent Discovery: 85/100 (A)
- Agent Understanding: 75/100 (B)
- Agent Usability: 53/100 (D)

## 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%.
- [warn] Schema coverage & depth — Only 63% of the 8 operations document request and response schemas, so an agent can't do function-calling against most endpoints. Investigated: spec 72%.
- [pass] Security & governance hygiene — No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.
- [warn] Auth declared & discoverable — The spec declares no authentication scheme, so an agent can't tell how to authenticate a request. Investigated: docs 50%, spec 25%.
- [pass] Example coverage — Only 28% of parameters and responses (52 of 189) include example values, so an agent has little grounding in real payload shapes. Investigated: spec 100%, docs 0%.

### Developer Experience

- [pass] Quickstart present — Quickstart at https://developer.ui.com/mobility/v1.0.0/getting-started includes a runnable first-call code sample. Investigated: docs 100%.
- [pass] Description completeness — Only 43% of operations and parameters have descriptions (63 of 73 ops, 0 of 178 params), leaving an agent to guess what most endpoints do. Investigated: spec 100%.
- [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%.
- [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] Registry & SDK presence — Indexed on Context7 (websites/help_ui_hc_en-us, 219 snippets). Investigated: docs 100%, sdk 0%, cli 0%.
- [warn] Docs reachable, not hard auth-gated — Server ignores Accept: text/markdown header (0/1 pages return markdown). Investigated: docs 75%.
- [warn] llms.txt present, valid & comprehensive — No llms.txt directive found in HTML of any of 1 pages. Investigated: docs 69%.
- [pass] Crawlable / AEO — No robots.txt on the docs host, so AI crawlers are unrestricted and can read the docs. Investigated: wellknown 100%.

### Agent Understanding

- [pass] Machine-readable errors (RFC 9457) — error codes is documented on the docs site at https://developer.ui.com/network/v10.4.57/error-handling, even though it isn't declared in the API spec. Investigated: docs 100%, spec 50%.
- [warn] Operation purpose clarity — Only 0% of operations (0 of 74) have a clear summary plus descriptive name, so an agent must guess purpose from the URL path for most. Investigated: spec 67%.
- [warn] Agent-navigable, token-efficient docs — No pages support .md URLs (0/1 tested). Investigated: docs 75%.
- [warn] Docs structured data — Only OpenGraph/meta tags across 19 assessed pages — no JSON-LD for AI answer engines to cite. Investigated: docs 50%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/, so coding agents have no ready-made setup and usage instructions. Investigated: wellknown 0%.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Rate-limit signaling — rate-limit behavior is documented on the docs site at https://developer.ui.com/usage/api/rate-limits, even though it isn't declared in the API spec. Investigated: spec 100%, docs 100%.
- [warn] Pagination documented & consistent — The 17 list endpoint(s) expose no pagination parameters, forcing an agent into all-or-nothing reads. Investigated: spec 50%, docs 50%.
- [warn] Idempotency documented — Only 0% of mutating operations (0 of 36) document idempotency, so an agent's retries can create duplicate writes. Investigated: spec 10%, docs 10%.
- [fail] Sandbox separation — None of the 2 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%.
- [fail] Runnable collection with test scripts — No public Postman workspace found for the org, so there's no runnable collection an agent can execute against. Investigated: platform 0%.

## Executive Summary

Ubiquiti's API program shows genuine strength in API design, auth security, and agent discoverability — partners and their agents can find and trust the contract. However, the program has two critical gaps that block partners from safely and quickly getting to value: there is no sandbox environment, no runnable collection, and no self-service onboarding path, meaning every new partner must touch production before writing a single line of integration code. Equally urgent, there is no changelog, no code samples, and no agent instructions file, leaving both human developers and AI coding agents without the context they need to build confidently. Prioritize safe, self-serve onboarding first, then close the documentation and agent-context gaps to unlock partner-program scale.