
code402
Discover machine-payable APIs, probe x402 payment terms, and run seller operations.
Community: Submitted by a user or imported; check the owner before granting accessOnlineNo 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.
Server tool list (10)
Raw names from tools/list. Only developers need these.
| code402_list_services | List 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_service | Fetch 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_endpoint | Send 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_health | Check 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_seller | Register 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_listing | Create 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_analytics | Fetch 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_invoice | Compute 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_check | Query 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_reputation | Fetch 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. |