x402search
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| EVM_PRIVATE_KEY | Yes | A wallet private key (EVM) used to pay for searches on the Base mainnet. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_x402_apisA | Search 13,000+ x402-enabled HTTP APIs by capability, category, network, or keyword. Returns ranked results with endpoint URLs, pricing, and payment metadata. Use this to discover paid APIs for any capability your agent needs. Costs $0.01 USDC per search on Base mainnet. |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap with other tools. The tool has a single, clearly defined purpose: searching x402-enabled APIs. Agents cannot misselect between tools as there is only one option.
A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The tool name 'search_x402_apis' follows a clear verb_noun pattern, which would be consistent if more tools were added.
One tool is too few for a server focused on API discovery, as it severely limits functionality. While the tool covers search, there are obvious gaps like filtering, sorting, or accessing detailed API information, making the server feel thin and incomplete for its domain.
The server is severely incomplete for API discovery. It only provides search functionality, missing essential operations such as retrieving detailed API metadata, filtering results, or managing saved searches. This will cause agent failures when trying to perform comprehensive API exploration tasks.