Liquid Death website screenshot

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 2 APIs on the APIs.io network: Catalog API and Discovery API. Tagged areas include Company, Beverages, Consumer Packaged Goods, Direct to Consumer, and E-Commerce.

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

41.4/100 developing ▬ flat Agent 47/100 agent native saas Full breakdown ↓
scored 2026-09-14 · rubric v0.22.0
AccessSelf serve
1 APIs 1 MCP Servers
CompanyBeveragesConsumer Packaged GoodsDirect to ConsumerE-CommerceRetailAgentic CommerceUniversal Commerce ProtocolMCPShopify

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-14 · rubric v0.22.0
Create-or-Update Ergonomics does not apply to this provider. The published contracts declare no write operations, and a read-only API cannot create-or-update. The facet is excluded from this provider's denominator entirely — not scored zero. A reference or data API is not deficient for being unable to upsert.
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 github.com/api-evangelist/liquid-death: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 4

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

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...

Liquid Death Catalog API

Product and collection data

Liquid Death Discovery API

Store-level discovery documents for crawlers and agents

Open Collections 1

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

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 7

Properties that don't map to a standard resource type

Scroll for all 7

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.'
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  - scopes
  - security
  generated: '2026-09-02'
  method: derived
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.23'
created: '2026-08-01'
modified: '2026-08-01'
tags:
- Company
- Beverages
- Consumer Packaged Goods
- Direct to Consumer
- E-Commerce
- Retail
- Agentic Commerce
- Universal Commerce Protocol
- MCP
- Shopify
tags_raw:
- Company
- Beverages
- Consumer Packaged Goods
- Direct to Consumer
- Ecommerce
- Retail
- Agentic Commerce
- Universal Commerce Protocol
- MCP
- Shopify
apis:
- 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
  - E-Commerce
  tags_raw:
  - 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
  tags_raw:
  - Authentication
  - OpenID Connect
  - OAuth
  properties:
  - type: OpenIDConnect
    url: well-known/liquid-death-openid-configuration.json
  - type: OAuthScopes
    url: scopes/liquid-death-scopes.yml
- aid: liquid-death:liquid-death-catalog-api
  name: Liquid Death Catalog API
  description: Product and collection data
  humanURL: https://liquiddeath.com/agents.md
  baseURL: https://liquiddeath.com
  tags:
  - Catalog
  properties:
  - type: OpenAPI
    url: openapi/liquid-death-catalog-api-openapi.yml
  - type: Documentation
    url: https://liquiddeath.com/agents.md
  - type: AgenticAccess
    url: agentic-access/liquid-death-agentic-access.yml
- aid: liquid-death:liquid-death-discovery-api
  name: Liquid Death Discovery API
  description: Store-level discovery documents for crawlers and agents
  humanURL: https://liquiddeath.com/agents.md
  baseURL: https://liquiddeath.com
  tags:
  - Discovery
  properties:
  - type: OpenAPI
    url: openapi/liquid-death-discovery-api-openapi.yml
  - type: Documentation
    url: https://liquiddeath.com/agents.md
  - type: AgenticAccess
    url: agentic-access/liquid-death-agentic-access.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: CapabilityMap
  url: capabilities/liquid-death-capability-edges.yml
  name: Liquid Death Business Capability Map
- 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

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/liquid-death"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/liquid-death/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/liquid-death/evidence"

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

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.

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