Skip to main content
Glama

x402 finder: search paid APIs, ranked and live-checked

x402_find
Read-only

Search and discovery of paid x402 API endpoints for a plain-language need, across Ultravioleta DAO x402 Bazaar and 402 Index directories. Dedupes by resource URL; ranks by relevance, verification, uptime, price and recency. Each result: resource URL, short description, USDC price, CAIP-2 networks, sources, verification. The top 3 GET endpoints get a live unpaid check: valid x402 402, live price, networks, canonical USDC, risk flags, OFAC SDN payTo screen, RDAP domain age. Price: $0.01 per successful call, paid in USDC with x402 v2; failed calls and calls that match nothing are not charged.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "x402_find"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesWhat the agent needs, in plain words, 2-120 characters (e.g. weather forecast for a US city, token price, web page to markdown).
limitNoNumber of results, 1-10 (default 5).
networkNoOnly endpoints that accept canonical USDC on this network.
max_priceNoHighest acceptable price per call in USD as a decimal, e.g. 0.01. Listings without a USDC price are left out when set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare readOnlyHint and openWorldHint, and the description adds substantial behavior on top: URL dedupe, a five-factor ranking, the exact result fields, and what the live check covers (402 validity, live price, CAIP-2 networks, OFAC SDN payTo screen, RDAP domain age). It also discloses the billing model — $0.01 per successful call in USDC via x402 v2, with failures and zero-match queries free — which is critical cost information an agent cannot get from the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core search purpose, then ranking, then result shape, then the live-check scope, then pricing — a sensible order with no filler sentences. It is dense and slightly list-like, but every clause carries information an agent needs before paying for a call.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description correctly enumerates the returned fields and the extra data from the live check, so return-value expectations are covered. It leaves one loose end for a paid, open-world tool: it does not explain how the $0.01 charge is settled (wallet/402 handshake) or whether the live check can fail independently of the search.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all four parameters are already documented with examples, enums, and ranges, making 3 the baseline. The description reinforces that q is a plain-language need and that pricing is in USDC, but adds no syntax or filtering nuance beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb pair (search and discovery) plus a specific resource (paid x402 API endpoints) and names the two directories it spans. It also distinguishes itself from the preflight/receipt siblings by framing itself as discovery with only a top-3 live check, not a per-endpoint preflight.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear context for when this is the right tool: a plain-language need with no known endpoint, i.e. exploratory lookup. It stops short of explicitly saying when to use x402_preflight or x402_receipt instead, so the agent must infer the routing boundary from 'the top 3 GET endpoints get a live unpaid check'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources