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.

Chef Robotics is profiled on the APIs.io network. Tagged areas include Robotics, Food Robotics, Food Manufacturing, Meal Assembly, and Physical AI.

Chef Robotics’ developer surface includes engineering blog, GitHub presence, support, and 14 more developer resources.

🌐 Visit website 📡 Source on GitHub

7.1/100 minimal ▬ flat Agent 0/100 human only Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0

0 APIs

RoboticsFood RoboticsFood ManufacturingMeal AssemblyPhysical AI Embodied AI Vision Language Action Foundation ModelsChefOSRobotics as a Service Manipulation Manufacturing Automation Hardware

Kin Score

Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0

Composite quality — 7.1/100 · minimal

Contract Quality 0.0 / 25

Developer Ergonomics 1.4 / 20

Access Clarity 0.0 / 20

Operational Transparency 0.7 / 13

Contract Governance 0.0 / 12

Discoverability 5.0 / 10

Agent readiness — 0/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

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

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/chef-robotics: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Chef Robotics Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Build 1

SDKs, sample code, and the tooling you integrate with

GitHub

GitHub

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

Contact

Contact

Support

Support

Company 6

The organization behind the API

Website

Blog

Careers

Twitter

LinkedIn

Press

Press

Other 7

Properties that don't map to a standard resource type

ArtificialIntelligence

ArtificialIntelligence

Industries

CaseStudies

CustomerImpact

Company

Resources

Sales

Scroll for all 7

Source (apis.yml)

aid: chef-robotics
name: Chef Robotics
description: 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.
type: Index
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - none
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source: []
  generated: '2026-07-22'
  method: derived
position: Producing
access: 3rd-Party
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/chef-robotics.png
tags:
- Robotics
- Food Robotics
- Food Manufacturing
- Meal Assembly
- Physical AI
- Embodied AI
- Vision Language Action
- Foundation Models
- ChefOS
- Robotics as a Service
- Manipulation
- Manufacturing Automation
- Hardware
tags_raw:
- Robotics
- Food Robotics
- Food Manufacturing
- Meal Assembly
- Physical AI
- Embodied AI
- Vision Language Action
- Foundation Models
- ChefOS
- Robotics As A Service
- Manipulation
- Manufacturing Automation
- Hardware
url: https://raw.githubusercontent.com/api-evangelist/chef-robotics/refs/heads/main/apis.yml
created: '2026-05-24'
modified: '2026-05-24'
specificationVersion: '0.23'
apis: []
common:
- type: DomainSecurity
  url: security/chef-robotics-domain-security.yml
- type: Website
  url: https://www.chefrobotics.ai
- type: ArtificialIntelligence
  url: https://www.chefrobotics.ai/artificial-intelligence
- type: Solutions
  url: https://www.chefrobotics.ai/solutions
- type: Industries
  url: https://www.chefrobotics.ai/industries
- type: CaseStudies
  url: https://www.chefrobotics.ai/case-studies
- type: CustomerImpact
  url: https://www.chefrobotics.ai/customer-impact
- type: Company
  url: https://www.chefrobotics.ai/company
- type: Resources
  url: https://www.chefrobotics.ai/resources
- type: Blog
  url: https://www.chefrobotics.ai/blog
- type: Careers
  url: https://www.chefrobotics.ai/careers
- type: Contact
  url: https://www.chefrobotics.ai/contact
- type: GitHub
  url: https://github.com/chef-robotics
- type: Twitter
  url: https://twitter.com/chefrobotics
- type: LinkedIn
  url: https://www.linkedin.com/company/chef-robotics
- type: Support
  url: mailto:support@chefrobotics.ai
- type: Sales
  url: mailto:sales@chefrobotics.ai
- type: Press
  url: mailto:press@chefrobotics.ai
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/chef-robotics"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/chef-robotics/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/chef-robotics/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.