Chord is a New York / Santa Barbara-based commerce data and AI platform founded in 2021 by Bryan Mahoney (CEO) and Henry Davis (President & Chairman), both former Glossier executives. Chord began as a headless commerce backbone built on top of Solidus — the open-source Spree Commerce fork written in Ruby on Rails — and has since evolved into an AI-native commerce data platform with three layers: a Data Foundation that unifies sources such as Shopify, ad platforms, and CDPs; a Context Stack that grounds AI in store-specific business context; and a set of Agents that take action across the commerce stack. Its current product surface includes Chord OMS (a Solidus-based order management system covering orders, products, promotions, subscriptions, affiliates, gift cards, returns, shipping, tax, and digital products documented at chord.stoplight.io), Chord CDP (customer data platform with identity resolution, RFM scoring, customer lifetime revenue, and destination activations), Chord Event Tracking (client- and server-side eventing with Shopify Web Pixel integration and consent management via OneTrust and Shopify Customer Privacy API), Chord Data Platform (analytics, predictive modeling, attribution, recommendations, Fivetran ingestion, GA4 compatibility), and Chord AI / Copilot Chat, powered by Anthropic Claude (Opus 4.5 for SQL generation, Haiku 4.5 for response generation and classification) with charts, monitors, context modeling, and natural-language data querying. Chord's GitHub org (github.com/chordcommerce) maintains a fleet of Solidus extensions (solidus_stripe, solidus_braintree, solidus_paypal_braintree, solidus_subscriptions, solidus_virtual_gift_card, solidus_importer, solidus_avatax_certified), a consent-manager TypeScript library, a Jitsu fork for event ingestion, and example repos for eventing and analytics. Notable customers include Sonos, Blue Bottle Coffee, Rodan + Fields, MrBeast, and Ritual. Funding has come from M13 Ventures, Equal Ventures, Act One Ventures, Chingona Ventures, and CEAS Investments, with an $18M Series A reported by TechCrunch in 2021. The commercial model is sales-led with custom enterprise pricing gated behind a demo request.
Chord is listed with 3 APIs on the APIs.io network. Tagged areas include Commerce, Composable Commerce, Headless Commerce, Order Management, and OMS.
The Chord catalog on APIs.io includes 1 event-driven AsyncAPI specification.
Chord’s developer surface includes documentation, API reference, getting-started guide, authentication, changelog, release notes, engineering blog, and 43 more developer resources.
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/chord-commerce/"><img src="https://apis.io/badge/chord-commerce/card.svg" alt="Chord 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):
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
Request/Response Examples+7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Documented Reversibility+6 pts — a reversal operation in the contract, graded up when a window is documented too
Agentic Commerce Well-Known Document+5 pts — a parsing /.well-known/ucp.json or acp.json declaring a version and at least one service, OR (0.27) a live x402 payment challenge from _data/x402-adoption.json — `self` when its endpoints are on the provider's own domain, `platform` when they are on a vendor's
3 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
The Kin Score Market layer reads a provider inside its market:
its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted:
not part of the Kin Score or agent readiness.
Registered MCP server and declares compatibility are report only — not weighted.
Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
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.
Chord's hosted Model Context Protocol server — a remote, OAuth-protected, read-only window into a customer's Chord data warehouse. Fourteen documented tools cover schema search,...
The HTTP ingest surface of the Chord customer data platform. Backend systems POST track and identify events to /api/track and /api/identify, authenticated with a per-source writ...
Read API for activated audiences. Once the Dynamic Audiences API destination is enabled on an account, a sync mirrors a custom audience into the API and a server-side GET on /au...
aid: chord-commerce
name: Chord
description: 'Chord is a New York / Santa Barbara-based commerce data and AI platform founded in 2021 by Bryan Mahoney (CEO)
and Henry Davis (President & Chairman), both former Glossier executives. Chord began as a headless commerce backbone built
on top of Solidus — the open-source Spree Commerce fork written in Ruby on Rails — and has since evolved into an AI-native
commerce data platform with three layers: a Data Foundation that unifies sources such as Shopify, ad platforms, and CDPs;
a Context Stack that grounds AI in store-specific business context; and a set of Agents that take action across the commerce
stack. Its current product surface includes Chord OMS (a Solidus-based order management system covering orders, products,
promotions, subscriptions, affiliates, gift cards, returns, shipping, tax, and digital products documented at chord.stoplight.io),
Chord CDP (customer data platform with identity resolution, RFM scoring, customer lifetime revenue, and destination activations),
Chord Event Tracking (client- and server-side eventing with Shopify Web Pixel integration and consent management via OneTrust
and Shopify Customer Privacy API), Chord Data Platform (analytics, predictive modeling, attribution, recommendations, Fivetran
ingestion, GA4 compatibility), and Chord AI / Copilot Chat, powered by Anthropic Claude (Opus 4.5 for SQL generation, Haiku
4.5 for response generation and classification) with charts, monitors, context modeling, and natural-language data querying.
Chord''s GitHub org (github.com/chordcommerce) maintains a fleet of Solidus extensions (solidus_stripe, solidus_braintree,
solidus_paypal_braintree, solidus_subscriptions, solidus_virtual_gift_card, solidus_importer, solidus_avatax_certified),
a consent-manager TypeScript library, a Jitsu fork for event ingestion, and example repos for eventing and analytics. Notable
customers include Sonos, Blue Bottle Coffee, Rodan + Fields, MrBeast, and Ritual. Funding has come from M13 Ventures, Equal
Ventures, Act One Ventures, Chingona Ventures, and CEAS Investments, with an $18M Series A reported by TechCrunch in 2021.
The commercial model is sales-led with custom enterprise pricing gated behind a demo request.'
type: Index
deliveryModel:
model: unknown
open_source: unknown
commercial: true
callable_host: false
label: Delivery model not determined — needs a product licence on record
confidence: low
source:
- pricing
- repository-unlicensed
generated: '2026-08-28'
method: derived
accessModel:
pricing: enterprise
onboarding: unknown
trial: false
try_now: false
public: false
label: Enterprise
confidence: medium
source:
- authentication
- scopes
- rate-limits
- security
generated: '2026-11-06'
method: derived
position: Producing
access: 3rd-Party
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/chord-commerce.png
tags:
- Commerce
- Composable Commerce
- Headless Commerce
- Order Management
- OMS
- Customer Data Platform
- CDP
- Event Tracking
- Commerce Analytics
- Customer Lifetime Value
- AI Agents
- Commerce Copilot
- Solidus
- Spree
- Ruby on Rails
- Shopify
- Direct to Consumer
tags_raw:
- Commerce
- Composable Commerce
- Headless Commerce
- Order Management
- OMS
- Customer Data Platform
- CDP
- Event Tracking
- Commerce Analytics
- Customer Lifetime Value
- AI Agents
- Commerce Copilot
- Solidus
- Spree
- Ruby On Rails
- Shopify
- DTC
- Direct To Consumer
url: https://raw.githubusercontent.com/api-evangelist/chord-commerce/refs/heads/main/apis.yml
created: '2026-05-25'
modified: '2026-08-13'
specificationVersion: '0.23'
apis:
- name: Chord MCP
description: Chord's hosted Model Context Protocol server — a remote, OAuth-protected, read-only window into a customer's
Chord data warehouse. Fourteen documented tools cover schema search, saved views, prior question/SQL pairs, org SQL conventions,
table preview, read-only SQL execution, activation/sync health, and multi-tenant routing across the Chord organizations
the authenticated user belongs to. Registered in Claude via Custom Connectors, via Chord's own Claude Code plugin, or
through the mcp-remote bridge; tools/list is auth-gated behind OAuth 2.1 with PKCE and dynamic client registration against
Chord's Stytch-backed authorization server.
humanURL: https://docs.chord.co/chord-mcp
baseURL: https://mcp.chord.co/mcp
tags:
- MCP
- AI Agents
- Commerce Analytics
- Data Warehouse
properties:
- type: MCPServer
url: mcp/chord-commerce-mcp.yml
- type: Documentation
url: https://docs.chord.co/chord-mcp
- type: OAuthScopes
url: scopes/chord-commerce-scopes.yml
- type: WellKnown
url: well-known/chord-commerce-well-known.yml
- type: SourceCode
url: https://github.com/chordcommerce/chord-copilot
- name: Chord CDP Ingest API
description: 'The HTTP ingest surface of the Chord customer data platform. Backend systems POST track and identify events
to /api/track and /api/identify, authenticated with a per-source write key (X-Write-Key header preferred). Chord publishes
a full canonical event catalog — order, shipment, subscription and user server events plus a browser tracking plan — and
documents its delivery semantics unusually thoroughly: at-least-once delivery, a stable messageId carried end to end,
exponential-backoff retries and a dead-letter queue. Ingest is deliberately permissive: the tracking plan is a convention,
not a schema validator, and custom events pass through unmodified.'
humanURL: https://docs.chord.co/server-events-overview
baseURL: https://production.cdp.ingest.chord.co
tags:
- Event Tracking
- CDP
- Customer Data Platform
- Event
tags_raw:
- Event Tracking
- CDP
- Customer Data Platform
- Events
properties:
- type: Documentation
url: https://docs.chord.co/server-events-overview
- type: Webhooks
url: asyncapi/chord-commerce-events.yml
- type: Authentication
url: authentication/chord-commerce-authentication.yml
- type: ErrorCatalog
url: errors/chord-commerce-error-codes.yml
- name: Chord Audiences API
description: Read API for activated audiences. Once the Dynamic Audiences API destination is enabled on an account, a sync
mirrors a custom audience into the API and a server-side GET on /audiences returns that user's audience memberships with
their attached attributes. Keyed by the CDP Blended User ID passed in the Chord-User-Id header and authenticated with
a bearer token issued by Chord. Intended for on-site personalization; Chord's docs state it must always be called server-side.
humanURL: https://docs.chord.co/audiences-api
baseURL: https://analytics.api.chord.co
tags:
- Audiences
- Personalization
- CDP
properties:
- type: Documentation
url: https://docs.chord.co/audiences-api
- type: Authentication
url: authentication/chord-commerce-authentication.yml
- type: ErrorCatalog
url: errors/chord-commerce-error-codes.yml
common:
- type: License
name: MIT
url: https://github.com/chordcommerce/chord-copilot/blob/main/LICENSE
- type: DomainSecurity
url: security/chord-commerce-domain-security.yml
- type: Website
url: https://www.chordcommerce.com
- type: Platform
url: https://www.chordcommerce.com/platform
- type: AI
url: https://www.chordcommerce.com/platform/agents
- type: CDP
url: https://www.chordcommerce.com/platform/data-foundation
- type: ContextLayer
url: https://www.chordcommerce.com/platform/context-layer
- type: Documentation
url: https://docs.chord.co
- type: OMSDocumentation
url: https://docs.chord.co/oms
- type: APIReference
url: https://docs.chord.co/sdk-api-reference
- type: GettingStarted
url: https://docs.chord.co/analytics-developer-docs
- type: EventTracking
url: https://docs.chord.co/chord-event-tracking
- type: DataPlatform
url: https://docs.chord.co/chord-data-platform
- type: Copilot
url: https://docs.chord.co/chord-copilot-chat
- type: AnthropicIntegration
url: https://docs.chord.co/chord-ai-models-powered-by-anthropic
- type: MCPServer
url: mcp/chord-commerce-mcp.yml
- type: AgentSkill
url: skills/_index.yml
- type: LLMsTxt
url: llms/chord-commerce-llms.txt
- type: Packages
url: packages/chord-commerce-packages.yml
- type: SDKs
url: packages/chord-commerce-packages.yml
- type: Authentication
url: authentication/chord-commerce-authentication.yml
- type: OAuthScopes
url: scopes/chord-commerce-scopes.yml
- type: WellKnown
url: well-known/chord-commerce-well-known.yml
- type: Conventions
url: conventions/chord-commerce-conventions.yml
- type: ErrorCatalog
url: errors/chord-commerce-error-codes.yml
- type: Conformance
url: conformance/chord-commerce-conformance.yml
- type: Lifecycle
url: lifecycle/chord-commerce-lifecycle.yml
- type: StatusPage
url: https://status.chord.co
- type: ChangeLog
url: changelog/chord-commerce-changelog.yml
- type: ReleaseNotes
url: https://chord.launchnotes.io
- type: Webhooks
url: asyncapi/chord-commerce-events.yml
- type: Components
url: components/chord-commerce-components.yml
- type: DataModel
url: data-model/chord-commerce-data-model.yml
- type: Plans
url: plans/chord-commerce-plans-pricing.yml
- type: RateLimits
url: rate-limits/chord-commerce-rate-limits.yml
- type: Blog
url: https://www.chordcommerce.com/resources/insights
- type: CaseStudies
url: https://www.chordcommerce.com/resources/case-studies
- type: Integrations
url: https://www.chordcommerce.com/integrations
- type: About
url: https://www.chordcommerce.com/about
- type: Support
url: https://www.chordcommerce.com/faq
- type: Pricing
url: https://www.chordcommerce.com/request-a-demo
- type: Demo
url: https://www.chordcommerce.com/request-a-demo
- type: Login
url: https://hub.chord.co/login
- type: TermsOfService
url: https://www.chordcommerce.com/legal/terms-of-service
- type: PrivacyPolicy
url: https://www.chordcommerce.com/legal/privacy-policy
- type: SecurityMeasures
url: https://www.chordcommerce.com/legal/security-measures
- type: DataProcessingAddendum
url: https://www.chordcommerce.com/legal/data-processing-addendum
- type: Subprocessors
url: https://www.chordcommerce.com/legal/subprocessors
- type: GitHubOrganization
url: https://github.com/chordcommerce
- type: LinkedIn
url: https://www.linkedin.com/company/chordcommerce
- type: Crunchbase
url: https://www.crunchbase.com/organization/arfa
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
x-enrichment:
date: '2026-08-13'
status: enriched
artifacts_added: 24
pass: local-v1
Chord API — frequently asked questions
Does Chord have an API?
Yes. APIs.io lists 3 APIs from Chord, including Chord MCP, Chord CDP Ingest API and Chord Audiences API.
How do I authenticate with the Chord API?
Chord documents its authentication (4 schemes). The details are profiled on APIs.io as Chord Commerce Authentication.
Does Chord have an MCP server?
Yes. APIs.io lists 1 MCP server for Chord: Chord's hosted MCP server. Gives an MCP client a read-only window into the customer's Chord data warehouse: schema search, saved views, prior question/SQL pairs, org SQL conventions, table preview, re
Is the Chord API ready for AI agents?
Chord has a Kin Score of 48.9 out of 100 (developing) and an Agent Readiness score of 53.6 (agent-ready), scored by API Evangelist on 2026-11-06.
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.
Kin Score
How this is scored →
It updates itself when the score changes. Paste this where you link to your API docs: