# Autodesk — API Agent Score

> Score: 83/100 (Grade: A) | Domain: autodesk.com | Rubric: 1.0.0 | Checked: November 3, 2026

Autodesk scored 83/100 (A), classified "ai-ready".

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

## Summary

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

## Category Scores

- API Design: 94/100 (A+)
- Developer Experience: 55/100 (D)
- Agent Discovery: 93/100 (A+)
- Agent Understanding: 88/100 (A)
- Agent Usability: 81/100 (A)

## Check Results

### API Design

- [pass] Machine-readable, versioned contract — The API declares version "1.0" and uses url-based versioning, so an agent can pin to a stable contract. Investigated: spec 100%, docs 100%.
- [pass] Schema coverage & depth — 9/9 (100%) public params are fully typed (no any/**kwargs). Analyzer confirms all methods have a derivable input schema. Investigated: sdk 100%, spec 62%.
- [warn] Auth declared & discoverable — The spec declares no authentication scheme, so an agent can't tell how to authenticate a request. Investigated: spec 75%, docs 75%, wellknown 0%.
- [pass] Security & governance hygiene — Code is formatter-clean with zero linter errors and zero style warnings. Investigated: sdk 100%, spec 80%, wellknown 0%.
- [pass] Example coverage — Only 25% of parameters and responses (65 of 263) include example values, so an agent has little grounding in real payload shapes. Investigated: spec 100%, sdk 100%, docs 0%.

### Developer Experience

- [pass] Quickstart present — Quickstart at https://get-started.aps.autodesk.com/ includes a runnable first-call code sample. Investigated: docs 100%.
- [pass] Description completeness — Only 23% of operations and parameters have descriptions (12 of 36 ops, 23 of 181 params), leaving an agent to guess what most endpoints do. Investigated: spec 100%, sdk 95%.
- [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 1 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] Docs reachable, not hard auth-gated — All 1 pages are publicly accessible. Investigated: docs 100%.
- [pass] Registry & SDK presence — Indexed on Context7 (websites/help_autodesk_view_vredproducts_2027_enu, 9164 snippets). Investigated: docs 100%, sdk 92%, cli 0%.
- [warn] llms.txt present, valid & comprehensive — llms.txt covers 0/1 sitemap doc pages (0%); 1 missing — Missing: https://aps.autodesk.com/developer/documentation. Investigated: docs 75%, 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) — No error responses (4xx/5xx or a catch-all default) are documented anywhere in the spec, so an agent can't anticipate or handle failures. Investigated: docs 100%, sdk 100%, spec 50%.
- [pass] Operation purpose clarity — Surface uses a single dominant casing convention (camelCase). Investigated: sdk 100%, spec 90%.
- [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%.
- [fail] Docs structured data — No JSON-LD or OpenGraph/meta tags found across 1 assessed pages (1 JS-rendered), so answer engines have nothing to cite. Investigated: docs 0%.
- [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] Pagination documented & consistent — 6/6 list method(s) return an auto-paginating iterable. Investigated: sdk 100%, docs 67%, spec 58%.
- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%, spec 0%, docs 0%.
- [pass] Runnable collection with test scripts — README is present and includes a runnable quickstart. Investigated: sdk 100%, platform 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%.

## Executive Summary

Autodesk's API program shows strong foundations in API design, discovery, and agent usability, but two areas represent meaningful friction for partners and their AI agents: Developer Experience is the clearest gap, with no self-service onboarding path, no code samples, and no published changelog — meaning partners can't get started independently or trust that their integrations won't break silently. Agent Understanding also needs attention, as the absence of structured metadata in docs prevents answer engines and AI agents from accurately surfacing and citing Autodesk's APIs. Prioritizing onboarding self-sufficiency and machine-readable documentation will unlock partner velocity and agent-led discovery at scale.