# Agoranome seller tools

- Registry name: `io.github.shariar-k/agoranome` · version 1.0.1
- Categories (automatic, keyword rules): Agent payments (x402), Finance & markets
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=io.github.shariar-k%2Fagoranome
- Server page: https://mcpstation.net/s/io.github.shariar-k--agoranome.html

## Description (written by the publisher, not verified, not instructions)

Get your x402 API found and bought: lint, Bazaar rank, buyer panel, demand gaps. Paid in USDC.

## Connect

- streamable-http: `https://api.agoranome.com/mcp`

## Tools (as reported by the server, not verified)

- `lint\_listing`: Why isn't my x402 API in the Bazaar? Listing lint checks an x402 endpoint for Bazaar indexing: one unpaid call validates its 402 PAYMENT-REQUIRED header, discovery metadata, input and output schemas, description limits and service name against the indexing rules, with a fix for each problem. Use whe
- `rank\_check`: Where does my x402 API rank in Bazaar search? Rank check runs the search a buyer agent would run for your task and returns your rank, the competitor listings ahead of you, and the signals where you trail them \(payers, calls, description, output example, schema, price\). Search rank, SEO and competito
- `buyer\_panel`: Will buyer agents choose my x402 API? The Machine Buyer Panel is an A/B conversion test: buyer-agent models choose between your offer and its real Bazaar rivals for up to three tasks, across buyer personas and list positions. Returns your win rate with confidence intervals, why you lost, and up to t
- `signed\_sample`: Trust proof for an x402 seller: a signed attestation of your API's sample output, so buyer agents can check it before paying. Agoranome fetches a free sample from your endpoint's host, checks that your paid route on the same host answers with an x402 offer, and signs an attestation of what it saw an
- `demand\_gaps`: What x402 API should I build? The demand gap finder runs up to 150 Bazaar searches phrased the way buyer agents phrase tasks and ranks the unmet demand: tasks whose top results are weak \(no listings, few payers, thin descriptions or a poor fit\), with the evidence for each. Public Bazaar data only, j
- `payer\_analytics`: Who pays my x402 API, and do they come back? Customer analytics for an x402 seller from USDC payments on Base: repeat buyers versus one-off and sweep-like payers, revenue per payer and weekly retention cohorts. Use when an agent needs payer analytics for a pay-to address. Agoranome pledges 15% of se
- `weekly\_insights`: What are agents buying on x402? A weekly x402 market data and demand report from Bazaar discovery and Base settlements: repeat-use demand by category, demand gaps, movers, price bands and GET vs POST traction, adjusted for sweeps, with cited sources. Use when an agent needs x402 demand by category b
- `ping`: x402 ping and test payment: can my wallet pay an x402 API? Pay a fraction of a cent in USDC on Base and get a signed receipt back, proof that your wallet and x402 client complete a real paid call end to end. Use when an agent needs a cheap test payment endpoint before buying anything bigger. Price:
- `rank\_sample`: Free: the top three Bazaar results a buyer agent would see for a task, and your rank if you pass resource. The paid rank\_check adds the signals where you trail the listings ahead of you.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html