code402

Discover machine-payable APIs, probe x402 payment terms, and run seller operations.

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

    What data it sees

    Do you need an account

    No: the server works without sign-in

    Discover machine-payable APIs, probe x402 payment terms, and run seller operations. Non-custodial.

    How to connect

    How to connect code402 to Claude

    The server address to paste into Claude settings:

    https://mcp.code402.dev/mcp

    1. Open Claude (claude.ai or the desktop app).
    2. Go to Settings → Connectors.
    3. Click Add custom connector.
    4. Paste the server address copied below into Remote MCP server URL and click Add.
    5. In a chat, click + → Connectors and switch the new connector on.

    Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

    Authorization

    After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

    How to connect code402 to ChatGPT

    The server address to paste into ChatGPT settings:

    https://mcp.code402.dev/mcp

    1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
    2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
    3. Open Settings → Connectors and click Create.
    4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
    5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
    6. In a new chat open + → Apps/Connectors and enable the connector.

    OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

    Authorization

    On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

    How to connect code402 to Cursor

    The server address to paste into Cursor settings:

    https://mcp.code402.dev/mcp

    Fastest: click Open in Cursor below and confirm the prompt.

    Manually:

    1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
    2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
    3. Save the file. The server appears in the MCP list; authorize it there if asked.

    Authorization

    If the service needs sign-in, an authorize button appears next to the server in the MCP list.

    Server tool list (10)

    Raw names from tools/list. Only developers need these.

    code402_list_servicesList services on the code402 gateway storefront (GET /v1/services): first-party APIs and third-party seller listings, each with method, URL, USDC price, and network. No account or API key exists or is needed anywhere on the gateway — paid services are accountless, priced per call via x402. Paying for a service requires an x402-capable HTTP client with the buyer's own wallet — this tool only discovers. Returns { total, count, offset, has_more, next_offset?, services: [{ serviceId, name, description, method, url, price, price_usdc_units, network }] }.
    code402_get_serviceFetch a single service from the code402 storefront by its serviceId (as returned by code402_list_services). Returns the same service shape as code402_list_services, or an error naming close matches when the id is unknown.
    code402_probe_endpointSend an unpaid GET to any public https URL and report whether it answers with a valid x402 402 challenge, plus normalized terms { scheme, network, amount (USDC base units), price (dollars), payTo, asset }. Use before budgeting a payment or to liveness-check a listing. No payment is ever sent. Private/internal addresses are rejected.
    code402_gateway_healthCheck the code402 gateway's /healthz: returns { status, service, network } where network is the settlement chain currently configured (e.g. base-sepolia or base).
    code402_register_sellerRegister a seller on the code402 gateway (or update its name — the payout wallet is immutable once set; re-binding requires EIP-191 proof): POST /v1/sellers with { id, wallet, name }. Payments for the seller's listings settle directly to this wallet (non-custodial). Registration is free; fees are 0.099% of settled volume, invoiced monthly against receipts (accrued until $9). Pro is $9/mo at 0% take. Returns { sellerId, wallet, storefront }. Prove wallet ownership later via the gateway's EIP-191 verify-challenge flow.
    code402_create_listingCreate or update a paid listing for a registered seller: POST /v1/sellers/{sellerId}/services with { serviceId, upstream_url, price_usd, method?, description? }. The gateway then serves the listing at /s/{sellerId}/{serviceId} behind an x402 paywall paying the seller's wallet directly. Returns { listing, paid_endpoint }.
    code402_get_seller_analyticsFetch a seller's own settlement analytics (free): GET /v1/sellers/{sellerId}/analytics. Returns { total_settled_calls, gross_usd, unique_buyers, by_service: [{ service_id, calls }] }.
    code402_get_seller_invoiceCompute a seller's platform-fee invoice from settled receipts: GET /v1/sellers/{sellerId}/invoice?since={unix_ms}. Returns { tier, transactions, gross_usdc_units, platform_fee_usdc_units, seller_net_usdc_units, fee_bps }. Amounts are integer USDC base units (6 decimals).
    code402_trust_checkQuery the code402 Atlas index for measured trust evidence on an endpoint or domain: probe-verified liveness (probedAlive), evidence tier (probe vs asserted), and ready-to-pay settlement terms (payTo, asset, CAIP-2 network, integer USDC amountUnits) when measured. Use before letting an agent pay any endpoint. Verified evidence is measured by probes, never self-reported. Returns { count, results: [{ title, url, probedAlive, evidence, settlement? }] }.
    code402_get_agent_reputationFetch an agent's tamper-evident reputation credential from the code402 Atlas rail: GET /v1/agent/{agent_id}/reputation. The credential is an HMAC-signed, expiring (10-minute TTL) bundle over a hash-chained outcome ledger — settled_ok, settled_fail, distinct_hosts, volume_units, reputation_score — verifiable without any shared secret via POST /v1/reputation/verify. Sellers use this to price counterparty risk before serving a new agent.