# Autodesk Platform Services vs nTop (slim)

> Autodesk Platform Services scores 44.3 (E) to nTop's 40.2 (E) for cad generate. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/autodesk-platform-services-vs-ntop.md (~4,250 tokens) · this version ~2,730 tokens · JSON https://www.anchorterminal.com/compare/autodesk-platform-services-vs-ntop.json · canonical https://www.anchorterminal.com/compare/autodesk-platform-services-vs-ntop
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-03
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Autodesk Platform Services scores 44.3 (E) on agent readiness against nTop's 40.2 (E), and leads in 3 of 7 scored categories. nTop leads on agent ergonomics and transparency & trust. Both do cad generate.

- Autodesk Platform Services: E 44.3, rank #1154 of 1349 · https://www.anchorterminal.com/tools/autodesk-platform-services.min.md
- nTop: E 40.2, rank #1214 of 1349 · https://www.anchorterminal.com/tools/ntop.min.md
- Autodesk Platform Services, good for Agents that must process existing Autodesk files (Inventor, Revit, AutoCAD, Fusion) at scale with add-ins a team already has, or translate models for viewing. Ahead on Reliability, 52 against 38; Security & auth, 47 against 26; Maintenance & community, 53 against 45.
- nTop, good for An engineering team that already runs nTop and wants an agent to drive design-of-experiments loops over a notebook or read exported implicit bodies in Python. Ahead on Agent ergonomics, 60 against 52; Transparency & trust, 51 against 34. Also A hosted endpoint, with nothing to install.

| Category | Autodesk Platform Services | nTop |
| --- | --- | --- |
| Reliability (16%) | 52 | 38 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 59 | 61 |
| Agent ergonomics (13%) | 52 | 60 |
| Security & auth (14%) | 47 | 26 |
| Payments & pricing (10%) | 0 | 0 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 53 | 45 |
| Transparency & trust (7%) | 34 | 51 |

| Fact (where they differ) | Autodesk Platform Services | nTop |
| --- | --- | --- |
| Kind | HTTP API | SDK + MCP |
| Vendor | Autodesk | nTopology Inc. |
| Hosted endpoint | no (local only) | `https://docs.ntop.com/mcp` |
| Transports |  | Streamable HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Pay per use | Paid |
| Tools exposed | 0 | 2 |
| Last release | 2026-09-16 | none |
| Terms last updated | no document linked | 2026-02-01 |
| Privacy policy last updated | no document linked | 2026-02-01 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | yes |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | yes |

