ItsaCheckmate
ItsaCheckmate (Checkmate) is restaurant middleware that connects point-of-sale systems to delivery marketplaces and ordering channels, providing two-way integration, menu management, and consolidated reporting across 50+ POS systems and 100+ ordering platforms for tens of thousands of restaurant locations. Through its Marketplace for Developers, Checkmate offers a self-service open REST API that lets technology partners build a single integration to read and write menus, orders, and locations across many POS systems. The API uses OAuth-style token authentication with short-lived, scoped access and refresh tokens, ready-to-use Postman collections, and an llms.txt index for AI agents.
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 ItsaCheckmate the way a machine reads it — 56 machine-readable artifacts across 4 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 — ItsaCheckmate scores 59.4/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 ItsaCheckmate
Each block below is one kind of artifact we hold for ItsaCheckmate. 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 4
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.
ItsaCheckmate Locations API
Location activation and location detail retrieval.
ItsaCheckmate Menus API
Menu retrieval per ordering platform.
ItsaCheckmate OAuth API
Token issuance, refresh, and introspection.
ItsaCheckmate Orders API
Standard and group order submission into the POS.
Open Collections 1
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).
ItsaCheckmate Marketplace for Developers 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.
Itsacheckmate 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.
Itsacheckmate Finops
FINOPSSemantic Vocabularies 1
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.
Itsacheckmate 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.
ItsaCheckmate API Rules
SPECTRALItsaCheckmate API Rules
SPECTRALJSON Schema 14
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.
ActivationResult
JSON SCHEMAAddress
JSON SCHEMACustomer
JSON SCHEMALocation
JSON SCHEMAMenuCategory
JSON SCHEMAMenuItem
JSON SCHEMAMenu
JSON SCHEMAOrderConfirmation
JSON SCHEMAOrderItem
JSON SCHEMAOrder
JSON SCHEMAOrderTotals
JSON SCHEMATokenInfo
JSON SCHEMATokenRequest
JSON SCHEMATokenResponse
JSON SCHEMAScroll within the panel for all 14 ·
JSON Structure 14
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.
Marketplace Api Activation Result Structure
JSON STRUCTUREMarketplace Api Address Structure
JSON STRUCTUREMarketplace Api Customer Structure
JSON STRUCTUREMarketplace Api Location Structure
JSON STRUCTUREMarketplace Api Menu Category Structure
JSON STRUCTUREMarketplace Api Menu Item Structure
JSON STRUCTUREMarketplace Api Menu Structure
JSON STRUCTUREMarketplace Api Order Confirmation Structure
JSON STRUCTUREMarketplace Api Order Item Structure
JSON STRUCTUREMarketplace Api Order Structure
JSON STRUCTUREMarketplace Api Order Totals Structure
JSON STRUCTUREMarketplace Api Token Info Structure
JSON STRUCTUREMarketplace Api Token Request Structure
JSON STRUCTUREMarketplace Api Token Response Structure
JSON STRUCTUREScroll within the panel for all 14 ·
Examples 14
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.
Marketplace Api Menu Example
EXAMPLEScroll within the panel for all 14 ·
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 ItsaCheckmate — 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 2
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 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/itsacheckmate · machine-readable index on apis.io