Publish a service

This publish form needs JavaScript. You can also publish via the API: POST /v1/marketplace/services with your X-Seller-Key — see the API docs.

New listing

Name *

Shown on your listing card. Keep it short and clear.

One-line summary

One sentence agents see in search results.

Description

Your seller name (public — one name for all your listings)

Buyers see “by this name” on your card, beside the price. Leave it blank and every listing you own reads “by Unnamed seller” — exactly where a buyer decides whether to trust that price. 1-60 characters, so use your product or company name, never an email address. Already set one? It is filled in for you — editing it here updates it on every listing you own.

How agents connect *

No hosted server? Most MCPs are stdio — pick npm package and list by package name (free).

MCP endpoint URL *

Your public MCP server URL. For paid listings it stays private — agents call you through the gateway (/s/:id). Tip: a stdio server can be hosted by wrapping it with mcp-proxy or supergateway.

Which tool should agents call? (recommended for MCP servers)

If your endpoint is an MCP server, name the tool the gateway invokes on each paid call. Leave blank only if your endpoint is a plain HTTP route. Without it, call_service can't route to a tool.

Listing tips

stdio / npx package? Pick “npm package” — no hosting needed; buyers get a ready npx config.
Free or paid: set the price to 0 for a free listing, or a per-call price (hosted endpoints only).
Paid listings are reached through the gateway (/s/:id) so the 99% / 1% split is enforced and your raw endpoint stays private.
Your listing is live in Browse immediately. The optional Verified badge adds the trust mark and featured eligibility.

Rehearse it: `?dryRun=1`

Add ?dryRun=1 to the publish call and FiatDock runs the entire publish path — field validation, the address-poisoning scan, the publish gate and a live probe of your server — then tells you exactly what a real publish would answer, and creates nothing. It hands back your server's own tool names too, so filling in mcpTool becomes a paste instead of a guess. Repeat it as often as you like.

curl -sS -X POST 'https://fiatdock.com/v1/marketplace/services?dryRun=1' -H 'content-type: application/json' -H 'X-Seller-Key: YOUR_SELLER_KEY' -d '{"name":"Acme Weather MCP","mcpEndpoint":"https://mcp.acme-weather.com","mcpTool":"get_weather","priceUsd":0.01,"category":"data"}'

Click the block to select it, then copy — and swap in your own key and fields; the values above are the same example the form's “Fill an example” button uses, so as written it will report that mcp.acme-weather.com cannot be reached. Signed in here rather than using a key? The same ?dryRun=1 works from your browser session.

It is a rehearsal, not a way past the gate. The real publish applies exactly the same refusals — a dry run only lets you find them for free, before the listing exists.

Who will see it

The moment you publish, your listing is in the catalog JSON, the browse grid and the search_services MCP tool; a callable paid listing is also advertised in llms.txt, /.well-known/x402 and the sitemap. Be clear-eyed about who is looking: most traffic on those surfaces today is automated — crawlers, uptime monitors and x402/MCP indexers discovering the catalog. That is distribution, not a queue of buyers.

Non-custodial: buyers' agents pay you directly via x402. FiatDock never holds your funds.