AutoCAD
APIs for Autodesk AutoCAD, providing programmatic access to CAD design, drawing, and automation capabilities through Autodesk Platform Services (APS, formerly Forge) and desktop development environments including AutoLISP, ObjectARX, .NET, and JavaScript.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles AutoCAD the way a machine reads it — 36 machine-readable artifacts across 6 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — AutoCAD scores 49.5/100 (developing), with a separate agent-readiness read of 46/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile AutoCAD
Each block below is one kind of artifact we hold for AutoCAD. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 6
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
AutoCAD API
Core API for AutoCAD automation, drawing manipulation, and entity management.
AutoCAD Design Automation API
Cloud-based API that enables running AutoCAD scripts, AutoLISP routines, and custom add-ins in the cloud to automate drawing creation, modification, and batch processing workflo...
AutoCAD Data Management API
API for managing AutoCAD files, versions, and collaboration workflows.
AutoCAD Model Derivative API
API for translating AutoCAD design files into formats like SVF and SVF2 for rendering in the Viewer SDK, extracting metadata, object hierarchy, properties, and generating thumbn...
AutoCAD Webhooks API
API enabling applications to listen for and receive notifications when specific events occur in AutoCAD data and workflows, supporting event-driven architectures.
AutoCAD Authentication API
OAuth 2.0-based authentication API for securing access to AutoCAD and Autodesk Platform Services APIs, supporting both 2-legged and 3-legged authentication workflows.
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
autocad-mcp.yml
MCP SERVERAgent Skills 5
An agent skill packages the how-to for driving these APIs from an assistant — the prompts, the sequence, the guardrails — so the knowledge to use the API travels with it.
Packaged agent skills for driving this provider's APIs from an AI assistant.
acad-arx-wizard
AGENT SKILLacad-cuix-builder
AGENT SKILLacad-dotnet
AGENT SKILLaps-docs-portal
AGENT SKILLaps-mcp-server-gen
AGENT SKILLPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Autocad Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Autocad Finops
FINOPSFeatures 6
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Cloud-Based Design Automation
Run AutoCAD scripts and add-ins in the cloud for batch processing without local AutoCAD installation.
3D Model Translation
Translate CAD files between formats and extract metadata for web-based viewing and analysis.
File Version Management
Manage design file versions, revisions, and collaboration workflows through the Data Management API.
Event-Driven Webhooks
Receive real-time notifications when design files are created, updated, or shared.
OAuth 2.0 Authentication
Secure API access with 2-legged and 3-legged OAuth flows for application and user-level authorization.
Web-Based Viewer
Embed 2D and 3D design viewers in web applications with the Viewer SDK.
Security Posture 4
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Autocad Trust Center
SOC 2, SOC 3, ISO 27001, ISO 27017, ISO 27018, PCI DSS, HIPAA, GDPR, FedRAMP, CSA STAR Level 1
SECURITYScopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Use Cases 5
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Automated Drawing Generation
Generate construction drawings, floor plans, and engineering diagrams automatically using Design Automation API.
Design File Collaboration
Build collaborative design workflows with file sharing, version control, and real-time notifications.
Batch File Processing
Process thousands of CAD files in the cloud for format conversion, data extraction, and quality checks.
BIM Integration
Integrate Building Information Modeling data with enterprise systems for construction project management.
Custom CAD Applications
Build custom AutoCAD plugins and extensions using ObjectARX, .NET, AutoLISP, or JavaScript APIs.
Integrations 5
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Autodesk Construction Cloud
Integration with ACC for construction project management and design coordination.
BIM 360
Cloud-based BIM collaboration platform integration for construction workflows.
Revit
Interoperability with Revit for architectural design and BIM workflows.
Navisworks
Integration for 3D coordination, clash detection, and project review.
Power BI
Data visualization integration for design analytics and project reporting.
Resources
Every other property we hold for AutoCAD — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 7
Authentication, authorization, and security posture
Scroll within the panel for all 7 ·
Operate 5
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/autocad · machine-readable index on apis.io