Teabox

Teabox is a premium loose-leaf tea brand and direct-to-consumer e-commerce company backed by Accel. It sources fresh Darjeeling, Assam, Nilgiri and other Indian teas direct from gardens and ships them globally through its online store. The storefront runs on Shopify, which exposes an agent-commerce surface built on the Universal Commerce Protocol (UCP): a hosted shopping MCP endpoint, a machine-readable llms.txt / agents.md, and OpenID Connect authentication via the Shopify Customer Account API (including a customer-account MCP scope). Buyer checkout always requires explicit human approval. This profile was surfaced as an Accel portfolio company and enriched from Teabox's public agent-facing surfaces.

Teabox is listed with 1 API on the APIs.io network. Tagged areas include Company, Consumer, Tea, Food and Beverage, and E-Commerce.

Teabox’s developer surface includes authentication and 8 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

15.4/100 emerging ▬ flat Agent 14/100 agent aware Front door AI 1/6 silent saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

1 API 1 MCP Servers

Company Consumer Tea Food and Beverage E-Commerce Retail Shopify Agentic Commerce

Kin Score

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

Composite quality — 15.4/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 2.0 / 17

Access Clarity 3.6 / 17

Operational Transparency 0.0 / 11

Contract Governance 0.0 / 10

Discoverability 5.7 / 9

Regulatory Posture 4.4 / 15

Agent readiness — 14/100 · agent aware

Machine-Readable Contract 0 / 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 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 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 6 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 5 / 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 could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% 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/teabox/"><img src="https://apis.io/badge/teabox/card.svg" alt="Teabox 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):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
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)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
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)

9 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 0.0 — up to +25.0 composite points
Developer Ergonomics scores 11.9 — up to +17.6 composite points
Access Clarity scores 21.1 — up to +15.8 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/teabox/apis.yml: open an issue on github.com/api-evangelist/teabox 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 2

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.

Model Context Protocol (MCP)

measured — observed by APIs.io (platform)

Universal Commerce Protocol (UCP)

measured — observed by APIs.io (shopify)

APIs 1

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

Teabox Agent Commerce (UCP)

Agent-driven commerce surface for the Teabox Shopify store, implementing the Universal Commerce Protocol (UCP) over a hosted MCP endpoint. Supports catalog search/lookup, cart, ...

MCP Servers 1

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

Teabox MCP Server

Remote MCP server at www.teabox.com over HTTP; 5 tools listed.

MCP SERVER

Security Posture 2

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

Teabox Authentication

openIdConnect/oauth2 · 1 scheme

SECURITY

Teabox Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Teabox Scopes

4 scopes · authorizationCode

4 scopes

SCOPES

Resources

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

MCPServer

MCPServer

WellKnown

WellKnown

LLMsTxt

LLMsTxt

Access & Security 3

Authentication, authorization, and security posture

Authentication

Authentication

OAuthScopes

OAuthScopes

DomainSecurity

DomainSecurity

Commercial 2

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

TermsOfService

TermsOfService

Company 1

The organization behind the API

Website

Website

Source (apis.yml)

aid: teabox
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - scopes
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/teabox.png
name: Teabox
description: 'Teabox is a premium loose-leaf tea brand and direct-to-consumer e-commerce company backed by Accel. It sources
  fresh Darjeeling, Assam, Nilgiri and other Indian teas direct from gardens and ships them globally through its online store.
  The storefront runs on Shopify, which exposes an agent-commerce surface built on the Universal Commerce Protocol (UCP):
  a hosted shopping MCP endpoint, a machine-readable llms.txt / agents.md, and OpenID Connect authentication via the Shopify
  Customer Account API (including a customer-account MCP scope). Buyer checkout always requires explicit human approval. This
  profile was surfaced as an Accel portfolio company and enriched from Teabox''s public agent-facing surfaces.'
url: https://raw.githubusercontent.com/api-evangelist/teabox/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- accel
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-21'
tags:
- Company
- Consumer
- Tea
- Food and Beverage
- E-Commerce
- Retail
- Shopify
- Agentic Commerce
tags_raw:
- Company
- Consumer
- Tea
- Food and Beverage
- E-commerce
- Retail
- Shopify
- Agent Commerce
apis:
- name: Teabox Agent Commerce (UCP)
  description: Agent-driven commerce surface for the Teabox Shopify store, implementing the Universal Commerce Protocol (UCP)
    over a hosted MCP endpoint. Supports catalog search/lookup, cart, checkout, fulfillment, discounts and orders. Payment
    completion requires explicit human buyer approval.
  humanURL: https://www.teabox.com/llms.txt
  tags:
  - Agentic Commerce
  - MCP
  - Universal Commerce Protocol
  - Shopify
  tags_raw:
  - Agent Commerce
  - MCP
  - UCP
  - Shopify
  properties:
  - type: MCPServer
    url: mcp/teabox-mcp.yml
  - type: WellKnown
    url: well-known/teabox-well-known.yml
  - type: LLMsTxt
    url: llms/teabox-llms.txt
  - type: Authentication
    url: authentication/teabox-authentication.yml
  - type: OAuthScopes
    url: scopes/teabox-scopes.yml
  x-surface: platform-generated
  x-platform: shopify
  x-platform-surface: ucp
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: MCPServer
  url: mcp/teabox-mcp.yml
- type: WellKnown
  url: well-known/teabox-well-known.yml
- type: LLMsTxt
  url: llms/teabox-llms.txt
- type: Authentication
  url: authentication/teabox-authentication.yml
- type: OAuthScopes
  url: scopes/teabox-scopes.yml
- type: DomainSecurity
  url: security/teabox-domain-security.yml
- type: PrivacyPolicy
  url: https://www.teabox.com/policies/privacy-policy
- type: TermsOfService
  url: https://www.teabox.com/policies/terms-of-service
- type: Website
  url: https://www.teabox.com
x-enrichment:
  date: '2026-07-21'
  status: enriched
  artifacts_added: 8
  pass: local-v1

Teabox API — frequently asked questions

Does Teabox have an API?

Yes. APIs.io lists 1 API from Teabox, including Teabox Agent Commerce (UCP).

How do I authenticate with the Teabox API?

Teabox documents its authentication (openIdConnect/oauth2 · 1 scheme). The details are profiled on APIs.io as Teabox Authentication.

Does Teabox have an MCP server?

Yes. APIs.io lists 1 MCP server for Teabox: Remote MCP server at www.teabox.com over HTTP; 5 tools listed.

Is the Teabox API ready for AI agents?

Teabox has a Kin Score of 15.4 out of 100 (emerging) and an Agent Readiness score of 13.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/teabox"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/teabox/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.