Skip to main content
Glama

AI x402 API recommender: ranked, preflighted picks

x402_recommend
Read-only

AI recommendation of the best paid x402 API for a task in plain words. Ultravioleta Bazaar and 402 Index listings are deduped and keyword-scored; Anthropic Claude reranks up to 30 for fit. The first 3 GET picks get a live unpaid preflight: valid 402, live USDC price, networks, risk flags, OFAC payTo screen, domain age. Each result: URL, description, price, networks, usage evidence, preflight, AI-written reason, verbatim-checked listing quote. Kit Rx routes are labelled. Price: $0.005 per successful call, paid in USDC with x402 v2; failed calls and calls that match nothing are not charged. AI-generated answer; a call with no arguments returns the stored example answer without a model call.

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": {
      "task": "<task>"
    },
    "name": "x402_recommend"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesWhat the agent needs done, in plain words, 3-300 characters (e.g. get a 7-day weather forecast for a US city, check if a token contract is a honeypot).
limitNoNumber of recommendations, 1-5 (default 3). The first 3 checkable ones get a live preflight.
networkNoOnly endpoints that accept canonical USDC on this network.
max_price_usdNoHighest acceptable price per call in USD as a decimal, e.g. 0.01. Listings without a USDC price are left out when set; a higher live price fails the preflight.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior5/5

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

With only readOnlyHint and openWorldHint declared, the description adds substantial behavior: $0.005 per successful call in USDC via x402 v2, no charge on failed or zero-match calls, preflight scope limited to the first 3 GET picks, the specific checks performed (valid 402, live USDC price, OFAC payTo screen, domain age), and the stored-example fallback. None of this is in the annotations or 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?

Dense and front-loaded, leading with what the tool does and following with pipeline, result shape, and pricing. It is a long single paragraph, but nearly every clause carries operational information; only minor tightening is possible.

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?

No output schema exists, yet the description enumerates the returned fields (URL, description, price, networks, usage evidence, preflight, AI reason, verbatim-checked quote) and covers cost, charging rules, and fallback behavior. An agent has enough to decide and call 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 coverage is 100% and every parameter is documented, so baseline 3 applies. The description adds marginal meaning by explaining that only the first 3 checkable picks are preflighted and that price filtering interacts with preflight failure, but it does not elaborate on task phrasing guidance beyond the schema example.

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

Purpose4/5

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

Specific verb+resource: 'AI recommendation of the best paid x402 API for a task in plain words', with the pipeline (dedupe, keyword-scoring, Claude rerank) spelled out. It does not explicitly differentiate itself from siblings like x402_find or x402_preflight, leaving the agent to infer the boundary.

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

Usage Guidelines3/5

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

Usage is implied by 'for a task in plain words' and the note that a no-argument call returns a stored example without a model call. However, there is no explicit when-to-use-this-vs-alternative statement, and the relationship to x402_preflight (which the description mentions as a stage rather than a sibling) is not clarified.

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