Taste

Taste Labs is a San Francisco research lab and infrastructure company building "the taste layer for AI" — decoding subjective design domains to end AI slop. Its Taste Engine API extracts brand and design guidelines from a reference site or a prior submission and enhances website and slide-deck prompts so AI generation stays on-brand, returning an enhanced prompt plus structured brand context and reasoning. The company is backed by CRV and Amplify Partners and runs the TasteMakers community program. This profile was enriched from the provider's live public surface, including the Taste Engine API OpenAPI.

Taste publishes 3 API contracts indexed on the APIs.io network: Health API, Prompt Enhancement API, and Engine API. Tagged areas include Company, Artificial Intelligence, Design, Machine Learning, and Developer Tools.

The Taste catalog on APIs.io includes 1 Spectral governance ruleset.

Taste’s developer surface includes engineering blog, authentication, and 12 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

23.1/100 emerging ▬ flat Agent 24/100 agent aware Front door AI 5/6 prominent Heartbeat 97/100 alive Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 published contract 1 Agent Skills

Company Artificial Intelligence Design Machine Learning Developer Tools Prompt Engineering Content Generation

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 23.1/100 · emerging

Contract Quality 8.3 / 19

Developer Ergonomics 2.4 / 15

Access Clarity 0.0 / 15

Operational Transparency 0.0 / 10

Contract Governance 1.6 / 9

Discoverability 5.5 / 8

Regulatory Posture 2.3 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 24/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 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 Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/taste/"><img src="https://apis.io/badge/taste/card.svg" alt="Taste on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

9 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Access Clarity scores 0.0 — up to +20.0 composite points
Developer Ergonomics scores 16.1 — up to +16.8 composite points
Contract Quality scores 44.0 — up to +14.0 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/taste/apis.yml: open an issue on github.com/api-evangelist/taste to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 1

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

OpenAPI

measured — observed by APIs.io (published)

APIs 3

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

Taste Health API

The health API from Taste — 2 operation(s) for health.

Taste Prompt Enhancement API

The Prompt Enhancement API from Taste — 2 operation(s) for prompt enhancement.

Taste Engine API

The Taste Engine API API from Taste — 1 operation(s) for taste engine api.

Open Collections 3

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Taste Engine health API

OPEN COLLECTION

Taste Engine health Prompt Enhancement API

OPEN COLLECTION

Taste Engine health Taste Engine API API

OPEN COLLECTION

Agent Skills 1

Packaged agent skills for driving this provider's APIs from an AI assistant.

Enhance a design prompt with brand guidelines

AGENT SKILL

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

Taste API Rules

40 rules · 38 errors 1 warnings 1 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Taste Taste Engine Overlay

3 actions · update · taste-taste-engine-openapi.json

DERIVED

Security Posture 2

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

Taste Authentication

http · 1 scheme

SECURITY

Taste Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

X-MCPServerCandidate

AgentSkill

LLMsTxt

WellKnown

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

ErrorCatalog

Conventions

DataModel

Conformance

Lifecycle

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

Overlay

Overlay

Source (apis.yml)

aid: taste
name: Taste
description: Taste Labs is a San Francisco research lab and infrastructure company building "the taste layer for AI" — decoding
  subjective design domains to end AI slop. Its Taste Engine API extracts brand and design guidelines from a reference site
  or a prior submission and enhances website and slide-deck prompts so AI generation stays on-brand, returning an enhanced
  prompt plus structured brand context and reasoning. The company is backed by CRV and Amplify Partners and runs the TasteMakers
  community program. This profile was enriched from the provider's live public surface, including the Taste Engine API OpenAPI.
url: https://raw.githubusercontent.com/api-evangelist/taste/refs/heads/main/apis.yml
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: true
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - openapi
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-06'
  method: derived
image: https://cdn.prod.website-files.com/6a1d5baf94efef5f7c435fc3/6a306ae79b1ce1b28e27e16b_taste_Logo.png
x-type: company
x-source: vc-portfolio
x-backed-by:
- crv
- amplify
x-tier: stub
x-tier-reason: portfolio-lead
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 14
  pass: local-v1
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-09-16'
tags:
- Company
- Artificial Intelligence
- Design
- Machine Learning
- Developer Tools
- Prompt Engineering
- Content Generation
tags_raw:
- Company
- Ai
- Design
- Machine Learning
- Developer Tools
- Prompt Engineering
- Content Generation
- Machine-Learning
apis:
- aid: taste:taste-health-api
  name: Taste Health API
  description: The health API from Taste — 2 operation(s) for health.
  humanURL: https://tastelabs.com/
  baseURL: https://api.tastelabs.com
  tags:
  - Health
  tags_raw:
  - health
  properties:
  - type: OpenAPI
    url: openapi/taste-health-api-openapi.yml
- aid: taste:taste-prompt-enhancement-api
  name: Taste Prompt Enhancement API
  description: The Prompt Enhancement API from Taste — 2 operation(s) for prompt enhancement.
  humanURL: https://tastelabs.com/
  baseURL: https://api.tastelabs.com
  tags:
  - Prompt Enhancement
  properties:
  - type: OpenAPI
    url: openapi/taste-prompt-enhancement-api-openapi.yml
- aid: taste:taste-taste-engine-api-api
  name: Taste Engine API
  description: The Taste Engine API API from Taste — 1 operation(s) for taste engine api.
  humanURL: https://tastelabs.com/
  baseURL: https://api.tastelabs.com
  tags:
  - Taste Engine API
  properties:
  - type: OpenAPI
    url: openapi/taste-taste-engine-api-api-openapi.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Overlay
  url: overlays/taste-taste-engine-overlay.yaml
- type: DomainSecurity
  url: security/taste-domain-security.yml
- type: Website
  url: https://tastelabs.com/
- type: Blog
  url: https://tastelabs.com/blog
- type: Authentication
  url: authentication/taste-authentication.yml
- type: ErrorCatalog
  url: errors/taste-problem-types.yml
- type: Conventions
  url: conventions/taste-conventions.yml
- type: DataModel
  url: data-model/taste-data-model.yml
- type: X-MCPServerCandidate
  url: mcp/taste-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: AgentSkill
  url: skills/_index.yml
- type: LLMsTxt
  url: llms/taste-llms.txt
- type: Conformance
  url: conformance/taste-conformance.yml
- type: WellKnown
  url: well-known/taste-well-known.yml
- type: Lifecycle
  url: lifecycle/taste-lifecycle.yml

Taste API — frequently asked questions

Does Taste have an API?

Yes. APIs.io lists 3 APIs from Taste, including Taste Health API, Taste Prompt Enhancement API and Taste Engine API.

Is there an OpenAPI specification for the Taste API?

Yes. APIs.io indexes 3 OpenAPI specifications for Taste, each linked for download from this page.

How do I authenticate with the Taste API?

Taste uses bearer-token authentication (http · 1 scheme). The details are profiled on APIs.io as Taste Authentication.

Is the Taste API ready for AI agents?

Taste has a Kin Score of 23.1 out of 100 (emerging) and an Agent Readiness score of 23.8 (agent-aware), scored by API Evangelist on 2026-11-06.

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/taste"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/taste/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/taste/evidence"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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