Skip to main content
Glama

aicomglobal

by io.github.moonspacenow-tech
OverviewDiscussionsAdmin

x402 router — the best service for your need (sub-cent, paid)

aicom_x402_route

The sub-cent ($0.002 x402) ROUTER: tell it a NEED in free text (e.g. 'ENS resolution', 'BTC spot price', 'web search') and get the best live x402 service(s) to actually CALL — ranked by relevance × aicomglobal's measured reliability × Coinbase 30-day demand, cheaper preferred, each with a verify-before-you-pay pointer. The decision over the 20,000+ live Bazaar services computed for you, so you never call a dead or overpriced endpoint. Browsing the full Index is FREE (aicom_x402_index); you pay only for the targeted need→best-service answer. Returns the QUOTE only; to get the answer, GET /route for a single-use nonce then POST /route {nonce, need}. LIVE right now: of 7 x402 services aicomglobal is currently observing, 4 are failing or drifting — a dead endpoint eats your call fee and your task, so verify before you send one your money (recompute free at /api/x402).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
needNoThe capability you need in free text, e.g. 'ENS resolution' (required when pay_with:'credits')
limitNoMax results (default 3)
pay_withNoSet to 'credits' to SETTLE now from your prepaid balance (no wallet) and get the ranked answer in THIS call; omit to get the quote.
idempotency_keyNoOptional retry-safety key: the same key on a retry returns the SAME answer, never a second debit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / idempotency_key
      Added value: +{
+  "description": "Optional retry-safety key: the same key on a retry returns the SAME answer, never a second debit.",
+  "type": "string"
+}
  2. Changed4 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / limit
      Added value: +{
+  "description": "Max results (default 3)",
+  "maximum": 10,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / need
      Added value: +{
+  "description": "The capability you need in free text, e.g. 'ENS resolution' (required when pay_with:'credits')",
+  "type": "string"
+}
    • addedInput schema / properties / pay_with
      Added value: +{
+  "description": "Set to 'credits' to SETTLE now from your prepaid balance (no wallet) and get the ranked answer in THIS call; omit to get the quote.",
+  "type": "string"
+}
  3. Added

TDQS

A4/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 discloses a lot: price ($0.002), that free-text NEED is only charged for the targeted answer, the QUOTE-vs-answer split, the single-use nonce requirement, idempotency safety, and the verify-before-you-pay pointer plus reliability caveat. It stops short of stating error/auth behavior or what the quote payload contains, so not a 5.

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

Conciseness3/5

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

Front-loaded with the core need→service function, but the marketing framing ('the best service for your need') and the mid-sentence 'LIVE right now: of 7 x402 services... 4 are failing' sales pitch add bulk that dilutes the actionable facts. The essential mechanics are buried among promotional claims.

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 paid, two-step router with no output schema, the description explains what is returned (quote vs answer) and how to obtain the answer, which is the critical missing piece. Remaining gaps (quote format, failure modes) are minor given the schema covers all four parameters fully.

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%, so the baseline is 3. The description reinforces the meaning of need (free text, examples given) and pay_with ('credits' settles now and returns the answer in this call), but largely restates what the schema's own parameter descriptions already say.

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: it takes a free-text NEED and returns ranked x402 services to call. It explicitly distinguishes itself from the sibling aicom_x402_index ('Browsing the full Index is FREE... you pay only for the targeted need→best-service answer'), so an agent can tell the two apart without opening either 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?

Clear when to use it (a targeted need→best-service decision over 20,000+ Bazaar services) versus the free aicom_x402_index for browsing. It also describes the two-step path to the actual answer (GET /route for a nonce, then POST). No explicit when-not-to-use or cost-comparison to other paid siblings, so not a 5.

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

All aicomglobal toolsInspect
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