Lish
Lish is a corporate catering and workplace food service company serving Seattle and the Bellevue/Eastside area of Washington, including Redmond and Kirkland. It connects employers with a curated roster of local partner chefs and runs the whole workplace meal program — menu curation, ordering, delivery and setup — across four service lines: subscription catering, PopUp restaurants that employees buy from directly, on-demand one-off catering, and occasion catering for breakfast, lunch, box lunches, happy hours, meetings and events. The company reports more than 3,000,000 meals served, 100+ curated menus from dozens of partner chefs, an average meal rating of 4.6 stars, and 97.8% of orders delivered on time within a 20-minute window, with dietary accommodation (gluten-free, vegetarian, vegan, dairy-free) as a stated focus. Lish describes an admin dashboard, budget tracking, GPS delivery tracking, Google Calendar and Outlook menu visibility and Slack feedback notifications, but these are end-user product integrations — Lish operates no developer program and publishes no product API. The only public, self-describing HTTP API is the WordPress REST API behind its marketing site, profiled here.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Lish the way a machine reads it — 13 machine-readable artifacts across 11 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 — Lish scores 36.0/100 (thin), with a separate agent-readiness read of 39/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 Lish
Each block below is one kind of artifact we hold for Lish. 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 11
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.
Lish Categories API
Category terms used to classify posts.
Lish Comments API
Comments left on Lish posts.
Lish Media API
Media library items (images, attachments).
Lish Pages API
Static marketing pages on the Lish site.
Lish Posts API
Blog posts published on the Lish site.
Lish Search API
Cross-resource search over site content.
Lish Statuses API
Registered post statuses.
Lish Tags API
Tag terms used to classify posts.
Lish Taxonomies API
Registered taxonomies.
Lish Types API
Registered post types.
Lish Users API
Post authors exposed by the site.
Scroll within the panel for all 11 ·
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 Lish — 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.
Get Started 2
Portal, sign-up, and the first successful call
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 5
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 2
Pricing, plans, and the legal terms of use
Company 3
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/lish · machine-readable index on apis.io