Skip to main content
Glama
camerxnduff

x402 Router

by camerxnduff
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to x402 Router

No user-submitted related servers found.

    Related Servers

    • x402-discovery

      rplryan
      A
      license
      Not graded
      quality
      D
      maintenance
      Discovers and queries x402-payable APIs at runtime — enables autonomous agents to find, evaluate, and pay for services via USDC micropayments on Base without API keys or subscriptions.
      MIT

    • Base Intel Search

      jakemaxsigal-creator
      A
      license
      Not graded
      quality
      D
      maintenance
      Pay-per-call web search for AI agents, settled in USDC on Base via the x402 protocol. No API key or subscription required; users fund a wallet and get a web_search tool.
      8 npm
      1
      MIT

    • SiteCheck

      bck-stack
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to call pay-per-request AI and web tools—including web-to-Markdown reading, PDF extraction, translation, compliance lookups, domain/email/Solana data, and prediction-market intelligence—without accounts or API keys, settling each call in USDC via x402 on Base, Solana, or Arc.
      MIT
    Deploy Server
    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

    TDQS

    A3.9/5.0

    Scored across 4 tools

    Disambiguation4/5

    search vs route is clearly differentiated (list vs best single match), and stats is distinct. get_paid_route_requirements overlaps somewhat with the routing tools since it examines the paid route without invoking it, but the description adequately clarifies it.

    Naming Consistency5/5

    All four tools use a consistent snake_case verb_noun pattern (search_, route_, get_, get_). The convention is uniform and predictable.

    Tool Count5/5

    Four tools is well-scoped for a small router/registry service; each tool (search, route, stats, payment requirements) covers a distinct facet with no filler.

    Completeness3/5

    Discovery and routing are covered, but there is no tool to actually invoke or pay for an endpoint—route_x402_request explicitly does not pay or call the target, and get_paid_route_requirements only returns requirements. The paid flow has a dead end within the surface.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources