Discovery documents and MCP server

An agent can find, price and call Suede's endpoints without reading a web page. app.suedeai.ai publishes the same three offerings in each format below, so your runtime can use whichever one it already reads. Every document listed answered HTTP 200 on 2026-10-11.

Discovery documents

Document	URL	What it holds
x402 discovery	`/.well-known/x402`, also served byte-for-byte at `/.well-known/x402.json`	`x402Version` 2. Three `resources`, each with its `accepts` payment requirement, an input schema under `extensions.bazaar` and Skyfire token types under `extensions.skyfire`.
OpenAPI 3.1.0	`/openapi.json`	Six operations: the three paid `POST`s and their three free `GET` poll routes. Response codes, the `x402Payment` and `SkyfireJWT` security schemes, and the versioning policy under `info.x-api-versioning`.
Product catalog	`/api/v1/catalog`	A schema.org `ItemList` of three `Product`s with USD offers, plus a `products` array with `price_usdc`, `price_usd_cents`, the fulfillment endpoint and payment methods (`x402` and `stripe_checkout`). One product: `/api/v1/products/{id}`.
Agentic Commerce manifest	`/.well-known/agentic-commerce.json`	Seller details, payment rails (`x402`, `stripe_checkout`, `stripe_link`), the Base network and USDC address, and the catalog index URL.
A2A agent card	`/.well-known/agent-card.json`, also at `/.well-known/agent.json`	"Suede AI Agent", protocol version 1.0, a JSON-RPC interface at `https://app.suedeai.ai/a2a`, and three skills.
AI plugin manifest	`/.well-known/ai-plugin.json`	Auth type `none`, with pointers to `openapi.json` and the MCP server.
LLM summaries	`/llms.txt` and `/llms-full.txt`	Plain-text summaries of the catalog and discovery URLs for language models.

The same ids name each offering everywhere: create_music, agent_video and agent_image are the catalog product ids, the A2A skill ids, the MCP tool names and the OpenAPI operationIds.

Read the x402 document

One request gives you every price, the amount to sign and the required fields:

curl -s https://app.suedeai.ai/.well-known/x402 \
  | jq '.resources[] | {resource, priceUsd, amount: .accepts[0].amount, required: .extensions.bazaar.input.body.schema.required}'

{ "resource": "https://app.suedeai.ai/create-music", "priceUsd": "$0.50", "amount": "500000", "required": ["prompt"] }
{ "resource": "https://app.suedeai.ai/agent/video", "priceUsd": "$4.99", "amount": "4990000", "required": ["prompt"] }
{ "resource": "https://app.suedeai.ai/agent/image", "priceUsd": "$0.15", "amount": "150000", "required": ["prompt"] }

Each resource entry also has a lastUpdated timestamp; all three read 2026-08-30T16:19:22Z on 2026-10-11. The endpoint reference turns these entries into per-endpoint pages.

MCP server

Model Context Protocol clients can list the same catalog from https://app.suedeai.ai/api/mcp, a streamable-HTTP JSON-RPC endpoint. On 2026-10-11 it answered initialize with protocol version 2025-06-18 and server name suede-agentic-commerce, version 1.0.0, and tools/list returned five tools:

Tool	What it does
`create_music`	Create Music, $0.50 USDC via x402 on Base.
`agent_video`	Agent Video, $4.99 USDC via x402 on Base.
`agent_image`	Agent Image, $0.15 USDC via x402 on Base.
`skyfire_create_music`	Create Music paid with a Skyfire PAY token scoped to the Create Music seller service; queues a job.
`skyfire_get_music`	Polls a `songId` for the finished track. Free.

For the three x402 tools, tools/call does not run the job. It returns a payment pointer that tells your client where and how much to pay; the client then pays the HTTP endpoint as in the quickstart.

curl -s -X POST https://app.suedeai.ai/api/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"agent_image","arguments":{"prompt":"test"}}}'

The structuredContent of the result, as returned on 2026-10-11:

{
  "paymentRequired": true,
  "protocol": "x402",
  "endpoint": "https://app.suedeai.ai/agent/image",
  "method": "POST",
  "network": "base",
  "chainId": "8453",
  "priceUsdCents": 15,
  "receiver": "0x10FF767043A1723E0BB5B9207bC37D3442cC9E4F",
  "discovery": "https://app.suedeai.ai/.well-known/x402.json"
}

The MCP input schemas list a few fields the OpenAPI spec does not, such as resolution on agent_video. The endpoint pages on this site document the HTTP request bodies from openapi.json.

Publishing your own endpoint

The same discovery formats work for any x402 seller. Three Suede tools help on that side:

x402 Agent Builder: Get Paid Per Call. Build an AI agent on a visual canvas, set a price per call, and get paid in USDC on Base through x402 once you enable payments. Dry runs need no wallet.
Suede ACP/x402 Performance Engine. Score your ACP/x402 readiness in 60 seconds. Free, no account required.
Agentix: x402 AI Agent Earnings Tracker for USDC on Base. The portfolio tracker for the x402 agents you've launched: total USDC earned on Base, calls, per-agent performance, status, and trend.

Sources

Each document above, fetched on 2026-10-11, plus live initialize, tools/list and tools/call requests to the MCP server on the same day.