paidfor

dev.paidforPublished by paidfor.devOfficial publisherv0.4.0Updated Oct 30, 2026

Check an x402 seller before paying: verdict, failure rate and evidence from paid calls on Base.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingFinanceSecurity & Monitoring

Overview

AI-generated overview

Checks x402 API sellers before an agent pays them, returning a verdict, failure rate and evidence from real paid calls on Base.

What you can do
  • Check a seller before paying: get a verdict (avoid, caution, ok, unknown) for an x402 resource URL or seller domain, with failure rate and evidence.
  • Find reliable sellers: list sellers with zero failures across at least 30 paid calls, with domain, category, call counts, failure-rate bound and median USDC price.
  • Track index changes: see verdict changes, new failures, moved quotes, changed pay-to addresses, new sellers and seller replies.
  • Report a payment outcome: submit the resource URL, settlement transaction hash and result after your own wallet has paid.
When to use it
Use it when an agent is about to pay an x402 API per call in USDC on Base, when a request returned HTTP 402 and you are deciding whether to retry, or when choosing among candidate sellers for a task.
Requirements
Runs as a remote streamable HTTP endpoint or as a local npm package over stdio. No account, API key, environment variable or header is declared; the tools read a public index. Reporting a payment needs the resource URL, settlement transaction hash and outcome.
Before you install
The tools only read a public index and send the URL being checked; reports send the resource URL, transaction hash, outcome and optional quote. It does not move money, but it does not guarantee a seller's future behavior, and an unknown verdict means no data rather than a safe seller. Reports count only once the transaction is verified as a USDC transfer on Base.

Installation

In SourceWeft

  1. Open paidfor in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.paidfor%2Fpaidfor/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "paidfor": {
      "type": "http",
      "url": "https://mcp.paidfor.dev/mcp"
    }
  }
}

README

This repository has no README.

Tools

4

check_x402_seller

Check an x402 seller before paying

Call this before any x402 payment, before retrying a request that answered HTTP 402, or whenever the user is about to buy an API call with USDC on Base or names an API they intend to pay per call. Returns a verdict (avoid, caution, ok, unknown), one sentence to act on, the seller's paid-call count and failure rate with a 95% interval, listed price, modal quote and max overcharge ratio when known, and links to the seller page and raw evidence.

Parametersurlrequired

list_reliable_sellers

List reliable pay-per-call API sellers

Call this when choosing among sellers for a task, or when the user asks for a safe or reliable API. Returns sellers with zero failures across at least 30 paid calls, most-called first. For each: domain, category, paid-call count, the 95% upper bound on its failure rate, median quoted price in USDC, USDC paid to it in the last 30 days, when it was last seen, and its paidfor seller page.

Parameterslimitcategory

recent_changes

Recent changes to x402 sellers

Call this when the user asks what changed, or before relying on a verdict older than a day. Returns recent changes, newest first: verdict changes, new failures by type, moved quotes, changed pay-to addresses, sellers added or reaching 30 paid calls, published seller replies, the operator-reported series maturing or disagreeing with ours. Each change has its time, type, seller domain, seller page and type-specific details (for example the old and new quote).

Parametershostsince

report_x402_payment

Report an x402 payment outcome

After your agent pays an x402 seller with any wallet, report what came back. Needs the resource URL, the settlement transaction hash and the outcome. Free, no account, no key; the report counts only with on-chain proof.

Parametersurlrequiredoutcomerequiredtx_hashrequiredhttp_statusquoted_usdc

Version history

1
  1. v0.4.0LatestOct 30, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Paidfor integrations

paidfor

Published by GitHub account sarmadahsan

Looks up x402 sellers in a public index of paid-call reliability, giving a verdict, failure rate and evidence before an assistant pays an API in USDC on Base.

Streamable HTTPWeb executable
Web Search & Scraping3 toolsOct 29, 2026