Maya
A collection of APIs for Maya, the popular 3D animation and modeling software developed by Autodesk, providing scripting and plugin development capabilities through Python, C++, MEL, and .NET interfaces.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Maya the way a machine reads it — 12 machine-readable artifacts across 9 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 — Maya scores 19.5/100 (emerging), with a separate agent-readiness read of 7/100 (human only). 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 Maya
Each block below is one kind of artifact we hold for Maya. 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 9
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.
Maya Python API 2.0
Modern Python API for Maya scripting and plugin development, offering improved performance and a more Pythonic interface compared to API 1.0.
Maya Python API 1.0
Original Python wrapper for the Maya C++ API providing access to OpenMaya, OpenMayaUI, OpenMayaAnim, OpenMayaFX, OpenMayaRender, and OpenMayaCloth modules.
Maya C++ API
C++ API for high-performance Maya plugin development, providing low-level access to Maya internals through OpenMaya, OpenMayaUI, OpenMayaAnim, OpenMayaFX, and OpenMayaRender lib...
Maya Commands (MEL)
Maya Embedded Language command API for scripting and automating tasks within Maya using the built-in MEL interpreter.
Maya Commands (Python)
Python command interface (maya.cmds) providing access to all MEL commands through Python, enabling scripting and automation with Python syntax.
Maya USD API
Universal Scene Description integration API for Maya, enabling USD stage loading, editing, and interchange within the Maya viewport.
Maya Batch Rendering API
API for batch rendering and render farm integration, enabling automated rendering workflows and pipeline integration.
Maya Hydra API
Maya plugin API that replaces the main Maya viewport with a Hydra viewer, enabling custom render delegate integration for viewport rendering.
Autodesk Platform Services - Maya API
Cloud-based API for Maya through Autodesk Platform Services (APS), providing web service integration, OAuth authentication, and cloud workflow capabilities for Maya development.
Scroll within the panel for all 9 ·
Pricing 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.
Maya Plans Pricing
PLANSRate 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.
Maya 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.
Maya Finops
FINOPSResources
Every other property we hold for Maya — 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 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Build 4
SDKs, sample code, and the tooling you integrate with
Learn 1
Tutorials, courses, talks, and written guidance
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/maya · machine-readable index on apis.io