FANUC
FANUC Corporation is a Japanese multinational headquartered in Oshino, Yamanashi at the base of Mount Fuji, and is one of the world's largest suppliers of factory automation, industrial robots, and CNC (computer numerical control) systems. Founded in 1972 after spinning out of Fujitsu's numerical control division (originated 1955) under Seiuemon Inaba, FANUC pioneered commercial NC and CNC technology and by the early 1980s held roughly half of the global CNC market. The company operates three primary business segments: FA (CNC systems, servo motors, lasers, and PMC controls for machine tools), Robot (industrial arms from the LR Mate and M-series through the heavy-payload M-2000iA, plus the CRX collaborative robot family), and ROBOMACHINE (ROBODRILL machining centers, ROBOCUT wire EDM, and ROBOSHOT all-electric injection molding machines). FANUC's primary developer surface is FOCAS (FANUC Open CNC API Specification), a licensed C/C++ library (fwlib32.dll) used by machine builders and MES/OEE vendors to read CNC state over Ethernet, plus KAREL and Teach Pendant (TP) programming on the robot controllers and a published ROS 2 driver for the CRX collaborative arms. FANUC does not operate a public REST developer portal or publish OpenAPI specifications; integrations are partner-driven through MTConnect adapters, OPC UA servers, FIELD system edge apps, and the FANUC America customer/training portals.
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 FANUC 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 — FANUC 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 FANUC
Each block below is one kind of artifact we hold for FANUC. 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.
Fanuc 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 FANUC — 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 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Learn 2
Tutorials, courses, talks, and written guidance
Operate 1
Status, limits, changes, and where to get help
Company 6
The organization behind the API
Other 14
Properties that don't map to a standard resource type
Scroll within the panel for all 14 ·
← All providers · Data indexed from github.com/api-evangelist/fanuc-robotics · machine-readable index on apis.io