Why the edge:
- Security & auth, Autodesk Platform Services +21: Autodesk Platform Services 47 (OAuth 2.0 with client credentials and authorisation code flows and named scopes (data:read, data:write, data:create, bucket scopes, code:all) in the published Authentication v2 spec, plus Secure Service Accounts for server workloads (30). Read-only scopes exist; no confirmation step before destructive calls was found (12 of 20). The engines execute add-ins and scripts on uploaded design files, and no prompt-injection guidance for agents was found on the pages read (5 of 15). No audit log or per-call visibility was found on the pages read (0 of 15). Autodesk's trust and security pages are on www.autodesk.com, unread, and aps.autodesk.com/.well-known/security.txt answered 406, and no disclosure policy, bug bounty or certification was established from the pages read (0 of 20). 30 + 12 + 5 + 0 + 0 = 47.); nTop 26 (Licence credentials rather than tokens, since ntopcl signs in with a username and password on the command line or a FlexNet server address, with no scoped, revocable or expiring key (8 of 30). The Run Command block has Prompt per File, Prompt per Block and Disallow All settings, which is the only approval control found; the docs MCP server is read-only (10 of 20). The docs server returns nTop's own documentation and ntopcl returns geometry, so little untrusted content reaches the model; no guidance was found (8 of 15). No audit log or per-call record found (0 of 15). No security.txt (404), disclosure policy, bug bounty, certification or advisories found on ntop.com or docs.ntop.com (0 of 20). 8 + 10 + 8 + 0 + 0 = 26.)
- Transparency & trust, nTop +17: Autodesk Platform Services 34 (Closed service. The APS terms of service are on www.autodesk.com and were not read, so terms clarity scores as absent (5 of 30). Privacy policy, data processing and retention statements are on the same host and unread (0 of 30). No deprecation policy or dated notices were readable; the docs pages that would carry them rendered empty (0 of 20). The status page names regional variants for the data APIs, which is the only location disclosure read; no subprocessor list was read (5 of 20). 5 + 0 + 0 + 5 = 10. These scores reflect what our reader could load, not a finding that the documents don't exist.); nTop 51 (Closed software under an EULA last updated February 2026 that names nTopology Inc. and New York law (15). The privacy policy of February 2026 names the controller and US hosting, keeps data as long as needed with no periods, names no subprocessors, and the EULA says usage data is collected to run and improve the products; the statements agree but say little (12 of 30). No deprecation policy; the Core package says only that breaking changes may occur (4 of 20). The EULA discloses usage data collection and the licensing page says the desktop connects to the cloud for analytics, with no opt-out found (6 of 20). 15 + 12 + 4 + 6 = 37.)
- Reliability, Autodesk Platform Services +14: Autodesk Platform Services 52 (Read with the hosted lines. health.autodesk.com is an Atlassian Statuspage listing APS components (Automation API, Model Derivative, Data Management, Developer Portal, Webhooks and the data model APIs) with history feeds (20). The history page didn't render for our reader; the RSS feed holds 20 items from 22 October to 2 November 2026, none naming an APS component, so most of the 90-day window is unread (15 of 30). Rate limits and quotas are documented on pages under /en/docs that rendered as empty shells, so no number was read (0). The OSS spec documents 429 with an instruction to wait and lengthen the wait on each attempt; no Retry-After header or idempotency guidance was found (7 of 15). No SLA found on the pages read (0). The Automation API is a released product with no beta label on its overview (10). 20 + 15 + 0 + 7 + 0 + 10 = 52.); nTop 38 (Read with the local-software lines, since ntopcl and the Core package run on the owner's machine. ntopcl ships inside the nTop Windows installer and the Core package states Python 3.10 or later on Windows and Linux, but both come from app.ntop.com behind a login, not a public package index (12 of 20). No public CI or test suite (0). No public issue tracker; the knowledge base has articles on debugging Automate errors and the 6.3 notes record ntopcl rejecting duplicate input names, which is all the crash record we could read (8 of 25). Release notes per version call out behaviour changes such as unique block names in 6.3, and the Core package warns that breaking changes may land between any two versions, with no semver statement (8 of 15). nTop 6.x is a released product; nTop Core is beta (10 of 15). 12 + 0 + 8 + 8 + 10 = 38.)
- Agent ergonomics, nTop +8: Autodesk Platform Services 52 (Data Management lists support filter and page parameters and Model Derivative returns per-object properties, so responses can be narrowed on the APIs with specs; the Automation API's job outputs are files (15 of 25). Pagination and filtering on the data APIs (15 of 20). Error responses are typed in the specs with reasons and the OSS spec explains 429, though the Automation API's error catalogue was unread (12 of 20). No idempotency key or safe-retry guidance was found; WorkItems are submitted and polled (0 of 20). Official SDKs in TypeScript (npm) and .NET (NuGet), but a Design Automation job needs an AppBundle, an Activity and a WorkItem and the add-in compiled against the desktop product (10 of 15). 15 + 15 + 12 + 0 + 10 = 52.); nTop 60 (A command line with one notebook and two JSON files, a Python package with one class, and a docs MCP server with two tools, so almost nothing to load before work starts (20 of 25). Outputs are files whose size follows the notebook, mesh and voxel outputs are sized by feature_size and spacing, and the docs server caps each answer at 30 KB with rg and head for narrowing (12 of 20). Core raises builtin exceptions with messages; ntopcl's errors are described in knowledge-base articles rather than a reference (10 of 20). Running a notebook again with the same inputs produces the same outputs, and the SAVE flag controls whether inputs are written back; no annotations on the docs tools were published (10 of 20). The three-function ntopcl.py helper keeps defaults few, but every run needs a licence argument or signed-in session and only Python is covered (8 of 15). 20 + 12 + 10 + 10 + 8 = 60.)
- Maintenance & community, Autodesk Platform Services +8: Autodesk Platform Services 53 (Read for a closed service with open SDK sources. The aps-sdk-openapi repository's last commit is 16 September 2026 (Data Management spec), with Model Derivative on 12 August (20 of 30). Two dated spec changes in the last 90 days; SDK package release dates on npm and NuGet were not read (10 of 20). Stack Overflow tags, a fortnightly expert call, a bookable onboarding call and paid ADN support; GitHub issue response was not read because the API refused us (10 of 25). No APS server in the official MCP registry was looked for because the Autodesk MCP servers page could not be read; official SDKs on npm and NuGet are current per the README badges (10 of 15). SDK CI and dependency health unread (3 of 10). 20 + 10 + 10 + 10 + 3 = 53.); nTop 45 (Read for closed software with a docs site. The newest release notes are for nTop 6.3, undated; the docs sitemap last modified the 6.1 page on 21 September 2026 and the Core package page on 19 October 2026, so a change within 90 days is likely but no release date was read (20 of 30). Four versions (6.0 to 6.3) are documented and the 6.0 and 6.1 pages changed in September, but without dates we can't count three releases in 90 days (12 of 20). support@ntop.com, a community site that renders only a loading screen, and a feedback tool on the docs server; no public issues or reply times (8 of 25). No entry in the official MCP registry for the docs server, and the only SDK is a beta Python package behind a login (5 of 15). No CI, package index or dependency data to read (0 of 10). 20 + 12 + 8 + 5 + 0 = 45.)