Tastewise

Tastewise is a food and beverage consumer-intelligence platform that reads live demand across social posts, recipes, restaurant menus and retail data, and exposes it to product-innovation, marketing, foodservice and retail-sales teams at CPG brands. The platform is built on menus from 1.4M+ restaurants, 12K+ retail brands, social signals from 90M+ consumers and a proprietary consumer panel. Tastewise sells a commercial REST API — documented publicly at docs.tastewise.io and served from api.tastewise.io — covering recipes, ingredients, dishes, restaurants, menus, consumer motivations, content discovery, trend validation and trend performance, plus an embedded widgets surface and bulk product-list operations with webhook callbacks. Access is per-customer: a bearer API key plus an X-Customer-Id header, with per-route permissions granted per contract. Customers include Nestle and Mars.

Tastewise publishes 1 API on the APIs.io network. Tagged areas include Company, Food and Beverage, Consumer Insights, Market Intelligence, and Restaurant.

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

Tastewise’s developer surface includes documentation, API reference, support, engineering blog, pricing, signup flow, authentication, and 16 more developer resources.

🌐 Visit website 📡 Source on GitHub
42.5/100 developing ▬ flat Agent 32/100 agent ready Full breakdown ↓
scored 2026-09-01 · rubric v0.17.2
1 APIs
CompanyFood and BeverageConsumer InsightsMarket IntelligenceRestaurantMenusRecipesTrendsCPGArtificial IntelligenceDataAnalytics

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-01 · rubric v0.17.2
Composite quality — 42.5/100 · developing
Contract Quality 10.7 / 25
Developer Ergonomics 7.1 / 20
Access Clarity 9.5 / 20
Operational Transparency 5.5 / 13
Contract Governance 2.2 / 12
Discoverability 7.6 / 10
Agent readiness — 32/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
Documented Reversibility 0 / 6
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 6 / 6
Agent Skills 0 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Delegated User Identity 0 / 6
Protected Resource Metadata 0 / 5
Registration Without a Human 0 / 6
Agentic Commerce Surface 0 / 5
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/tastewise: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

Tastewise API

Commercial REST API over the Tastewise food and beverage intelligence graph. Publicly documented operations span recipes (popular/trending), ingredients, dishes and side dishes,...

Pricing Plans 1

Published pricing tiers and plan structures.

Tastewise Plans Pricing

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Tastewise Rate Limits

3 limits

RATE LIMITS

Event Specifications 1

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

Tastewise Webhooks

ASYNCAPI

Security Posture 3

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

Tastewise Authentication

2 schemes

SECURITY

Tastewise Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Tastewise Trust Center

ISO 27001, ISO 27017, GDPR

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

SignUp
SignUp

Documentation 2

Reference material describing how the API behaves

Documentation
Documentation
 APIReference
APIReference

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt
LLMsTxt

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

ErrorCatalog
ErrorCatalog
 Conventions
Conventions
 Webhooks
Webhooks
 Lifecycle
Lifecycle
 Conformance
Conformance

Build 2

SDKs, sample code, and the tooling you integrate with

GitHubOrganization
GitHubOrganization
 Packages
Packages

Access & Security 4

Authentication, authorization, and security posture

TrustCenter
TrustCenter
 DomainSecurity
DomainSecurity
 Compliance
Compliance
 Authentication
Authentication

Operate 2

Status, limits, changes, and where to get help

Support
Support
 RateLimits
RateLimits

Commercial 4

Pricing, plans, and the legal terms of use

Pricing
Pricing
 TermsOfService
TermsOfService
 PrivacyPolicy
PrivacyPolicy
 Plans
Plans

Company 2

The organization behind the API

Website
Website
 Blog
Blog

Source (apis.yml)

apis.yml Raw ↑ 
aid: tastewise
name: Tastewise
description: 'Tastewise is a food and beverage consumer-intelligence platform that reads live demand across social posts,
  recipes, restaurant menus and retail data, and exposes it to product-innovation, marketing, foodservice and retail-sales
  teams at CPG brands. The platform is built on menus from 1.4M+ restaurants, 12K+ retail brands, social signals from 90M+
  consumers and a proprietary consumer panel. Tastewise sells a commercial REST API — documented publicly at docs.tastewise.io
  and served from api.tastewise.io — covering recipes, ingredients, dishes, restaurants, menus, consumer motivations, content
  discovery, trend validation and trend performance, plus an embedded widgets surface and bulk product-list operations with
  webhook callbacks. Access is per-customer: a bearer API key plus an X-Customer-Id header, with per-route permissions granted
  per contract. Customers include Nestle and Mars.'
