Build

Merchants

The Arcus merchant directory lists x402 APIs that settle through Arcus on Arc mainnet. Agents discover them through one JSON catalog; people try them in the browser.

The directory

arcusnetwork.co/merchants shows every listed API with its endpoints, prices and a playground that pays from a connected wallet. Official merchants are run by Arcus Labs and route revenue to the public $ARCUS buyback wallet. Community merchants set their own payTo.

List your API

  1. 1
    Ship an x402 endpoint on Arc mainnet
    Use the Quickstart or the x402-server package. The endpoint must return a 402 with network: eip155:5042 and the Arc USDC asset.
  2. 2
    Open the dashboard
    Go to arcusnetwork.co/dashboard and connect the wallet that will own the listing. Writes are signed messages, so there is no password.
  3. 3
    Describe the merchant
    Name, description, the payout address and each endpoint's URL, method, price and parameters. The listing appears in the directory and the catalog as soon as it is saved.
  4. 4
    Watch settlements
    The dashboard shows verify and settle activity for your endpoints, with transaction hashes on Arc.
Listings are self-serve and unreviewed. Arcus verifies and settles payments; it does not proxy or vouch for the upstream API.

Machine-readable catalog

Agents can read the whole directory from one open endpoint. Prices are raw 6-decimal USDC units with a priceUsd convenience field. Metered endpoints quote a ceiling; the 402 carries the exact amount.

GET /api/merchants
sh
curl https://arcusnetwork.co/api/merchants

{
  "facilitator": "https://facilitator.arcusnetwork.co",
  "merchants": [
    {
      "id": "arcus",
      "name": "Arcus Data",
      "network": "eip155:5042",
      "asset": "0x3600000000000000000000000000000000000000",
      "endpoints": [
        {
          "method": "GET",
          "url": "https://arcusnetwork.co/api/merchants/arcus/wallet",
          "title": "Wallet snapshot",
          "pricing": "fixed",
          "price": "2000",
          "priceUsd": 0.002,
          "params": ["address"]
        }
      ]
    }
  ]
}

Payment headers

Arcus merchant routes follow the x402 v2 header names. Servers built on the SDK behave the same way.

HeaderDirectionMeaning
PAYMENT-REQUIREDresponse, 402Base64 JSON with the accepted requirements and resource description.
PAYMENT-SIGNATURErequestBase64 JSON payload with the signed EIP-3009 authorization. X-PAYMENT is accepted as a legacy alias.
PAYMENT-RESPONSEresponse, 200Base64 JSON settlement result including the transaction hash.