Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Chef Robotics website screenshot

Chef Robotics

Chef Robotics is a San Francisco, California physical-AI company building AI-enabled robots for high-mix food production. Its core product is an NSF-certified food-assembly robot that picks, scoops, and deposits a wide range of ingredients — fresh, cooked, IQF, sauces, leafy greens, mixed vegetables, and discrete piece items — into trays, burritos, wraps, pizza bases, and other containers on conveyor lines. The robots are powered by ChefOS, a proprietary Generalized Food Manipulation Model trained on tens of millions of real-world servings and tens of thousands of hours of production data, combining vision, decision-making, and robot control across a See / Think / Act stack with continuous Fleet Learning. Chef Robotics sells via a Robotics-as-a-Service (RaaS) model that bundles hardware, software updates, 24/7 monitoring, and customer success. Deployed customers include Amy's Kitchen, Sunbasket, Cafe Spice, and Chef Bombay, with the fleet having produced 98+ million servings across the US, Canada, and Europe. The company is venture-backed (Kleiner Perkins, Avataar Ventures-led $43M Series A, Bloomberg Beta, Construct Capital) and serves frozen meals, fresh meals, co-manufacturing, D2C meal delivery, medically tailored meals, meatpacking, airline catering, and foodservice verticals. There is no public developer API, SDK, or open-source release for ChefOS — the platform is operated as a closed, fleet-managed service on Chef-owned hardware deployed inside customer facilities.

human only

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.

Kin Score

API Evangelist profiles Chef Robotics the way a machine reads it — 1 machine-readable artifact, 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 — Chef Robotics scores 8.7/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 Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 8.7/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 1.3 / 20
Commercial Clarity 0.0 / 20
Operational Transparency 0.7 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile Chef Robotics

Each block below is one kind of artifact we hold for Chef Robotics. 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.

Security 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.

Chef Robotics Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Every other property we hold for Chef Robotics — 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

Operate 2

Status, limits, changes, and where to get help

← All providers · Data indexed from github.com/api-evangelist/chef-robotics · machine-readable index on apis.io