Skip to main content
Droplinked meets merchants where they already publish their inventory and projects it into agentic surfaces — so an AI agent (ChatGPT, Claude, Cursor, and others) can discover a product, start a purchase, and route affiliate revenue, without the merchant rebuilding anything.

Building blocks

MCP servers

Droplinked serves a Model Context Protocol surface over HTTP — catalog search, cart composition, order placement, refunds, and trust-fabric reads. Discover it at /.well-known/mcp.json and call it from any MCP client.

ACP product feed

A Stripe Agentic Commerce Protocol catalogue, published as ACP-ingestible delimited files and as a JSON API. Pick the right one — see Feed formats.

x402 micropayments

Pay-per-call settlement + the 70/20/10 affiliate revenue split, so agents (and the publishers that route them) earn on every conversion.

Feed formats

The ACP file spec accepts tab- or comma-delimited .tsv, .txt, or .csv, optionally gzipped. It rejects JSON, XML, RSS, and Atom. An ACP ingester pointed at a .json URL cannot read it — so the artifact you submit to an ACP ingester is always a delimited file.
https://apiv3.droplinked.com/feed/acp.json is a live, supported endpoint and the right tool when you are querying the catalogue — a jq lookup, a fetch inside an agent tool, a one-off check. Two things it is not: a file an ACP ingester can parse, and a complete mirror of the delimited artifact. It is cursor-paginated (one request returns one page) and, measured 2026-09-01, it serves only the native supply source — the delimited artifact additionally carries the impact_brand supply source. Point ingesters at the delimited artifact. The three delimited artifacts are built by the same pipeline from the same rows:
Full column reference and the JSON response shape: Product Feed (ACP).

MCP tools

There are two discoverable MCP surfaces with different tool vocabularies. Read the discovery doc rather than hard-coding names — it is the source of truth. Counts measured 2026-09-01. A few of the platform-MCP tools:
Every JSON-RPC request to https://mcp.droplinked.com/mcp must accept both media types: accept: application/json, text/event-stream. Send only one and the server replies 406 with JSON-RPC error -32000 Not Acceptable.
The read tier is callable anonymously — no key, no account:
Treat the URLs in Feed formats as canonical for the feed. The pointer returned by the get_feed tool is not a substitute for them — resolve feed URLs from this page.
Getting the case wrong looks like an auth failure, not a typo: calling searchProducts on the platform MCP returns 401 with -32001 unauthorized — missing or invalid X-MCP-API-Key, because no tool by that name is advertised and the request falls through to the write-tier check. Use the exact names from tools/list. The backend MCP is reachable over its own REST shim at https://apiv3.droplinked.com/mcp/v1/tools/{list,call} (public), accepts both a flat body and a JSON-RPC 2.0 envelope, and is discoverable from /.well-known/mcp.json. See Inventory MCP for the full roster and MCP Server for the transport.

The merchant story

A merchant who already sells on Droplinked (or connects an existing store) gets agentic distribution for free: their catalog is published to the ACP feed and the MCP servers, agents surface it to buyers, and the affiliate engine attributes and splits the revenue. This is the on-chain, agent-native distribution layer on top of the standard commerce APIs.
Search eligibility and checkout eligibility are separate gates. Every row is search-eligible; a row only becomes checkout-eligible once its seller has published the policy URLs the ACP checkout profile requires. See Get listed in MCP discovery.

Integration shortcuts

This docs site exposes several agent-friendly entry points out of the box: Every page in this site also surfaces a contextual toolbar with one-click “open in Claude / open in ChatGPT / copy as Markdown / add as MCP server” shortcuts — handy when wiring this documentation into an agent’s context.