Notch
Notch (formerly OrderEZE/ChefHero) brings the restaurant supply chain online, digitizing the paper-driven process of wholesale food ordering and order taking between restaurants and their distributors. Founded in 2015 and headquartered in Toronto, the platform spans four product surfaces — Order Manager and Invoice Manager for buyers, AP Manager for restaurant accounts payable, and AR Manager for distributor accounts receivable — handling order placement, invoice management, reconciliation, payment collection, and payment processing for food and beverage suppliers and buyers. Notch keeps ordering and finance workflows in sync through one-way and two-way connectors to accounting and ERP systems including QuickBooks Online, QuickBooks Desktop, NetSuite, Xero, and Microsoft Dynamics 365, plus CSV import/export. Notch does not publish a public developer API or developer portal; its accounting/ERP connectivity is delivered through its own connectors and the third-party Rutter unified accounting API, so Notch operates as an API consumer rather than an API provider. (This profile covers Notch the restaurant-to-supplier ordering and AR/AP automation company at notch.financial, and is unrelated to "Notch Pay," the African payments company at developer.notchpay.co.)
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 Notch the way a machine reads it — 1 machine-readable artifact, 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 — Notch scores 8.8/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 Notch
Each block below is one kind of artifact we hold for Notch. 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 1
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 Notch — 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.
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 3
The organization behind the API
Other 3
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/notch · machine-readable index on apis.io