Yaskawa / Motoman
Yaskawa Electric Corporation is a Kitakyushu, Japan industrial automation company and the world's largest manufacturer of AC servo motors and motion controllers, with major business segments in motion control (AC servo motors, SERVOPACK amplifiers, machine controllers), AC drives / inverters, industrial robotics (under the Motoman brand), and systems engineering. Yaskawa's Motoman robotics division supplies articulated, SCARA, delta, collaborative, and mini robots used across automotive, EV, semiconductor, electronics, food, biomedical, and logistics manufacturing, alongside its Sigma-X servo family and GA / U1000 industrial AC drives. The company exposes a developer surface through the Yaskawa Motoman Developer Portal at developer.motoman.com and the Yaskawa-Global GitHub organization, including YMConnect (a modern PC-side communication library for C++ 17 and C#), MotoPlus SDK (on-controller C code for deterministic motion, I/O, jobs, and alarms), MotoROS2 (a native ROS 2 / micro-ROS node running on DX200, YRC1000, and YRC1000micro controllers), MotoCom SDK (legacy Windows communication SDK), the Smart Pendant SDK (Java extensions for the Smart Pendant teach interface), and YIP (Yaskawa Innovation Plus) packages and Smart Packager tooling. The catalog is SDK- and protocol-driven rather than HTTP/REST — there are no public OpenAPI specifications, so this profile captures the SDK, ROS, GitHub, and developer-portal surface without generated OpenAPI artifacts.
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 Yaskawa / Motoman the way a machine reads it — 2 machine-readable artifacts, 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 — Yaskawa / Motoman scores 20.0/100 (emerging), with a separate agent-readiness read of 0/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 Yaskawa / Motoman
Each block below is one kind of artifact we hold for Yaskawa / Motoman. 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.
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Yaskawa Robotics Context
JSON-LDSecurity Posture 1
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.
Resources
Every other property we hold for Yaskawa / Motoman — 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 2
Reference material describing how the API behaves
Build 11
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 11 ·
Access & Security 1
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 1
Status, limits, changes, and where to get help
Company 8
The organization behind the API
Scroll within the panel for all 8 ·
Other 6
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/yaskawa-robotics · machine-readable index on apis.io