Miso Robotics
Miso Robotics is a Pasadena, California kitchen-automation company that builds AI-powered robotics and restaurant operations software for commercial food service. Its flagship product, Flippy, is an autonomous fry station that uses computer vision and NVIDIA-accelerated motion planning to identify food items, detect doneness and run up to 100 baskets per hour on existing commercial fryers from Frymaster, Henny Penny and Pitco. Miso also ships Zippy (built on the acquired Zignyl platform), a real-time digital shift manager for forecasting, scheduling, task management, incentives and payroll that connects to restaurant point-of-sale systems. Customers include White Castle, Jack in the Box, CaliBurger and Auntie Anne's. Miso publishes no public developer API, no OpenAPI/AsyncAPI contract and no SDKs; its integrations are delivered as private partner connections (Toast, PAR and other POS vendors) arranged through sales, and its public GitHub organization carries ROS/robotics and cloud-infrastructure forks used internally rather than a client-facing API surface.
Miso Robotics is profiled on the APIs.io network. Tagged areas include Company, Robotics, Kitchen Automation, Restaurant, and Food Service.
Miso Robotics’ developer surface includes engineering blog, support, and 17 more developer resources.
Kin Score
Markets this provider is in provisional
The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.
| Market | Position | Depth | Registered MCP server | Declares compatibility |
|---|---|---|---|---|
| ONVIF Video Analytics (video surveillance, edge cameras, computer vision) | undeclared | - | - | - |
Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 1
Portal, sign-up, and the first successful call
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 2
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 7
The organization behind the API
Scroll for all 7
Other 3
Properties that don't map to a standard resource type
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.