url: https://raw.githubusercontent.com/api-evangelist/tastewise/refs/heads/main/apis.yml
image: https://tastewise.io/wp-content/uploads/2024/01/favicon-150x150.png
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.20'
created: '2026-08-29'
modified: '2026-08-29'
tags:
- Company
- Food and Beverage
- Consumer Insights
- Market Intelligence
- Restaurant
- Menus
- Recipes
- Trends
- CPG
- Artificial Intelligence
- Data
- Analytics
tags_raw:
- Company
- Food and Beverage
- Consumer Insights
- Market Intelligence
- Restaurants
- Menus
- Recipes
- Trends
- CPG
- Artificial Intelligence
- Data
- Analytics
apis:
- aid: tastewise:tastewise-api
  name: Tastewise API
  description: Commercial REST API over the Tastewise food and beverage intelligence graph. Publicly documented operations
    span recipes (popular/trending), ingredients, dishes and side dishes, restaurants (search, detail, menus, ingredients,
    signals, bestsellers, price analysis, chain matching), menus and menu insights, consumer motivations, social content discovery,
    flavor combinations, trend validation and trend performance, a combined insights endpoint, an embedded widgets query surface,
    and product-list management with bulk import and webhook completion callbacks. Authentication is a bearer API key paired
    with an X-Customer-Id header, and each route requires a named permission on the account. No machine-readable OpenAPI is
    published; the reference is human-readable Slate documentation.
  humanURL: https://docs.tastewise.io/
  baseURL: https://api.tastewise.io
  tags:
  - Food and Beverage
  - Consumer Insights
  - Restaurant
  - Menus
  - Recipes
  - Trends
  tags_raw:
  - Food and Beverage
  - Consumer Insights
  - Restaurants
  - Menus
  - Recipes
  - Trends
  properties:
  - type: APIReference
    url: https://docs.tastewise.io/
  - type: Authentication
    url: authentication/tastewise-authentication.yml
  - type: RateLimits
    url: rate-limits/tastewise-rate-limits.yml
  - type: ErrorCatalog
    url: errors/tastewise-problem-types.yml
  - type: Conventions
    url: conventions/tastewise-conventions.yml
  - type: Webhooks
    url: asyncapi/tastewise-webhooks.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: TrustCenter
  url: security/tastewise-trust-center.yml
- type: DomainSecurity
  url: security/tastewise-domain-security.yml
- type: Website
  url: https://tastewise.io/
- type: Documentation
  url: https://docs.tastewise.io/
- type: APIReference
  url: https://docs.tastewise.io/
- type: Support
  url: https://help.tastewise.io/knowledge
- type: Blog
  url: https://tastewise.io/blog
- type: GitHubOrganization
  url: https://github.com/tastewise
- type: Pricing
  url: https://tastewise.io/pricing
- type: SignUp
  url: https://app.tastewise.io/login
- type: TermsOfService
  url: https://tastewise.io/legal/terms-and-conditions
- type: PrivacyPolicy
  url: https://tastewise.io/privacy-policy
- type: Compliance
  url: https://tastewise.io/trust
- type: LLMsTxt
  url: llms/tastewise-llms.txt
- type: RateLimits
  url: rate-limits/tastewise-rate-limits.yml
- type: Authentication
  url: authentication/tastewise-authentication.yml
- type: ErrorCatalog
  url: errors/tastewise-problem-types.yml
- type: Conventions
  url: conventions/tastewise-conventions.yml
- type: Webhooks
  url: asyncapi/tastewise-webhooks.yml
- type: Lifecycle
  url: lifecycle/tastewise-lifecycle.yml
- type: Conformance
  url: conformance/tastewise-conformance.yml
- type: Plans
  url: plans/tastewise-plans-pricing.yml
- type: Packages
  url: packages/tastewise-packages.yml
x-enrichment:
  date: '2026-08-29'
  status: enriched
  artifacts_added: 14
  pass: local-v1

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider 
curl "https://apis.io/api/v1/providers/tastewise"
All providers 
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose 
curl "https://apis.io/api/v1/providers/tastewise/operations?limit=25"
How their score was established 
curl "https://apis.io/api/v1/providers/tastewise/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.