iRobot
iRobot Corporation is a Bedford, Massachusetts consumer robotics company best known for the Roomba robot vacuum and the Braava and Braava jet robot mop product lines. Founded in 1990 by MIT roboticists, iRobot pioneered the home cleaning robot category and has sold tens of millions of units worldwide. Its current portfolio includes the Roomba Max, Roomba Plus, and Roomba 100/200 series vacuums and combo (vacuum + mop) models, along with AutoWash and AutoEmpty docks, the iRobot Home App for scheduling and mapping, and a cleaning accessories and trade-in program. The proposed acquisition by Amazon was abandoned in January 2024 after regulatory pushback from the European Commission, after which iRobot underwent a major restructuring and layoffs. iRobot's revenue model is direct robot and accessory sales plus recurring consumables; it does not publish a public developer API, SDK, or OpenAPI specification, and its homesupport documentation explicitly notes that Wi-Fi connected Roombas do not have an open API. A community of unofficial reverse-engineered libraries (dorita980, rest980, pyirobot) exists but is not endorsed by iRobot.
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 iRobot 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 — iRobot 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.
How we profile iRobot
Each block below is one kind of artifact we hold for iRobot. 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.
Resources
Every other property we hold for iRobot — 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.
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 1
Tutorials, courses, talks, and written guidance
Operate 1
Status, limits, changes, and where to get help
Company 8
The organization behind the API
Scroll within the panel for all 8 ·
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/irobot · machine-readable index on apis.io