Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Agoranome buyer checks and market data

REMOTE · API.AGORANOME.COM

Free tools for agents that pay with x402: the fair pick, a check before paying, buyers' reports.

+1 this week 75 Trust /100

Last scanned (13 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability73
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 4018 tokens (~223/item across 18 items; 17 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management28
  • Stability check failed: schema churn in the 27 days we've observed: 8 tool removals, 0 breaking changes, 0 auth/transport breaks, 12 additions. See how to fix → Fail
Tool Coverage99
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 97% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 19 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 25 to 28.

  • 19 Nov 26 −1
    • A breaking change shipped without a version bump: still 1.0.4 ▼ security
    • Tool “payer_mix” was removed ▼ security
    • Tool “fund_commons” was removed ▼ security
    • Tool “insights_page” was removed ▼ security
    • Tool “mandate_check” was removed ▼ security
    • Tool “payer_analytics” was removed ▼ security
    • Tool “pick_odds” was removed ▼ security
    • Tool “repeat_demand” was removed ▼ security
    • Tool “research_brief” was removed ▼ security
    • Tool “row_set” was removed ▼ security
    • Tool “server_standing” was removed ▼ security
    • Tool “solana_reach” was removed ▼ security
    • Tool “status_credential” was removed ▼ security
    • Tool “survival_odds” was removed ▼ security
    • Tool “weekly_insights” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “ping” rewrote its description, which is the text the model reads security
    • Tool “price_position” rewrote its description, which is the text the model reads security
    • Tool “proof_value” rewrote its description, which is the text the model reads security
    • Tool “which_delivers” rewrote its description, which is the text the model reads security
    • Schema quality: 310 → 223 ▲ functional
    • “fair_pick” reworded the description of “rule” cosmetic
    • “proof_value” dropped the optional parameter “kyapay-token” cosmetic
  • 18 Nov 26 0
    • Tool “server_standing” rewrote its description, which is the text the model reads security
    • Tool “which_delivers” rewrote its description, which is the text the model reads security
    • Tool “server_standing” changed its title: MCP server standing (answers from 17 Nov 2026) → MCP server standing cosmetic
    • Tool “which_delivers” changed its title: Which paid offers deliver (not answering yet) → Which paid offers deliver cosmetic
  • 17 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “buyer_check” rewrote its description, which is the text the model reads security
    • Tool “dispute_pack” rewrote its description, which is the text the model reads security
    • Tool “fair_pick” rewrote its description, which is the text the model reads security
    • Tool “price_position” rewrote its description, which is the text the model reads security
    • Tool “rank_sample” rewrote its description, which is the text the model reads security
    • Tool “repeat_demand” rewrote its description, which is the text the model reads security
    • Tool “solana_reach” rewrote its description, which is the text the model reads security
    • Tool “which_delivers” rewrote its description, which is the text the model reads security
    • “buyer_check” added an optional parameter “network” cosmetic
    • “dispute_pack” added an optional parameter “network” cosmetic
    • “fair_pick” added an optional parameter “rule” cosmetic
    • “response_scan” added an optional parameter “payment_tx” cosmetic
    • “which_delivers” added an optional parameter “network” cosmetic
    • “buyer_check” reworded the description of “tx” cosmetic
    • “dispute_pack” reworded the description of “tx” cosmetic
    • “insights_page” reworded the description of “page” cosmetic
    • “response_scan” reworded the description of “share” cosmetic
    • Tool “which_delivers” changed its title: Which paid offers deliver → Which paid offers deliver (not answering yet) cosmetic
  • 16 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “fund_commons” rewrote its description, which is the text the model reads security
    • Tool “insights_page” rewrote its description, which is the text the model reads security
    • Tool “payer_analytics” rewrote its description, which is the text the model reads security
    • Tool “payer_mix” rewrote its description, which is the text the model reads security
    • Tool “pick_odds” rewrote its description, which is the text the model reads security
    • Tool “ping” rewrote its description, which is the text the model reads security
    • Tool “price_position” rewrote its description, which is the text the model reads security
    • Tool “proof_value” rewrote its description, which is the text the model reads security
    • Tool “repeat_demand” rewrote its description, which is the text the model reads security
    • Tool “research_brief” rewrote its description, which is the text the model reads security
    • Tool “row_set” rewrote its description, which is the text the model reads security
    • Tool “server_standing” rewrote its description, which is the text the model reads security
    • Tool “survival_odds” rewrote its description, which is the text the model reads security
    • Tool “weekly_insights” rewrote its description, which is the text the model reads security
    • Tool “which_delivers” rewrote its description, which is the text the model reads security
    • Schema quality: 253 → 306 ▼ functional
    • New tool “mandate_check” functional
    • New tool “solana_reach” functional
    • New tool “status_credential” functional
    • “row_set” added an optional parameter “network” cosmetic
    • “pick_odds” reworded the description of “category” cosmetic
    • “pick_odds” reworded the description of “price” cosmetic
    • “price_position” reworded the description of “category” cosmetic
    • “price_position” reworded the description of “price” cosmetic
    • “price_position” reworded the description of “resource” cosmetic
    • “proof_value” reworded the description of “price” cosmetic
    • “repeat_demand” reworded the description of “category” cosmetic
    • “survival_odds” reworded the description of “category” cosmetic
    • “survival_odds” reworded the description of “price” cosmetic
    • “survival_odds” reworded the description of “resource” cosmetic
    • “which_delivers” reworded the description of “category” cosmetic
  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 21.

  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 11 to 14.

  • 11 Nov 26 −6
    • Stability: 0.53 → fail ▼ security
    • Tool “buyer_drill” was removed ▼ security
    • Tool “buyer_panel” was removed ▼ security
    • Tool “certify_continuous” was removed ▼ security
    • Tool “certify_offer” was removed ▼ security
    • Tool “conformance_check” was removed ▼ security
    • Tool “demand_gaps” was removed ▼ security
    • Tool “model_watch” was removed ▼ security
    • Tool “rank_check” was removed ▼ security
    • Tool “rank_watch” was removed ▼ security
    • Tool “signed_sample” was removed ▼ security
    • Tool “vendor_watch” was removed ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “buyer_check” rewrote its description, which is the text the model reads security
    • Tool “dispute_pack” rewrote its description, which is the text the model reads security
    • Tool “lint_listing” rewrote its description, which is the text the model reads security
    • Tool “plan_quote” rewrote its description, which is the text the model reads security
    • Tool “response_scan” rewrote its description, which is the text the model reads security
    • Tool “spend_audit” rewrote its description, which is the text the model reads security
    • Tool “pick_odds” rewrote its description, which is the text the model reads security
    • Tool “which_delivers” rewrote its description, which is the text the model reads security
    • Schema quality: 288 → 253 ▲ functional
    • Server version: 1.0.3 → 1.0.4 functional
    • New tool “fair_pick” functional
    • “buyer_check” dropped the optional parameter “kyapay-token” cosmetic
    • “dispute_pack” dropped the optional parameter “kyapay-token” cosmetic
    • “lint_listing” dropped the optional parameter “kyapay-token” cosmetic
    • “plan_quote” dropped the optional parameter “kyapay-token” cosmetic
    • “response_scan” dropped the optional parameter “kyapay-token” cosmetic
    • “spend_audit” dropped the optional parameter “kyapay-token” cosmetic
    • Tool “pick_odds” changed its title: Pick odds (not answering yet) → Pick odds cosmetic
    • Tool “which_delivers” changed its title: Which paid offers deliver (not answering yet) → Which paid offers deliver cosmetic
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://api.agoranome.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=agoranome.com CN=YE2,O=Let's Encrypt,C=US 22 Oct 2026 20 Jan 2027 ECDSA 256 ECDSA-SHA384 6f107f6fd7966fda3ac2a5cd25ed15cee9f
SANs: *.agoranome.com, agoranome.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.agoranome.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
agoranome.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.agoranome.com/mcp Verified 200
http (plaintext) http://api.agoranome.com/mcp HTTPS enforced 301 https://api.agoranome.com/mcp
MCP tools · 17 exposed · ~3,289 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
agent_payments_weekly ~107

Free: Agoranome Weekly's edition for a week (the newest if week is left out): real demand on Base (payments into the busiest Bazaar sellers with catalog sweeps and self-payments taken out), the Bazaar's sellers, new sellers, price index and Fair Offer share, and x402 SDK downloads, with the method version and how to cite it. CC BY 4.0.

NameTypeReqDescription
week––ISO week, e.g. 2026-W44

No output schema declared.

No examples provided.

buyer_check ~289

Use when a buyer agent is about to pay an x402 seller it hasn't paid before, or above its usual amount: a signed verdict from what Agoranome holds: the Fair Offer block and certification, the pay-to and since when, OFAC sanctions on it, Google Web Risk on the URL, price against listing and quote, verified deliveries, policy tiers met. Give url= up to 20 times to rank sellers safest first. With tx=, settlement proof: the USDC transfer on Base, Monad or Solana and if it matched the quote. Free: no payment is asked.

NameTypeReqDescription
accept_proof––Your requirements, as an Accept-Proof value
expected_price––The quoted price in USD
max_pricenumber–Your per-call cap in USD
network––Settlement mode: eip155:8453 (Base, the default), eip155:143 (Monad) or solana
pay_to––The quoted pay-to address
shareboolean–Settlement mode: publish the buyer-side receipt in the evidence commons
tx––Settlement mode: the payment's transaction hash on Base or Monad, or its signature on Solana
url–yesThe x402 offer's URL, or a list of up to 20 offer URLs to check in one call for the same price, listed safest first

No output schema declared.

No examples provided.

check_fair_offer ~101

Free: check any x402 offer's Fair Offer block from outside, without paying. Each of the eight Fair Offer rules comes back verified, declared, contradicted or not claimed. Pass accept_proof (e.g. "sample=attested; price<=listing") to learn whether the offer meets a buyer's requirements.

NameTypeReqDescription
accept_proof––Optional Accept-Proof value
urlstringyesPublic https URL of the paid endpoint

No output schema declared.

No examples provided.

check_offer ~128

Free: would a buyer's policy pay this x402 offer? Applies Agoranome's open buyer policy (a price cap, the listing price, no instructions in the listing, and a proof tier: any, sampled or delivered) and returns allowed or refused with the reasons. Nothing is paid or signed.

NameTypeReqDescription
expected_price_usd––A quoted price, if any
max_price_usdnumber–The buyer's price cap
tierstring–Proof tier: any, sampled or delivered
urlstringyesPublic https URL of the paid endpoint

No output schema declared.

No examples provided.

dispute_pack ~278

Use when a buyer agent was charged by an x402 seller and not served: given the payment's transaction hash, the seller URL, the accepted 402 and the response, get the settlement on Base, Monad or Solana, the Fair Offer terms at quote time (failed calls free, receipts, refunds), what Agoranome observed of that seller in that hour, the seller's published contact and a draft claim addressed to it, all signed. Free: no payment is asked.

NameTypeReqDescription
claim––What went wrong, in your words
expected_price_usd–––
network––Where the payment settled: eip155:8453 (Base, the default), eip155:143 (Monad) or solana
offer––The accepted 402 as received
pay_to–––
response––status, body or body_sha256, headers, received_at
sellerstringyesThe x402 offer's URL
ticket––Optional: true to get a ticket instead of waiting. The run then has minutes instead of 85 s and waits for a busy slot; the paid answer is the ticket, and its result is free with the job_status tool.
txstringyesThe payment's transaction hash on Base or Monad, or its signature on Solana

No output schema declared.

No examples provided.

fair_pick ~251

Which paid API should my agent call for this job? Paid x402 and MPP endpoints that fit a job in plain words, under your price per call, ranked by a published rule no seller can pay for: only offers that answered payable this week, those that asked what they list first, then a Fair Offer block, then the closer fit, then the lower price, two places a seller at most. From the inspector's signed weekly tables; anyone can recompute it. Free at agoranome.com/pick. Free: no payment is asked.

NameTypeReqDescription
budget_usd––Optional: the most to pay for one request, in USD
jobstringyesWhat the endpoint should do, in plain words
kyapay-tokenstring–A Skyfire pay or kya-pay token made for Agoranome's service, from a client that can't set the kyapay-token header. Leave it out when paying with x402 or the header.
limitinteger–How many to return
market––Optional: one market only
rule––Optional: pick-2 (the default, the inspector's public rule) or pick-1, its first

No output schema declared.

No examples provided.

job_status ~80

Free: a ticket's standing, and its result once the run is done. A slow tool called with ticket=true answers with a job; pass its id here as often as you like. A failed run says why and when it will be tried again; it's owed a result.

NameTypeReqDescription
job_idstringyesThe job's id, from the ticket

No output schema declared.

No examples provided.

lint_listing ~154

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 and the fixed 402 ready to paste, graded as the weekly report card would grade it. Also lints A2A agent cards. Use when an agent needs to lint an x402 listing or A2A agent card before its first sale. Free: no payment is asked.

NameTypeReqDescription
urlstringyesPublic https URL of the paid endpoint, or of an A2A agent card (/.well-known/agent-card.json)

No output schema declared.

No examples provided.

ping ~262

x402 test payment: can this wallet pay an x402 API? A paid call of a fraction of a cent in USDC on Base or Solana that returns a signed receipt, proof that the wallet, its spending limit and its x402 client (an AgentCore payments session, a CDP or Privy wallet, or any other client) complete a real paid call end to end, plus what Agoranome already knows about the wallet. For an agent's first payment, before it buys anything bigger. Price: $0.001 in USDC per call, paid with x402 inside the tool call. Same price over HTTP, which any x402 client pays without MCP (prefer it if your client pays HTTP 402s): GET https://api.agoranome.com/v1/machine/ping. Or send a Skyfire pay or kya-pay token in the kyapay-token header (or in this tool's kyapay-token argument), and this tool charges $0.001 to it. Failed calls aren't charged.

NameTypeReqDescription
kyapay-tokenstring–A Skyfire pay or kya-pay token made for Agoranome's service, from a client that can't set the kyapay-token header. Leave it out when paying with x402 or the header.

No output schema declared.

No examples provided.

plan_quote ~140

Use when a buyer's planner agent is about to start a batch of paid x402 calls: post a plan of seller URLs and call counts and get the total cost, each seller's listing and certification state, its expected failure share from reconciled receipts, the fit against your caps (per call, per seller, total, policy tier), and every certified seller in the same category sorted by price with the sort key stated. Free: no payment is asked.

NameTypeReqDescription
caps––max_price_usd, max_per_seller_usd, max_total_usd, tier
planarrayyesLines of {seller: URL, calls: n}

No output schema declared.

No examples provided.

price_position ~364

Is this x402 seller's price high or low for its category? One signed number for the moment before paying: where a price per call sits among the established sellers in the same category, with its 95% range, the same place counted by calls, the category's median, p10 and p90, the seller count and the four newest weeks. Takes a category and the price asked, or the listing's URL. Asked again with its ETag, an unchanged answer is a free 304. Price: $0.001 in USDC per call, paid with x402 inside the tool call. Same price over HTTP, which any x402 client pays without MCP (prefer it if your client pays HTTP 402s): GET https://api.agoranome.com/v1/facts/price-position?category=web_search&price=0.01. Or send a Skyfire pay or kya-pay token in the kyapay-token header (or in this tool's kyapay-token argument), and this tool charges $0.001 to it. Failed calls aren't charged.

NameTypeReqDescription
category––Category, such as web_search
if_none_match––Send the answer's ETag back in If-None-Match (over MCP, the if_none_match argument): while the answer is unchanged it comes back as a free 304 Not Modified.
kyapay-tokenstring–A Skyfire pay or kya-pay token made for Agoranome's service, from a client that can't set the kyapay-token header. Leave it out when paying with x402 or the header.
price––Price per call in USD, such as 0.01
resource––Or your listing's URL, in place of category and price

No output schema declared.

No examples provided.

proof_value ~191

What is a proof worth at my x402 price? One signed number: the premium buyer-agent models gave a cue (a passed certification, an attested sample, pay on delivery, signed receipts, a pledge, the data-not-instructions declaration, or a fake payer count, urgency or an authority claim), in dollars at your price, with its 95% range and whether it's beyond chance, from the newest readable price-of-proof run, and only near the listing prices that run tested. Free: no payment is asked.

NameTypeReqDescription
cuestringyesThe proof or manipulation to price
if_none_match––Send the answer's ETag back in If-None-Match (over MCP, the if_none_match argument): while the answer is unchanged it comes back as a free 304 Not Modified.
pricenumberyesPrice per call in USD, such as 0.01

No output schema declared.

No examples provided.

rank_sample ~57

Free: the top three Bazaar results a buyer agent would see for a task, and your rank if you pass resource.

NameTypeReqDescription
resourcestring–Your listed resource URL
taskstringyesWhat a buyer agent is searching for

No output schema declared.

No examples provided.

registered_agent_card ~98

Free: check an ERC-8004 agent on Base from outside, by its id in the Identity Registry: whether its registration file is valid and points back to it, whether its https endpoints answer and their domains list it, whether its x402 offer or A2A agent card passes the lint, and how concentrated its Reputation Registry feedback is. Nothing is paid or written.

NameTypeReqDescription
agent_idintegeryesThe agent's id on Base

No output schema declared.

No examples provided.

response_scan ~198

Use when a buyer agent is about to act on a paid x402 response: post the body, or passages of it, with the seller's URL and get back instruction-like passages aimed at an agent, hidden characters, exfiltration links, a mismatch against the seller's declared output example, and whether its "data, never instructions" claim held. Nothing posted is stored; with share=true a contradicted claim becomes evidence on the seller's record, as hashes. Free: no payment is asked.

NameTypeReqDescription
body––The paid response body
payment_tx––With share: your payment for this response on Base, settled in the last 24 hours
sellerstringyesThe x402 offer's URL the response came from
shareboolean–Let a contradicted claim count as evidence on the seller's record (hashes only); needs payment_tx
spans––Or: passages of the body

No output schema declared.

No examples provided.

spend_audit ~189

Use when a buyer agent or its operator must account for an x402 wallet's spending: a statement for a buyer wallet on Base. Every USDC payment checked against the payee's listed Bazaar price (above listed, oversize 10x or more, unlisted), spend and calls per seller, duplicate payments within a minute, payments after a seller's listing vanished or its pay-to changed, sellers whose certification failed since, whether the wallet looks sweep-like, and a CSV of every payment. Free: no payment is asked.

NameTypeReqDescription
daysinteger–Days to look back
ticket––Optional: true to get a ticket instead of waiting. The run then has minutes instead of 85 s and waits for a busy slot; the paid answer is the ticket, and its result is free with the job_status tool.
walletstringyesBuyer wallet address on Base

No output schema declared.

No examples provided.

which_delivers ~402

Before paying one of several x402 tools for the same task: which ones deliver? The five offers in a category most likely to deliver at their listed terms, by odds from Agoranome's own paid calls, with price, listing and the order rule stated. Sellers the evidence can't tell apart rotate daily, and the answer says whether the odds are validated yet. Takes a category, an optional price cap and network. Read from the daily deliver feed: no new spend, no model call, refused unpaid when stale. Price: $0.002 in USDC per call, paid with x402 inside the tool call. Same price over HTTP, which any x402 client pays without MCP (prefer it if your client pays HTTP 402s): GET https://api.agoranome.com/v1/facts/delivers?category=web_search. Or send a Skyfire pay or kya-pay token in the kyapay-token header (or in this tool's kyapay-token argument), and this tool charges $0.002 to it. Failed calls aren't charged.

NameTypeReqDescription
categorystringyesCategory, such as web_search
explore––Optional: give the fifth place to the most recently listed seller with an attested sample and no probe yet, labelled exploration
if_none_match––Send the answer's ETag back in If-None-Match (over MCP, the if_none_match argument): while the answer is unchanged it comes back as a free 304 Not Modified.
kyapay-tokenstring–A Skyfire pay or kya-pay token made for Agoranome's service, from a client that can't set the kyapay-token header. Leave it out when paying with x402 or the header.
max_price––Optional: only offers at or under this price per call in USD
network––Optional: only offers whose listing takes USDC on this network's mainnet, at their price there

No output schema declared.

No examples provided.

Install

How do I install the Agoranome buyer checks and market data MCP server?

Agoranome buyer checks and market data is a hosted endpoint at https://api.agoranome.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.agoranome.com

# add to Claude Code
claude mcp add --transport http agoranome-agoranome 'https://api.agoranome.com/mcp'
Common questions

What is the Agoranome buyer checks and market data MCP server?

Agoranome buyer checks and market data is an MCP server listed in the public MCP registry as io.github.Agoranome/agoranome. Free tools for agents that pay with x402: the fair pick, a check before paying, buyers' reports. This page covers its hosted endpoint (https://api.agoranome.com/mcp).

Is the Agoranome buyer checks and market data MCP server safe to use?

Agoranome buyer checks and market data scores 75 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Agoranome buyer checks and market data MCP server expose?

Agoranome buyer checks and market data exposes 17 tools: ping, price_position, which_delivers, fair_pick, lint_listing, and 12 more. Their descriptions and schemas cost roughly 3,289 tokens of context every time the server is loaded.

Does the Agoranome buyer checks and market data MCP server require authentication?

No. We connected to Agoranome buyer checks and market data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Agoranome buyer checks and market data MCP server still maintained?

Agoranome buyer checks and market data is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Agoranome buyer checks and market data MCP server?

VerifyMCP ran 13 checks on Agoranome buyer checks and market data, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.