Aeron Marketplace MCP server — tools & history
Aeron Marketplace MCP server: observed open status, tool schemas, linked apps and version history.
Aeron Marketplace
Endpoint: https://market.aeron.sh/mcp
Observed status: open. Checked: 2026-10-12T05:05:24+00:00.
Linked apps
- Aeron Marketplace
A read-only catalogue of pay-per-call x402 APIs — search ~760 endpoints across 28 merchants and read their exact payment terms.
Observed tools
- get_endpoint — Everything known about one indexed endpoint, by the id search_endpoints returned: price, chain, token, the wallet the payment settles to, the x402 scheme it speaks, its 30-day usage, and the steps to pay it.
- list_merchants — Every merchant in the indexed directory, with how many endpoints it publishes, its price range, its 30-day usage and the categories it covers, plus totals for the directory as a whole. Read this to see who is on the rail before searching one merchant by host.
- list_services — Aeron's own listed services: endpoints whose merchant signed a listing here. Unlike indexed endpoints, these are called through market.aeron.sh, which forwards the request and accrues a take-rate in its ledger — the payment itself still settles to the merchant's own wallet. Returns the absolute URL to call, the price, and that wallet.
- search_endpoints — Search the machine-payable (x402) API endpoints Aeron indexes from the public network: the Coinbase Bazaar and Circle's Agent Marketplace catalogue. Every result is an endpoint an agent can call and pay for per request — no account, no API key, no subscription. `payable: true` rows take USDG on Robinhood Chain and an Aeron wallet can pay them as they stand; `payable: false` rows name the chain and USDC they take instead. Results carry the price, currency, chain, the merchant wallet the payment settles to, and how much the endpoint was used in the last 30 days: payable first, then most-used. Aeron does not stand between the buyer and these endpoints and takes nothing from them.
Data as of 2026-10-12T05:05:24+00:00.
OpenApps records store listings and observed changes. Store ranks are not download counts; launch dates may be derived or use the first observation. Coverage gaps are shown in the interactive catalog.
REST API specification · Guide for AI clients · Manage API keys and MCP connections