Ritual
Ritual is a Toronto-based restaurant order-ahead and "social ordering" platform (ritual.co, founded 2014) that lets consumers pre-order, pay, and skip the line at local restaurants and coffee shops, and lets colleagues pile onto a shared order for group pickup. For restaurants it offers Ritual ONE (online ordering, company/building perk programs, and Ritual for Coffee). Ritual does NOT publish a public or self-serve developer API - there is no developer portal, API reference, SDKs, or authentication documentation. Restaurant order injection into point-of-sale systems is handled through partner/POS integrations (documented on partnersupport.ritual.co) and third-party ordering aggregators such as Deliverect, not through a Ritual-published API. Operating status - Ritual continues to operate the consumer app and online-ordering platform, but the business is distressed and in transition - revenue fell from ~US$11M (2021) to ~US$3.9M (H1 2024) with repeated layoffs, and in January 2025 Shopify "acqui-hired" the co-founders (CEO Ray Reddy became Shopify's VP of Retail/POS) and much of the R&D team while a separate process to sell the standalone Ritual business was underway. This entry is a documentation stub with no APIs modeled because none are publicly documented.
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 Ritual 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 — Ritual scores 11.1/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.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Ritual
Each block below is one kind of artifact we hold for Ritual. 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 Ritual — 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
Access & Security 2
Authentication, authorization, and security posture
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/ritual-ordering · machine-readable index on apis.io