Skip to main content
Glama

AI Product Index

Find a paid API you can call with x402

search_x402_endpoints

Search 33,461 x402-payable HTTP endpoints — the machine-payable web, normalized from the Coinbase CDP Bazaar. Use this to find an API an agent can pay for per call (USDC on Base and other chains) and to see what it costs before calling it. Filter by chain, HTTP method, host or maximum price; results are ranked by relevance then cheapest first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_x402_endpoints"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNoRestrict to endpoints on a hostname (substring match).
chainNoRestrict to one chain, e.g. base, solana, polygon.
limitNo
queryNoWhat the endpoint should do, e.g. "weather forecast" or "token price".
methodNoRestrict to an HTTP method, e.g. GET or POST.
max_priceNoMaximum price per call in USD. Endpoints priced in an unrecognised asset are excluded when this is set, because their price is unknown rather than zero.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful behavior: result-set size, upstream source, and the ranking rule ('relevance then cheapest first'). It omits what a result record actually contains and any pagination/truncation behavior beyond the limit cap, leaving some operational gaps.

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

Conciseness5/5

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

Three sentences, front-loaded with what it is, then when to use it, then how filtering and ordering work. No filler; the precise endpoint count and the Bazaar provenance each earn their place.

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?

For a six-parameter, filter-only search tool with no annotations and no output schema, the description covers purpose, filters, and ranking well. The main gap is the absence of any indication of what a returned endpoint record contains, which matters since there is no output schema to fall back on.

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 coverage is 83%, so the schema already documents nearly every parameter including the subtle max_price exclusion rule. The description only restates the filter set (chain, HTTP method, host, max price) and adds the ordering behavior, which does not meaningfully deepen parameter meaning beyond the schema.

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 and resource — 'Search 33,461 x402-payable HTTP endpoints' — plus provenance (normalized from the Coinbase CDP Bazaar) and the unit of payment (USDC per call). This is unmistakably distinct from siblings like search_mcp_servers and search_products; an agent can select it without opening the schema.

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 a clear use case: find an API an agent can pay for per call and check its cost before invoking it. It does not name an alternative tool or state when NOT to use this one, so it stops short of full routing guidance.

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