Skip to main content
Droplinked’s thesis: meet merchants where they already publish their inventory and project it into agentic surfaces. If you already sell on Droplinked — or connect an existing store — your catalog becomes discoverable and purchasable by AI agents automatically. No re-platforming.
If you’re connecting an existing Shopify store specifically (with step-by-step webhook setup, app-install instructions, catalog sync, and lender-routing pickup), see the dedicated Connect your Shopify store guide.

​
What you get

An ACP product feed

Your products are published to the Stripe ACP product feed so agentic shopping surfaces can ingest them. Ingesters read the delimited artifact; the JSON endpoint is for direct queries — see Feed formats.

MCP tools

Your catalog is queryable through the MCP server by any agent.

Affiliate revenue

Conversions settle through x402 + the 70/20/10 split, so the publishers and agents that surface you are incentivized to.

​
Per-merchant MCP surface

Beyond the platform-wide MCP server, every Droplinked shop is projected as its own path-prefixed MCP surface at mcp.droplinked.com/{shopSlug}/.... An agent that lands on a single storefront can pin to just that shop’s tools — no shop-slug filter argument needed on every call, no risk of fanning out across the catalog.

​
Endpoints (per merchant)

The scoped surface is a REST shim — a plain POST with the tool arguments as the body, no JSON-RPC envelope and no accept: text/event-stream requirement. For the full 38-tool roster, call the platform MCP at https://mcp.droplinked.com/mcp instead; read the roster from tools/list rather than assuming the scoped and platform surfaces match.

​
How agents discover it

Two paths, agent’s choice:
  • Storefront-advertised — your storefront page advertises its MCP URL via a meta tag the agent reads at page-load time:
  • Canonical platform discovery — the platform-wide well-known doc carries a merchantDiscovery.pathTemplate an agent can substitute any shop slug into:
Either way the result is the same: the agent ends up with a shop-scoped tool surface it can call directly. See MCP server for the platform-wide tool inventory the per-merchant surface inherits.
For a complete guide to advertising your storefront’s MCP URL via the <meta name="mcp-url"> tag (with snippets for custom Next.js, React, Shopify Liquid, and generic HTML storefronts), see Storefront MCP Discovery.

​
Steps

1

Publish your catalog

List products on your Droplinked shop (physical, digital, or POD). The public catalog is immediately available via product-v2/public/shop/{shopName} and flows into the ACP feed.
2

Verify the feed

Confirm your items appear in the delimited artifact — the complete catalogue in one file, and the format an ACP ingester reads:
Columns are 1-indexed: 19 is brand, 13 is is_eligible_checkout. The JSON endpoint at apiv3.droplinked.com/feed/acp.json is for direct queries, not ACP ingestion, and it is both cursor-paginated and narrower than the delimited artifact — so a filter over one response can report a false negative.
3

Expose via MCP

Point an agent at the MCP server and confirm search_products / list_shop_products return your catalog. Every JSON-RPC request must accept both media types, or the server answers 406 / -32000 Not Acceptable:
4

Close the purchase loop

Agent purchases route through Stripe ACP / x402. (start_checkout is finalizing as the Stripe ACP enrollment completes — see the MCP status note.)

​
Already hosting elsewhere?

Connecting an existing store surfaces the same catalog through Droplinked’s commerce APIs and the agentic layer — the goal is additive distribution, not migration. See the platform model and API reference for the import/connect surface.