Chord website screenshot

Chord

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

46.2/100 developing ▬ flat Agent 48/100 agent ready Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
3 APIs 1 MCP Servers
CommerceComposable CommerceHeadless CommerceOrder ManagementOMSCustomer Data PlatformCDPEvent TrackingCommerce AnalyticsCustomer Lifetime ValueAI AgentsCommerce CopilotSolidusSpreeRuby on RailsShopifyDirect to Consumer

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
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.
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/chord-commerce: 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 3

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

Chord MCP

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

Chord CDP Ingest API

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

Chord Audiences API

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

MCP Servers 1

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

Chord MCP Server

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

MCP SERVER

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Chord Commerce Rate Limits

0 limits

RATE LIMITS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Security Posture 2

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

Chord Commerce Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Chord Commerce Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Get Started 3

Portal, sign-up, and the first successful call

Documentation 3

Reference material describing how the API behaves

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 7

Pagination, idempotency, versioning, errors, and events

Scroll for all 7

Build 4

SDKs, sample code, and the tooling you integrate with

Access & Security 4

Authentication, authorization, and security posture

Operate 5

Status, limits, changes, and where to get help

Commercial 5

Pricing, plans, and the legal terms of use

Company 5

The organization behind the API

Other 10

Properties that don't map to a standard resource type

Scroll for all 10

Source (apis.yml)

apis.yml Raw ↑
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: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source: []
  generated: '2026-07-22'
  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

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