Liquid Death

Liquid Death is a Los Angeles beverage company founded in 2014 by Mike Cessario, Pat Cook and JonRyan Riggins, selling still and sparkling mountain water, iced tea, flavored sparkling water, the Death Dust electrolyte powder and a Sparkling Energy line, all in recyclable aluminum tallboys and marketed through a deliberately horror-comedy brand voice. It has raised roughly $264M and was valued at $1.4B in its 2024 Series F. Liquid Death publishes no conventional developer portal, yet it is one of the more agent-forward direct-to-consumer storefronts in the catalog: liquiddeath.com serves a first-party agents.md (mirrored at /llms.txt), a dedicated agentic-discovery sitemap, an agent policy block inside robots.txt, a Universal Commerce Protocol merchant profile at /.well-known/ucp, a live UCP shopping MCP endpoint, and both OpenID Connect and RFC 8414 OAuth discovery documents for its customer account. The storefront exposes an anonymous read-only product and collection JSON surface, while every cart, checkout and order capability is confined to the identity-gated, idempotency-keyed MCP transport that requires contemporaneous human approval before payment.

Liquid Death publishes 1 API on the APIs.io network: Storefront Read-Only JSON API. Tagged areas include Company, Beverages, Consumer Packaged Goods, Direct to Consumer, and Ecommerce.

Liquid Death’s developer surface includes documentation, getting-started guide, authentication, FAQ, support, engineering blog, and 27 more developer resources.

38.8/100 thin ▬ flat Agent 57/100 agent native Full breakdown ↓
scored 2026-08-05 · rubric v0.9.1
3 APIs 1 MCP Servers
CompanyBeveragesConsumer Packaged GoodsDirect to ConsumerEcommerceRetailAgentic CommerceUniversal Commerce ProtocolMCPShopify

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-05 · rubric v0.9.1
Composite quality — 38.8/100 · thin
Contract Quality 14.5 / 25
Developer Ergonomics 9.5 / 20
Commercial Clarity 4.2 / 20
Operational Transparency 0.0 / 13
Governance 1.4 / 12
Discoverability 9.3 / 10
Agent readiness — 57/100 · agent native
Machine-Readable Contract 18 / 18
Agentic Access Contract 10 / 10
MCP Server 12 / 12
Machine-Readable Auth 10 / 10
Idempotency 9 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 7 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 5 / 5
Well-Known Catalog 4 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
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/liquid-death: 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 3

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

Liquid Death Storefront Read-Only JSON API

The anonymous, read-only product and collection JSON surface Liquid Death documents for AI agents in its agents.md, covering product records, collection listings, storefront sea...

Liquid Death UCP Shopping MCP

Liquid Death's hosted Model Context Protocol server implementing the Universal Commerce Protocol dev.ucp.shopping service — catalog search and lookup, cart, checkout, fulfillmen...

Liquid Death Customer Account OAuth

The OpenID Connect and OAuth 2.0 authorization server for the Liquid Death customer account, hosted at account.liquiddeath.com and discoverable from both /.well-known/openid-con...

MCP Servers 1

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

Security Posture 2

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

Liquid Death Authentication

none/openIdConnect/oauth2/agentProfile · 4 schemes

SECURITY

Liquid Death Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Liquid Death Scopes

4 scopes · authorizationCode

4 scopes

SCOPES

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Liquid Death Agentic Access

7 operations

7 operations · 0 acting

AGENTIC

Resources

Get Started 1

Portal, sign-up, and the first successful call

Documentation 2

Reference material describing how the API behaves

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 3

Authentication, authorization, and security posture

Operate 2

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

Company 5

The organization behind the API

Other 6

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: liquid-death
name: Liquid Death
description: 'Liquid Death is a Los Angeles beverage company founded in 2014 by Mike Cessario, Pat Cook and JonRyan Riggins,
  selling still and sparkling mountain water, iced tea, flavored sparkling water, the Death Dust electrolyte powder and a
  Sparkling Energy line, all in recyclable aluminum tallboys and marketed through a deliberately horror-comedy brand voice.
  It has raised roughly $264M and was valued at $1.4B in its 2024 Series F. Liquid Death publishes no conventional developer
  portal, yet it is one of the more agent-forward direct-to-consumer storefronts in the catalog: liquiddeath.com serves a
  first-party agents.md (mirrored at /llms.txt), a dedicated agentic-discovery sitemap, an agent policy block inside robots.txt,
  a Universal Commerce Protocol merchant profile at /.well-known/ucp, a live UCP shopping MCP endpoint, and both OpenID Connect
  and RFC 8414 OAuth discovery documents for its customer account. The storefront exposes an anonymous read-only product and
  collection JSON surface, while every cart, checkout and order capability is confined to the identity-gated, idempotency-keyed
  MCP transport that requires contemporaneous human approval before payment.'
image: https://liquiddeath.com/cdn/shop/files/Liquid-Death-Preview-Image_7033558e-a84d-4880-8a70-87e84739f262.jpg?v=1681949476
url: https://raw.githubusercontent.com/api-evangelist/liquid-death/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
x-tier: profiled
x-tier-reason: harvest
specificationVersion: '0.20'
created: '2026-08-01'
modified: '2026-08-01'
tags:
- Company
- Beverages
- Consumer Packaged Goods
- Direct to Consumer
- Ecommerce
- Retail
- Agentic Commerce
- Universal Commerce Protocol
- MCP
- Shopify
apis:
- name: Liquid Death Storefront Read-Only JSON API
  description: The anonymous, read-only product and collection JSON surface Liquid Death documents for AI agents in its agents.md,
    covering product records, collection listings, storefront search and the store-level discovery documents. No authentication
    required. Contains no transactional capability by design.
  humanURL: https://liquiddeath.com/agents.md
  baseURL: https://liquiddeath.com
  tags:
  - Ecommerce
  - Catalog
  - Direct to Consumer
  - Agentic Commerce
  properties:
  - type: Documentation
    url: https://liquiddeath.com/agents.md
  - type: OpenAPI
    url: openapi/liquid-death-storefront-openapi.yml
  - type: Overlay
    url: overlays/liquid-death-storefront-overlay.yaml
  - type: AgenticAccess
    url: agentic-access/liquid-death-agentic-access.yml
- name: Liquid Death UCP Shopping MCP
  description: Liquid Death's hosted Model Context Protocol server implementing the Universal Commerce Protocol dev.ucp.shopping
    service — catalog search and lookup, cart, checkout, fulfillment, discount and order. Advertised in robots.txt, agents.md
    and the /.well-known/ucp merchant profile. Requires a resolvable UCP agent profile, mandates an Idempotency-Key on complete_checkout,
    cancel_checkout and cancel_cart, and forbids completing payment without explicit buyer approval.
  humanURL: https://liquiddeath.com/agents.md
  baseURL: https://liquiddeath.myshopify.com/api/ucp/mcp
  tags:
  - Agentic Commerce
  - MCP
  - Universal Commerce Protocol
  - Ecommerce
  properties:
  - type: Documentation
    url: https://liquiddeath.com/agents.md
  - type: MCPServer
    url: mcp/liquid-death-mcp.yml
  - type: ToolCrosswalk
    url: mcp/liquid-death-tool-crosswalk.yml
  - type: OpenRPC
    url: mcp/liquid-death-ucp-shopping-mcp.openrpc.json
- name: Liquid Death Customer Account OAuth
  description: The OpenID Connect and OAuth 2.0 authorization server for the Liquid Death customer account, hosted at account.liquiddeath.com
    and discoverable from both /.well-known/openid-configuration and /.well-known/oauth-authorization-server. Authorization
    code flow with PKCE (S256); advertises the customer-account-api:full and customer-account-mcp-api:full scopes.
  humanURL: https://liquiddeath.com/.well-known/openid-configuration
  baseURL: https://account.liquiddeath.com/authentication
  tags:
  - Authentication
  - OpenID Connect
  - OAuth
  properties:
  - type: OpenIDConnect
    url: well-known/liquid-death-openid-configuration.json
  - type: OAuthScopes
    url: scopes/liquid-death-scopes.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://liquiddeath.com/
- type: Documentation
  url: https://liquiddeath.com/agents.md
- type: GettingStarted
  url: https://liquiddeath.com/agents.md
- type: LLMsTxt
  url: llms/liquid-death-llms.txt
- type: WellKnown
  url: well-known/liquid-death-well-known.yml
- type: OpenAPI
  url: openapi/liquid-death-storefront-openapi.yml
- type: Overlay
  url: overlays/liquid-death-storefront-overlay.yaml
- type: MCPServer
  url: mcp/liquid-death-mcp.yml
- type: ToolCrosswalk
  url: mcp/liquid-death-tool-crosswalk.yml
- type: Authentication
  url: authentication/liquid-death-authentication.yml
- type: OAuthScopes
  url: scopes/liquid-death-scopes.yml
- type: Conventions
  url: conventions/liquid-death-conventions.yml
- type: Idempotency
  url: conventions/liquid-death-conventions.yml
- type: ErrorCatalog
  url: errors/liquid-death-problem-types.yml
- type: Conformance
  url: conformance/liquid-death-conformance.yml
- type: Lifecycle
  url: lifecycle/liquid-death-lifecycle.yml
- type: DataModel
  url: data-model/liquid-death-data-model.yml
- type: AgenticAccess
  url: agentic-access/liquid-death-agentic-access.yml
- type: AgentSkill
  url: skills/_index.yml
- type: DomainSecurity
  url: security/liquid-death-domain-security.yml
- type: FAQ
  url: https://liquiddeath.com/pages/faq
- type: Support
  url: https://liquiddeath.com/pages/summon-us
- type: Blog
  url: https://liquiddeath.com/blogs/news
- type: Shop
  url: https://liquiddeath.com/collections/all
- type: WhereToBuy
  url: https://liquiddeath.com/pages/where-to-buy
- type: Careers
  url: https://liquiddeath.com/pages/careers
- type: About
  url: https://liquiddeath.com/pages/manifesto
- type: TermsOfService
  url: https://liquiddeath.com/policies/terms-of-service
- type: PrivacyPolicy
  url: https://liquiddeath.com/policies/privacy-policy
- type: RefundPolicy
  url: https://liquiddeath.com/policies/refund-policy
- type: Instagram
  url: https://www.instagram.com/liquiddeath/
- type: TikTok
  url: https://www.tiktok.com/@liquiddeath
- type: SecondaryMarket
  url: https://forgeglobal.com/liquid-death_stock/
x-enrichment:
  date: '2026-08-01'
  status: enriched
  artifacts_added: 21
  pass: local-v1