Service Manifest

Machine-readable service description at /.well-known/agent.json

The service manifest is a machine-readable JSON document that buyer agents use to understand what a merchant sells, at what price, and how to interact.

Endpoint

GET /.well-known/agent.json

Authentication: None — this endpoint is publicly accessible.

Response

{
  "name": "data",
  "description": "Real-time Solana token intelligence",
  "version": "1.0.0",
  "services": [
    {
      "name": "fetch-price",
      "description": "Live token prices via Jupiter API",
      "endpoint": "/api/fetch-price/:token",
      "method": "GET",
      "price": 50000,
      "payment_token": "USDC",
      "payment_network": "solana-devnet"
    },
    {
      "name": "analyze-token",
      "description": "Token security analysis (mint/freeze authority, holder distribution)",
      "endpoint": "/api/analyze-token/:address",
      "method": "GET",
      "price": 100000,
      "payment_token": "USDC",
      "payment_network": "solana-devnet"
    }
  ],
  "reputation_url": "/reputation",
  "payment_address": "YourBase58PublicKeyHere"
}

Response Fields

name · string

Human-readable name for the merchant agent. Configured via AGENT_NAME in .env.

description · string

Short description of the services offered. Configured via AGENT_DESCRIPTION in .env.

services · array

Show Each service object contains:

name · string

Service identifier

description · string

What the service provides

endpoint · string

The x402-gated route path

method · string

HTTP method (GET, POST)

price · number

Cost in token base units (e.g., 50000 = 0.05 USDC)

payment_token · string

Token symbol (e.g., USDC)

payment_network · string

Blockchain network

reputation_url · string

Path to the merchant’s reputation endpoint.

payment_address · string

Solana public key that receives USDC payments.

How Buyer Agents Use This

After discovering a merchant via discover_registry, a buyer agent calls read_manifest to fetch this document. The agent then:

1. Parses the available services
2. Compares prices
3. Selects the service to purchase
4. Uses probe_x402 to confirm on-chain payment details
5. Executes the purchase via pay_x402_invoice