GadgetHumans API Hub

x402_search

Free. Search every live x402 bazaar - PayAI (14,841 listings) and Coinbase CDP (73,178) plus this catalogue - in one call, ranked by measured 30-day call volume. Compare providers and prices before paying any endpoint.

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_search"
  }
}

Input Schema

Name	Required	Description
`q`	Yes	Search term, e.g. whois or token price
`sort`	No	calls (default, measured 30-day volume) or price (cheapest first)
`limit`	No	Max results (1-25)
`source`	No	Only listings from this bazaar
`network`	No	Only listings settling on this network, e.g. 8453 (Base) or an eip155 id
`max_price`	No	Only listings at or below this price in USD, e.g. 0.002

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedNov 2, 2026

addedInput schema / properties / max_price

Added value: +{
+  "description": "Only listings at or below this price in USD, e.g. 0.002",
+  "type": "number"
+}

addedInput schema / properties / network

Added value: +{
+  "description": "Only listings settling on this network, e.g. 8453 (Base) or an eip155 id",
+  "type": "string"
+}

addedInput schema / properties / sort

Added value: +{
+  "description": "calls (default, measured 30-day volume) or price (cheapest first)",
+  "enum": [
+    "calls",
+    "price"
+  ],
+  "type": "string"
+}

addedInput schema / properties / source

Added value: +{
+  "description": "Only listings from this bazaar",
+  "enum": [
+    "payai",
+    "cdp",
+    "ours"
+  ],
+  "type": "string"
+}

AddedNov 2, 2026

TDQS

A4/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It usefully discloses that the tool is free, covers PayAI/CDP/this catalogue, and ranks by measured 30-day call volume, but it does not describe auth requirements, rate limits, result contents, or pagination behavior.

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?

The description is compact and front-loaded: 'Free' and the core search action appear immediately. Every sentence contributes either scope, ranking behavior, or the pre-payment use case.

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 search tool with a fully described 6-parameter schema and no output schema, the description covers the domain, sources, ranking logic, and intended use. It could say more about result shape or limits, but an agent has enough context to invoke it correctly.

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 the schema already explains q, sort, limit, source, network, and max_price. The description supports the ranking and price-comparison intent but does not add syntax or semantics 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?

The description uses a specific verb and resource: 'Search every live x402 bazaar ... in one call.' It names the included bazaars and the ranked-by-volume behavior, which clearly distinguishes this from generic web/search tools in the sibling list.

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?

It gives a clear use case: compare providers and prices before paying any endpoint. It does not explicitly name alternatives or when-not-to-use, but the x402-specific context is strong enough for an agent to choose it over generic search tools.

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

All GadgetHumans API Hub tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.