Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Lanch website screenshot

Lanch

LANCH GmbH is a Berlin-based food-tech startup that builds creator-led virtual restaurant brands for the delivery market. Founded by Nono Konopka and Jonas Meynert and headquartered at Schoenhauser Allee 180 in Berlin, LANCH develops food brands together with German influencers, musicians and athletes, then scales them through franchise partners and ghost-kitchen partners operating out of existing restaurant kitchens. Its two flagship brands are Loco Chicken (halal-certified wings, filets, burgers and chicken-and-waffle creations) and Happy Slice (hand-pulled pinsa-dough pizza, dips and cookies), both distributed through delivery marketplaces including Wolt, Lieferando and Uber Eats. The company is backed by HV Capital and Felix Capital alongside founders of FlixBus, Gorillas, Flaschenpost, Glovo, Foodspring, Foodora, Honest Food and Finleap. LANCH publishes a marketing and partner-recruitment website only; as of this enrichment pass it exposes no public developer portal, API documentation, machine-readable API specification or SDK surface.

human only

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.

Kin Score

API Evangelist profiles Lanch 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 — Lanch scores 11.0/100 (minimal), with a separate agent-readiness read of 4/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 Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 11.0/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 0.0 / 20
Commercial Clarity 4.2 / 20
Operational Transparency 0.0 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Agent readiness — 4/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3

How we profile Lanch

Each block below is one kind of artifact we hold for Lanch. 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.

Lanch Domain Security

TLSv1.3 · HSTS

SECURITY

Resources

Every other property we hold for Lanch — 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.

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Access & Security 1

Authentication, authorization, and security posture

Company 3

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/lanch · machine-readable index on apis.io