mcpField
A
Agoranome seller tools

Agoranome seller tools

Remote
agoranome.comBusiness & Marketing0Updated 3d ago

About Agoranome seller tools

Agoranome’s hosted MCP service checks x402 API offers against the Fair Offer Standard for buyers and their agents. It focuses on verifiable claims such as pricing, samples, and receipts.

Key features

  1. 01Check live offer claims
  2. 02Validate Fair Offer blocks
  3. 03Compare prices with Bazaar listings
  4. 04Check signed receipts and free samples

Use cases

  1. 01Verify an x402 offer before payment
  2. 02Review claims in a seller listing

MCP support

The hosted MCP server exposes a check_offer tool for MCP clients to inspect offers.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://api.agoranome.com/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

The Fair Offer Standard

Seven open rules for selling to AI agents honestly, and a machine-readable way to prove them inside the x402 payment handshake. Version 0.2 (draft).

Human-readable page: https://agoranome.com/standard · JSON: standard.json · Schema: schema/fair-offer-0.2.schema.json

The seven rules

IDRuleWhat it meansHow to check
FO-1Price before paymentAn unpaid call returns an x402 offer (HTTP 402) that states the price, asset, network and pay-to address. Nothing is charged before the buyer has signed that exact offer.check
FO-2Failure is freeA call that fails, times out or returns no result is not settled. The buyer is told so.self-declared
FO-3Receipts are signedEvery paid result carries a receipt signed by the seller's key: what was bought, for how much, and when.check
FO-4Sample before you buyA free sample shows what the paid route returns, and a third party can attest that the sample and the paid offer come from the same host.check
FO-5Honest listingThe listing's description, input schema and output example match what the route really returns. Edits made to win buyers must stay true.check
FO-6Data, never instructionsResponses carry data for the buying agent to use, never instructions aimed at it. A buyer can treat any instruction in a response as an attack.self-declared
FO-7Promises are verifiableAny claim about where revenue goes (a pledge, a split, a donation) comes with a public ledger that a buyer can check per receipt, with on-chain proof of what was given.check

Declaring it (0.2)

A seller's HTTP 402 carries an x402 extension, extensions["fair-offer"], whose info states which rules the offer keeps and where a buyer can check each one:

{
  "version": "0.2",
  "standard": "https://agoranome.com/standard",
  "settlement": {
    "failed_calls": "not_charged",
    "enforced_by": "seller"
  },
  "receipts": {
    "signed": true,
    "verify": "https://api.example.com/receipts/verify"
  },
  "sample": {
    "url": "https://api.example.com/v1/search/sample"
  },
  "listing_price_matches_offer": true,
  "data_not_instructions": true,
  "pledge": {
    "share": 0.15,
    "basis": "settled_revenue",
    "ledger": "https://api.example.com/impact/ledger"
  }
}
  • Keep it stable. Keep the info identical in the unpaid 402 and on the paid retry: x402 clients echo it, and servers reject a payment whose echo drops or changes a field. Put live numbers behind a URL, never in the block.
  • URLs. Each URL is https, or a path relative to the resource URL.
  • Put the fair-offer block in your 402's extensions (see handshake), and link this URL from your llms.txt or agent manifest as "conforms_to": {"fair_offer": "0.2"}.

Asking for proof: Accept-Proof

A buyer says what proof it needs before it pays, in an Accept-Proof request header (or an accept_proof field in the block it echoes in the payment payload):

Accept-Proof: sample=attested; price<=listing; payers_30d>=20
RequirementMet when
sample=anythe offer declares a free sample on its own host
sample=attestedthe sample has an attestation on record
settlement=sellerfailed calls are not charged (the seller's promise)
settlement=railthe payment is captured only on success (auth-capture)
price<=listingthe live price was checked against the Bazaar listing
receipts=signedpaid results carry signed receipts
pledge=ledgera pledge with a public ledger that answers
instructions=nonedeclared data-not-instructions, and no instruction-like text found
payers_30d>=Nat least N distinct payers in 30 days (Bazaar's count)
calls_30d>=Nat least N paid calls in 30 days (Bazaar's count)
deliveries_30d>=Nat least N deliveries in 30 days: receipts confirmed on chain, paid by buyers (evidence commons)

Checking an offer

  • Validate a block: POST https://api.agoranome.com/v1/fair-offer/validate (free)
  • Check a live offer's claims from outside: GET https://api.agoranome.com/v1/fair-offer/check?url=... (free)

Implementations

  • Agoranome (https://agoranome.com): every paid x402 route at api.agoranome.com sends the block, and the hosted MCP server (https://api.agoranome.com/mcp, listed in the official MCP Registry) offers a check_offer tool. That service's source isn't public; this repository holds the open standard.
  • Using it in your 402s? Open an issue with your host and it can be listed here.

Proposing changes

Open an issue or a pull request. Changes to the block's fields go into a new version, so a buyer's policy written for 0.2 keeps working. Corrections, data questions and replication requests can also go to [email protected].

Versions

  • 0.1: The seven rules, declared in an agent manifest or llms.txt.
  • 0.2: The same seven rules, plus the machine-readable fair-offer block in the x402 402 and the buyer's Accept-Proof header.

License

The standard text, schema and examples are licensed under CC BY 4.0. Implement it freely; credit "The Fair Offer Standard, Agoranome".

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.