P0 Agent Economy Index

by dev.workers.x402-bazaar-rank-worker.x402-bazaar-rank

Search x402 services

search_x402_services

Read-onlyIdempotent

Search verified x402 sellers by capability (a set compiled from Agenstry, Open 402, pay.sh, the Official MCP Registry and apis.io listings, with price, networks and evidence of a live 402 challenge or manifest). Free tier returns the top 5; full results are available as the paid /search endpoint (x402 or MPP) on the same host. Calls and paying wallets, where shown, are P0's own on-chain counts of transfers to each seller's wallet (null where not measured). Not for picking one service for a concrete task (use best_service_for_task), for market-wide totals (use x402_market_stats) or for this host's own products (use list_paid_data_products).

Input Schema

Name	Required	Description
`query`	Yes	capability to look for, e.g. 'web search', 'llm inference'
`network`	No	optional CAIP-2 filter, e.g. eip155:8453
`include_testnets`	No	also list services that exist only on test networks (default false)

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 20, 2026

addedInput schema / properties / include_testnets

Added value: +{
+  "description": "also list services that exist only on test networks (default false)",
+  "type": "boolean"
+}

First observedOct 13, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the readOnly/openWorld/idempotent annotations by disclosing the free-tier truncation to 5 results and the paid /search endpoint (x402 or MPP) on the same host for full results — a behavioral constraint the agent must know to interpret a short list. It also explains that call and paying-wallet figures are P0's own on-chain transfer counts and are null when unmeasured, preventing misreading of empty fields.

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-loads the action and corpus, then the free/paid caveat, then the exclusions — a sensible ordering with no filler sentences. The provenance parenthetical and the repeated caveats make it denser than strictly necessary, but every clause carries usable information.

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

Completeness5/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 compensates by naming the fields returned (price, networks, 402 evidence, calls, paying wallets) and the result-count limit. Combined with the sibling routing, an agent has everything needed to decide to call it and interpret the response.

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 query, network (CAIP-2) and include_testnets are already documented, establishing a baseline of 3. The description adds only loose context — 'by capability' and 'networks' — without new syntax, defaults or filtering semantics 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 and resource ('Search verified x402 sellers by capability') and immediately qualifies the corpus it searches (Agenstry, Open 402, pay.sh, MCP Registry, apis.io) plus what each record carries (price, networks, 402 evidence). An agent can distinguish this from best_service_for_task or x402_market_stats without opening any schema.

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

Usage Guidelines5/5

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

Gives explicit negative routing with the exact sibling to use instead for three distinct cases: picking one service (best_service_for_task), market totals (x402_market_stats), and this host's own products (list_paid_data_products). That is when-not-to-use plus named alternatives, which is the top of the scale.

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

All P0 Agent Economy Index 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.

Resources

Need Help?