Plug FMCG HQ into the stack you already run
REST API, webhooks, native connectors, and an MCP server for agentic workflows. Cohort one ships with the integrations founding brands actually need — sequenced by demand, not by vendor partnerships.
Cohort one priority on connector roadmap · Founding pricing locked · REST + webhooks default
Every CPG operations stack is a Frankenstein.
Talk to any CPG operator about their stack and you'll hear the same story: Shopify for DTC, Klaviyo for email, Meta + TikTok for paid, a 3PL portal for fulfillment, an Excel sheet for retail orders, a separate tool for influencer outreach, and three Google Sheets stitched together to make sense of any of it. Nothing talks to anything. Every decision requires a CSV export and a VLOOKUP.
FMCG HQ's Integrations Hub is the connective tissue. Not a new tool replacing existing ones — but the layer that lets sampling, UGC, and operational signal flow into and out of the stack you're already running. Shopify, Klaviyo, Meta Ads, Looker, Snowflake, Slack — wire it once, the data flows continuously.
We're building the connector roadmap with cohort one input. Every integration that ships is one founding brands voted up. Native connectors for the highest-demand tools land first; REST API and webhooks cover everything else from day one of cohort one.
What changes when CPG infrastructure is API-first
With FMCG HQ Integrations
- REST API + webhooks ship with cohort one — day one
- Native connectors for top-demand tools (vote-driven roadmap)
- MCP server for agentic AI workflows (let agents drive sampling, UGC, etc.)
- Scoped API keys with per-team permissions and audit logs
- Webhook event subscriptions for every operational milestone
- Sandbox environment for testing — no impact on production data
Traditional CPG platforms
- API access locked behind “enterprise” tier ($$$)
- Limited or no webhook support
- No MCP / AI-agent compatibility
- API keys single-scope, single-team, no audit logs
- Polling required for state changes
- Sandbox costs extra or doesn't exist
How a cohort one integration ships
Most cohort one brands integrate in under a day once API keys are provisioned.
API key provisioning
- Scoped keys (read-only, write, admin) per use case
- Audit log on every API call
- Sandbox + production environments from day one
Connector or REST
- Native connectors via OAuth flow (no API key juggling)
- REST API with OpenAPI 3.1 spec
- Webhook subscriptions for state changes
Webhook subscription
- Per-event subscription with selective filtering
- Retry logic with exponential backoff
- Signed webhook payloads (HMAC verification)
MCP server (optional)
- MCP-compliant tool exposure for agentic workflows
- Scoped API keys per agent
- Audit log per agent action
Five integration patterns cohort one is shipping
Sync sampling cohorts to your Klaviyo flows
Push UGC assets directly into Meta + TikTok ad accounts
Stream operational signal to Snowflake / BigQuery / Looker
Let agents drive sampling, UGC, and reorder cycles
Sampling readouts and UGC delivered to your team channel
Four developer-grade capabilities
Built for engineering teams that want infrastructure-as-code, not vendor lock-in.
REST API — OpenAPI-spec, documented, sandbox-tested
- OpenAPI 3.1 spec with auto-generated SDKs
- TypeScript, Python, and Go client libraries
- Sandbox environment identical to production
- Rate limits scaled to actual usage, not gating
Webhooks — signed, retried, observable
- HMAC-signed payloads for verification
- Exponential-backoff retry on delivery failure
- Per-event subscription with filtering
- Delivery-status dashboard for debugging
Scoped API keys — per-team, audited, rotatable
- Scoped permissions (read / write / admin)
- Per-key audit log
- One-click rotation
- Endpoint allowlist per key
MCP Server — AI agents drive FMCG HQ natively
- MCP-compliant tool exposure
- Compatible with Claude, ChatGPT, and MCP-aware agents
- Scoped per-agent permissions
- Audit log per agent action
“The most important integration is the one a founder didn't have to ask for. We ship REST API and webhooks day one, then build native connectors for the tools cohort one votes up. We don't sell integrations as upsells.”
What founding brands get from Integrations
API access from cohort one onboarding. No upgrade tier required.
Founding brands vote on which connectors ship first. We build what cohort one needs.
Test environment included. No cost, no rate-limit games.
Model Context Protocol server for agentic workflows. Cohort one access included.
Common questions we get
Have more questions? Please contact our team.
Related reading
Get API access in cohort one
Private beta · REST + webhooks day one · founding pricing locked · MCP server for AI agents · sandbox included.