Lunchbox
Lunchbox is a digital ordering and guest engagement platform for enterprise restaurant chains and ghost kitchens, offering online ordering, catering, loyalty, marketing CRM, order aggregation, and call center tooling across thousands of locations. For technology partners, Lunchbox provides an Open API that connects a restaurant's tech stack to its ecosystem, exposing location and menu data, guest account management, and order injection into the POS. The Open API supports last-mile delivery webhooks, menu consumption for digital boards and kiosks, and third-party marketplace integrations, and is documented on a dedicated developer portal at docs.lunchbox.io.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Lunchbox the way a machine reads it — 121 machine-readable artifacts across 6 APIs, 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 — Lunchbox scores 56.9/100 (developing), with a separate agent-readiness read of 48/100 (agent ready). 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 Lunchbox
Each block below is one kind of artifact we hold for Lunchbox. 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 6
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.
Lunchbox Customer API
Guest account registration, authentication, and profile management.
Lunchbox Misc API
Reference data such as contact, countries, and states.
Lunchbox Orders API
Order creation, item management, discounts, payments, and group orders.
Lunchbox Service Types API
Configure store service types.
Lunchbox Stores API
Store configuration, hours, menus, and discounts.
Lunchbox User Wallet API
Create, search, retrieve, update, validate, confirm, refund, and adjust loyalty user wallets.
Open Collections 4
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Lunchbox Core API
OPEN COLLECTIONLunchbox Loyalty API
OPEN COLLECTIONLunchbox Management API
OPEN COLLECTIONLunchbox POS API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Lunchbox Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Lunchbox Finops
FINOPSSemantic Vocabularies 4
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Lunchbox Core Context
JSON-LDLunchbox Loyalty Context
JSON-LDLunchbox Management Context
JSON-LDLunchbox Pos Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Lunchbox API Rules
SPECTRALLunchbox API Rules
SPECTRALJSON Schema 33
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
AddItemsRequest
JSON SCHEMAAddress
JSON SCHEMAAuthSession
JSON SCHEMACharges
JSON SCHEMACustomer
JSON SCHEMALoginRequest
JSON SCHEMAMenuItem
JSON SCHEMAMenu
JSON SCHEMANewOrderRequest
JSON SCHEMAOrderChildItem
JSON SCHEMAOrderItem
JSON SCHEMAOrder
JSON SCHEMARegistrationRequest
JSON SCHEMAStore
JSON SCHEMAUserWalletCreate
JSON SCHEMAUserWallet
JSON SCHEMAUserWalletUpdate
JSON SCHEMAWalletReward
JSON SCHEMAManagedOrderSummary
JSON SCHEMAManagedStore
JSON SCHEMAManagedStoreSummary
JSON SCHEMAOrderPage
JSON SCHEMAServiceTypeConfig
JSON SCHEMAStorePage
JSON SCHEMAOrderUpdateEvent
JSON SCHEMAPosContact
JSON SCHEMAPosHours
JSON SCHEMAPosLocation
JSON SCHEMAPosOrderAck
JSON SCHEMAPosOrderLocation
JSON SCHEMAPosOrder
JSON SCHEMAPosStore
JSON SCHEMAStoreUpdateEvent
JSON SCHEMAScroll within the panel for all 33 ·
JSON Structure 33
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Core Add Items Request Structure
JSON STRUCTURECore Address Structure
JSON STRUCTURECore Auth Session Structure
JSON STRUCTURECore Charges Structure
JSON STRUCTURECore Customer Structure
JSON STRUCTURECore Login Request Structure
JSON STRUCTURECore Menu Item Structure
JSON STRUCTURECore Menu Structure
JSON STRUCTURECore New Order Request Structure
JSON STRUCTURECore Order Child Item Structure
JSON STRUCTURECore Order Item Structure
JSON STRUCTURECore Order Structure
JSON STRUCTURECore Registration Request Structure
JSON STRUCTURECore Store Structure
JSON STRUCTURELoyalty User Wallet Create Structure
JSON STRUCTURELoyalty User Wallet Structure
JSON STRUCTURELoyalty User Wallet Update Structure
JSON STRUCTURELoyalty Wallet Reward Structure
JSON STRUCTUREManagement Managed Order Summary Structure
JSON STRUCTUREManagement Managed Store Structure
JSON STRUCTUREManagement Managed Store Summary Structure
JSON STRUCTUREManagement Order Page Structure
JSON STRUCTUREManagement Service Type Config Structure
JSON STRUCTUREManagement Store Page Structure
JSON STRUCTUREPos Order Update Event Structure
JSON STRUCTUREPos Pos Contact Structure
JSON STRUCTUREPos Pos Hours Structure
JSON STRUCTUREPos Pos Location Structure
JSON STRUCTUREPos Pos Order Ack Structure
JSON STRUCTUREPos Pos Order Location Structure
JSON STRUCTUREPos Pos Order Structure
JSON STRUCTUREPos Pos Store Structure
JSON STRUCTUREPos Store Update Event Structure
JSON STRUCTUREScroll within the panel for all 33 ·
Examples 33
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Core Address Example
EXAMPLECore Auth Session Example
EXAMPLECore Charges Example
EXAMPLECore Customer Example
EXAMPLECore Login Request Example
EXAMPLECore Menu Example
EXAMPLECore Menu Item Example
EXAMPLECore Order Example
EXAMPLECore Order Item Example
EXAMPLECore Store Example
EXAMPLELoyalty User Wallet Example
EXAMPLEPos Pos Contact Example
EXAMPLEPos Pos Hours Example
EXAMPLEPos Pos Location Example
EXAMPLEPos Pos Order Ack Example
EXAMPLEPos Pos Order Example
EXAMPLEPos Pos Store Example
EXAMPLEScroll within the panel for all 33 ·
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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Lunchbox — 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 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/lunchbox · machine-readable index on apis.io