Choco
Choco is an AI-powered digital ordering platform that simplifies how restaurants order from their food suppliers and distributors. Serving tens of thousands of distributors and over one hundred thousand buyers across the US, UK, Europe, and the GCC, Choco lets restaurateurs place orders and chat with all their suppliers in one app while converting orders into a supplier's preferred format (email, WhatsApp, text, fax, or direct ERP integration). Choco connects to supplier ERP systems such as Entree, NetSuite, QuickBooks, Microsoft Dynamics, Target Data System, NCR, Sage, and Odoo, and uses AI — including OrderAgent for multimodal order capture and VoiceAgent built on OpenAI's Realtime API — to turn emails, texts, images, and documents into structured, ERP-ready orders. Choco does not publish a public developer API; integration is delivered through managed ERP connections, and its public GitHub organization (chocoapp) hosts only internal data-engineering and infrastructure tooling rather than client SDKs or API specifications.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Choco the way a machine reads it — 2 machine-readable artifacts, 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 — Choco scores 17.2/100 (emerging), 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
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Choco
Each block below is one kind of artifact we hold for Choco. 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 2
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 Choco — 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.
Get Started 1
Portal, sign-up, and the first successful call
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
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 3
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/choco · machine-readable index on apis.io