Coco Robotics
Coco Robotics is a Santa Monica, California urban robotics company operating a fleet of zero-emission, remotely-supervised sidewalk delivery robots ("Cocobots") for last-mile food, grocery and retail delivery. Merchants do not integrate with Coco directly: Coco is consumed as a delivery service provider through Uber Eats, DoorDash, Wolt and Olo Dispatch, and the company publishes no developer portal, API documentation, SDKs or webhooks of its own. Its public software surface is limited to a marketing site, a customer order-tracking web app, and a GitHub organization of forked ROS and infrastructure tooling.
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 Coco 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 — Coco Robotics scores 11.9/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.
Why this profile is thin
Coco has no developer surface at all — the 39-page Framer marketing site 404s on /developers and /api, no docs/developer/api subdomain resolves, and the only API host in its own code (api.cyanbot.com, hard-coded in the track.cocodelivery.com order-tracker bundle) is now NXDOMAIN; merchants reach Coco through Uber Eats, DoorDash, Wolt and Olo Dispatch rather than through a Coco API.
This is an honest zero, not a gap in our research. Coco Robotics does not appear to expose an API, so there is nothing here for us to index and nothing for them to fix.
What we probed
https://www.cocodelivery.com/developers→ HTTP 404https://www.cocodelivery.com/api→ HTTP 404https://www.cocodelivery.com/.well-known/api-catalog→ HTTP 404https://www.cocodelivery.com/llms.txt→ HTTP 404https://api.cyanbot.com/openapi.json→ HTTP 0
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-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from Coco Robotics's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/coco/"
title="Coco Robotics on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/coco.svg"
alt="Coco Robotics Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/coco/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/coco/"
title="Coco Robotics on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/coco/card.svg"
alt="Coco Robotics Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Coco Robotics
Each block below is one kind of artifact we hold for Coco 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.
Resources
Every other property we hold for Coco 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.
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
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 8
The organization behind the API
Scroll within the panel for all 8 ·
← All providers · Data indexed from github.com/api-evangelist/coco · machine-readable index on apis.io
This is an independent, third-party profile of Coco Robotics, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.