Kitchensurfing
Kitchensurfing was a New York City marketplace that booked professional chefs to shop for, cook, and serve meals in customers' own kitchens, founded in 2012 and backed by roughly $20M from Union Square Ventures, Spark Capital, and Tiger Global. It began as an advance-booking platform for private dinner parties and pivoted in 2015 to a flat-rate on-demand model in which a chef arrived and cooked dinner within a fixed window. Neither model produced sustainable demand against better-capitalized meal-kit and delivery competitors, and the company discontinued service and shut down on April 15, 2016. It never published a public developer API, SDK, or developer portal. Its GitHub organization survives with eleven public repositories - open-source Ruby/Rails forks and internal hackathon projects, last active in 2016 - but contains no client library or API definition. The kitchensurfing.com domain was subsequently re-registered by an unrelated cooking-products affiliate publisher and no longer represents this company.
Kitchensurfing is tracked in the API Evangelist network. This page is the human-readable profile that sits on top of the machine-readable index we maintain at apis.io.
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. The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Resources
Every other property we hold for Kitchensurfing — 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.
Build 1
SDKs, sample code, and the tooling you integrate with
Company 3
The organization behind the API
Other 2
Properties that don't map to a standard resource type
Kitchensurfing is in the network as a tracked entity. We haven't yet indexed a public API surface for it — when one is published, the artifacts, score, and agent-readiness read will appear here automatically. The source repository is where that profile is built.
← All providers · Data indexed from github.com/api-evangelist/kitchensurfing · machine-readable index on apis.io
This is an independent, third-party profile of Kitchensurfing, 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.