KUKA
KUKA AG is a German industrial automation company headquartered in Augsburg, Bavaria, founded in 1898 and majority-owned by China's Midea Group since 2016. KUKA designs and manufactures industrial robots, autonomous mobile robots (AMRs), production cells, controllers, and the software stack that drives them. Its product portfolio spans six-axis articulated robots (KR series), sensitive collaborative robots (LBR iiwa, LBR iisy), mobile platforms (KMR iiwa, KMP), and palletizing/welding/CNC cells, controlled by the KR C4 and KR C5 / KR C5 micro controller generations. The robot software stack centers on KUKA System Software (KSS/VSS) for KR C4-class hardware, the newer iiQKA.OS / iiQKA.OS2 operating system for KR C5, and the KUKA Robot Language (KRL) for motion programming, with extension surfaces including KUKA.RobotSensorInterface (RSI), KUKA.EthernetKRL, KUKA.PLC mxAutomation for external PLC control, KUKA.OPC UA, and KUKA.AppTech / iiQKA App Builder for option packages. Engineering and simulation are delivered through iiQWorks (iiQWorks.Sim, iiQWorks.App Builder, iiQWorks.Copilot) and KUKA.Sim, while operational software includes KUKA Xpert (documentation/cloud), KUKA iiQoT (condition monitoring), and KUKA Connect / my.KUKA customer portals. KUKA does not publish a first-party public REST/OpenAPI developer API or an official GitHub organization for its robot control stack; integration is performed through proprietary protocols (RSI, EthernetKRL, mxAutomation, OPC UA, PROFINET, EtherCAT) and SDKs distributed via the iiQKA Creator portal and KUKA Xpert. A meaningful body of open-source KUKA integration code lives in the community-maintained kroshu GitHub organization (ROS 2 drivers, external-control SDK, URDF robot descriptions) and the roboticsapi / openkuka projects. KUKA serves automotive, electronics, battery, metal, consumer goods, healthcare, aerospace, and e-commerce logistics customers, and through its Swisslog subsidiary extends into warehouse and intralogistics automation.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles KUKA the way a machine reads it — 3 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 — KUKA scores 12.6/100 (minimal), 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 KUKA
Each block below is one kind of artifact we hold for KUKA. 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.
Kuka Robotics Context
JSON-LDSecurity Posture 2
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 KUKA — 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
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 1
Status, limits, changes, and where to get help
Company 7
The organization behind the API
Scroll within the panel for all 7 ·
Other 18
Properties that don't map to a standard resource type
Scroll within the panel for all 18 ·
← All providers · Data indexed from github.com/api-evangelist/kuka-robotics · machine-readable index on apis.io