Kitopi
Kitopi is a Dubai-headquartered, tech-powered multi-brand restaurant and cloud kitchen platform that discovers, creates and curates homegrown F&B brands for the MENA region. It operates over 200 restaurant and delivery-only outlets across the UAE, Saudi Arabia, Bahrain, Qatar and Kuwait with more than 6,000 employees, and runs a Global Customer Experience center in Dubai plus a 100-plus person technology hub in Krakow, Poland. Kitopi's differentiator is its in-house Smart Kitchen Operating System (SKOS), a suite of applications that optimizes every aspect of cloud-kitchen operations in real time to maximize throughput and utilization for its restaurant partners, letting a brand scale into a new market in roughly 14 days. Kitopi is a SoftBank Vision Fund portfolio company. It publishes no public product or partner developer API; its only machine-readable surface is a Wix-provided site MCP endpoint and an llms.txt agent-access declaration on www.kitopi.com.
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 Kitopi the way a machine reads it — 4 machine-readable artifacts across 1 API, 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 — Kitopi scores 21.7/100 (emerging), with a separate agent-readiness read of 30/100 (agent aware). 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 Kitopi
Each block below is one kind of artifact we hold for Kitopi. 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.
APIs 1
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Kitopi Site MCP
The Model Context Protocol endpoint that Kitopi's Wix-hosted website exposes for agentic AI access. It is a platform-provided (Wix) site assistant server rather than a Kitopi pr...
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
kitopi-mcp.yml
MCP SERVERSecurity 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 Kitopi — 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
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
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 10
The organization behind the API
Scroll within the panel for all 10 ·
Other 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/kitopi · machine-readable index on apis.io