Apptronik
Apptronik is an Austin, Texas-based humanoid robotics company founded in 2016 as a spinout from the Human Centered Robotics Lab at the University of Texas at Austin. Co-founded by Jeff Cardenas (CEO), Dr. Nick Paine (CTO), and Dr. Luis Sentis (scientific advisor), the company designs and manufactures Apollo, a general-purpose humanoid robot standing 5'8", weighing 160 lbs, capable of lifting 55 lbs, and running for roughly 4 hours on a swappable battery. Apollo targets warehouse, manufacturing, and logistics applications including trailer unloading, case picking, palletization, machine tending, and workcell delivery. Apptronik has commercial pilot programs and partnerships with Mercedes-Benz (automotive manufacturing logistics), GXO Logistics (multi-phase R&D in U.S. distribution centers), Jabil (supply-chain partner helping scale production and an internal Apollo deployment), and Google DeepMind (Apollo integrates Gemini Robotics vision-language-action models). The company previously built NASA's Valkyrie humanoid and ten-plus other research robots. As of February 2026 Apptronik had raised more than $935M (including a $520M Series A-X extension) at a reported $5B valuation, with investors including B Capital, Google, and Mercedes-Benz. The company sells/leases Apollo to enterprise customers via a direct contact-sales motion and ships a proprietary "point-and-click" control suite for deploying solutions; there is no public developer portal, no published REST/AsyncAPI/gRPC API, no public SDK, no open-source release, and no public GitHub repositories under the `apptronik` org.
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 Apptronik 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 — Apptronik scores 11.2/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 Apptronik
Each block below is one kind of artifact we hold for Apptronik. 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.
Apptronik 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 Apptronik — 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.
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 2
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/apptronik · machine-readable index on apis.io