> ## Documentation Index
> Fetch the complete documentation index at: https://docs.droplinked.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect your store

> Make a merchant's existing inventory agent-shoppable — meet customers where the agents already are.

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.

<Note>
  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](/agentic/connect-shopify) guide.
</Note>

## What you get

<CardGroup cols={3}>
  <Card title="An ACP feed" icon="rss">
    Your products are published to the [Stripe ACP feed](/agentic/acp-feed) so agentic shopping
    surfaces can ingest them.
  </Card>

  <Card title="MCP tools" icon="plug">
    Your catalog is queryable through the [MCP server](/agentic/mcp-server) by any agent.
  </Card>

  <Card title="Affiliate revenue" icon="coins">
    Conversions settle through x402 + the 70/20/10 split, so the publishers and agents that
    surface you are incentivized to.
  </Card>
</CardGroup>

## Per-merchant MCP surface

Beyond the platform-wide [MCP server](/agentic/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)

| Endpoint                                              | Purpose                                                                      |
| ----------------------------------------------------- | ---------------------------------------------------------------------------- |
| `GET mcp.droplinked.com/{shopSlug}/manifest`          | Discoverable per-shop manifest (shop metadata + tool URLs)                   |
| `GET mcp.droplinked.com/{shopSlug}/mcp/tools`         | Scoped tool list — same shape as the platform list, pre-bound to this shop   |
| `POST mcp.droplinked.com/{shopSlug}/mcp/tools/{name}` | Invoke a scoped tool (e.g. `search_products`, `start_checkout`) on this shop |

### 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:
  ```html theme={null}
  <meta name="mcp-url" content="https://mcp.droplinked.com/{shopSlug}" />
  ```
* **Canonical platform discovery** — the platform-wide well-known doc carries a
  `merchantDiscovery.pathTemplate` an agent can substitute any shop slug into:
  ```bash theme={null}
  # Agent discovers the platform-wide origin
  curl -s https://mcp.droplinked.com/.well-known/mcp.json | jq .merchantDiscovery

  # Pivot to a specific merchant
  curl -s https://mcp.droplinked.com/your-shop-slug/manifest
  ```

Either way the result is the same: the agent ends up with a shop-scoped tool surface it can
call directly. See [MCP server](/agentic/mcp-server) for the platform-wide tool inventory
the per-merchant surface inherits.

<Note>
  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](/agentic/storefront-mcp-discovery).
</Note>

## Steps

<Steps>
  <Step title="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.
  </Step>

  <Step title="Verify the feed">
    Confirm your items appear in the feed:

    ```bash theme={null}
    curl "https://apiv3.droplinked.com/feed/acp.json" | jq '.items[] | select(.brand=="<your brand>")'
    ```
  </Step>

  <Step title="Expose via MCP">
    Point an agent at the [MCP server](/agentic/mcp-server) and confirm `search_products` /
    `list_shop_products` return your catalog.
  </Step>

  <Step title="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.)
  </Step>
</Steps>

## 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](/concepts/platform-model) and [API reference](/api-reference/introduction)
for the import/connect surface.