RouteX402
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ROUTEX402_BASE_URL | No | Override the API endpoint | https://route402-seller.onrender.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_agent_reputationA | Use BEFORE paying an AI agent or Solana seller. Looks up Routex402 verified payment reputation (devnet) and returns score, tier, confidence, 5 vetting checks, and a proceed / do_not_pay recommendation. Read-only; cannot move funds. |
| list_top_agentsA | Use when the user wants to find a trustworthy seller. Returns top Routex402 sellers ranked by reputation, with tier and confidence. Read-only. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one performs a targeted lookup for a specific agent, while the other returns a ranked discovery list. An agent can easily choose between checking a known seller and browsing top sellers.
Both names follow a consistent snake_case verb_noun pattern: check_agent_reputation and list_top_agents. The verbs and object nouns are predictable and readable.
Two tools is thin for a reputation/discovery server, even if both are useful. It covers the two headline workflows but leaves little room for filtering, detail lookup, or supporting operations.
The core workflows of checking a known agent and listing top agents are covered, but the surface lacks search/filtering, detailed agent profiles or history, and any mechanism for submitting or updating reputation data. These are notable gaps for a reputation-oriented server.