Cooklist website screenshot

Cooklist

Cooklist is an agentic commerce platform purpose-built for grocery and retail. It provides retailer-native AI shopping assistants that plan meals, run solution-first agentic search over live catalog and inventory, assemble cart-ready bundles, and execute verified cart operations against the retailer's system of record. Founded in 2018, Cooklist powers the first agentic AI shopping experience launched by Kroger (the Kroger AI Meal Assistant, live since December 2025) and integrates with 15+ retailer catalogs. Retailers embed a drop-in JavaScript SDK that talks to Cooklist over HTTPS (GraphQL) and WSS (real-time streaming); a B2B Partner API (API key or JWT auth, per-organization field allowlists), authenticated webhooks, and a Model Context Protocol (MCP) interface expose real-time retail inventory and pricing to third-party LLMs such as ChatGPT and Gemini for off-site agentic commerce.

Cooklist is profiled on the APIs.io network. Tagged areas include Company, Agentic Commerce, Grocery, Retail, and AI Assistant.

The Cooklist catalog on APIs.io includes 1 event-driven AsyncAPI specification.

Cooklist’s developer surface includes documentation, support, signup flow, authentication, and 10 more developer resources.

26.8/100 emerging ▬ flat Agent 27/100 agent aware Full breakdown ↓
scored 2026-07-27 · rubric v0.5
AccessSelf serve
0 APIs 1 MCP Servers
CompanyAgentic CommerceGroceryRetailAI AssistantModel Context ProtocolRecipesMeal PlanningE-CommercePersonalization

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 26.8/100 · emerging
Contract Quality 5.7 / 25
Developer Ergonomics 6.5 / 20
Commercial Clarity 6.8 / 20
Operational Transparency 1.0 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Agent readiness — 27/100 · agent aware
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 6 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/cooklist: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

cooklist-mcp.yml

MCP SERVER

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Cooklist Authentication

apiKey/http · 2 schemes

SECURITY

Cooklist Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

Documentation 1

Reference material describing how the API behaves

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Access & Security 2

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

Source (apis.yml)

apis.yml Raw ↑
aid: cooklist
name: Cooklist
description: Cooklist is an agentic commerce platform purpose-built for grocery and retail. It provides retailer-native AI
  shopping assistants that plan meals, run solution-first agentic search over live catalog and inventory, assemble cart-ready
  bundles, and execute verified cart operations against the retailer's system of record. Founded in 2018, Cooklist powers
  the first agentic AI shopping experience launched by Kroger (the Kroger AI Meal Assistant, live since December 2025) and
  integrates with 15+ retailer catalogs. Retailers embed a drop-in JavaScript SDK that talks to Cooklist over HTTPS (GraphQL)
  and WSS (real-time streaming); a B2B Partner API (API key or JWT auth, per-organization field allowlists), authenticated
  webhooks, and a Model Context Protocol (MCP) interface expose real-time retail inventory and pricing to third-party LLMs
  such as ChatGPT and Gemini for off-site agentic commerce.
url: https://raw.githubusercontent.com/api-evangelist/cooklist/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- techstars
- mercury-fund
x-tier: stub
x-tier-reason: portfolio-lead
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
specificationVersion: '0.20'
created: '2026-07-17'
modified: '2026-07-18'
image: https://cooklist.com/images/favicon.png
tags:
- Company
- Agentic Commerce
- Grocery
- Retail
- AI Assistant
- Model Context Protocol
- Recipes
- Meal Planning
- E-Commerce
- Personalization
apis: []
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
- FN: Cooklist
  email: daniel@cooklist.com
common:
- type: Website
  url: https://cooklist.com/
- type: Documentation
  url: https://cooklist.com/platform/agentic-commerce
- type: About
  url: https://cooklist.com/company/about
- type: Support
  url: https://cooklist.com/support
- type: SignUp
  url: https://cooklist.com/request-demo
- type: PrivacyPolicy
  url: https://cooklist.com/privacy-policy
- type: TermsOfService
  url: https://cooklist.com/terms-of-use
- type: LLMsTxt
  url: llms/cooklist-llms.txt
- type: MCPServer
  url: mcp/cooklist-mcp.yml
- type: Webhooks
  url: asyncapi/cooklist-webhooks.yml
- type: Authentication
  url: authentication/cooklist-authentication.yml
- type: Conventions
  url: conventions/cooklist-conventions.yml
- type: Components
  url: components/cooklist-components.yml
- type: DomainSecurity
  url: security/cooklist-domain-security.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence