How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
2ndKitchen website screenshot

2ndKitchen

2ndKitchen was a Chicago-based food-technology startup (Techstars '18) that let businesses without an on-site kitchen — bars, breweries, hotels, and apartment communities — offer custom food menus sourced from nearby partner restaurants, handling ordering, pricing, payment, and delivery on their behalf. The company was acquired by REEF Technology in December 2021 and its 2ndkitchen.com domain now redirects to reeftechnology.com. This API Evangelist profile captures the set of nine microservice OpenAPI definitions still published on the legacy Swagger UI at docs.2ndkitchen.com (authentication, business, user, restaurant, order, pricing, payment, delivery, and indexing services), preserved here as a historical record of the platform's API surface.

agent aware

More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.

Kin Score

API Evangelist profiles 2ndKitchen the way a machine reads it — 27 machine-readable artifacts across 9 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 — 2ndKitchen scores 24.1/100 (emerging), with a separate agent-readiness read of 21/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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.

Kin Score Kin Score How this is scored →
scored 2026-09-10 · rubric v0.20.0
2ndKitchen Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from 2ndKitchen's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.

<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/2ndkitchen/"
   title="2ndKitchen on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/2ndkitchen.svg"
       alt="2ndKitchen Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile 2ndKitchen

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

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.

2ndKitchen Authentication API

The Authentication API from 2ndKitchen — 5 operation(s) for authentication.

2ndKitchen Brand API

The Brand API from 2ndKitchen — 1 operation(s) for brand.

2ndKitchen Business API

The Business API from 2ndKitchen — 1 operation(s) for business.

2ndKitchen Coupons API

The Coupons API from 2ndKitchen — 1 operation(s) for coupons.

2ndKitchen Deliveries API

The Deliveries API from 2ndKitchen — 1 operation(s) for deliveries.

2ndKitchen Orders API

The Orders API from 2ndKitchen — 3 operation(s) for orders.

2ndKitchen Payment API

The Payment API from 2ndKitchen — 1 operation(s) for payment.

2ndKitchen Product API

The Product API from 2ndKitchen — 4 operation(s) for product.

2ndKitchen Products API

The Products API from 2ndKitchen — 1 operation(s) for products.

2ndKitchen Restaurant API

The Restaurant API from 2ndKitchen — 1 operation(s) for restaurant.

2ndKitchen Restaurants API

The Restaurants API from 2ndKitchen — 1 operation(s) for restaurants.

2ndKitchen Users API

The Users API from 2ndKitchen — 4 operation(s) for users.

Scroll within the panel for all 12 ·

Open Collections 13

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).

Scroll within the panel for all 13 ·

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.

2Ndkitchen Authentication

http · 1 scheme

SECURITY

2Ndkitchen Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Every other property we hold for 2ndKitchen — 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

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Access & Security 2

Authentication, authorization, and security posture

Company 1

The organization behind the API

Other 1

Properties that don't map to a standard resource type

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

Where this information came from

This is an independent, third-party profile of 2ndKitchen, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.