PayQL
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PAYQL_NETWORK | No | Network: base or base-sepolia | base |
| PAYQL_RPC_URL | No | Advanced override: RPC URL | |
| PAYQL_PRIVATE_KEY | No | Base wallet private key (for wallet mode) | |
| PAYQL_GATEWAY_BASE | No | Advanced override: gateway base URL | |
| PAYQL_PAYMENT_MODE | No | Payment mode: wallet, harness, or managed (default: wallet if key set, else harness) | |
| PAYQL_REGISTRY_URL | No | Optional free GraphQL endpoint for discovery | |
| PAYQL_USDC_ADDRESS | No | Advanced override: USDC contract address | |
| PAYQL_WALLET_PROVIDER | No | Set to 'ampersend' with managed payment mode | |
| PAYQL_MAX_USD_PER_QUERY | No | Max USD per query | 0.01 |
| PAYQL_NETWORK_SUBGRAPH_ID | No | Advanced override: network subgraph ID | |
| PAYQL_AMPERSEND_SESSION_KEY | No | Ampersend session key (required for managed mode) | |
| PAYQL_AMPERSEND_SMART_ACCOUNT | No | Ampersend smart-account address (required for managed mode) |
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_subgraphsA | Find live subgraphs on The Graph by keyword/protocol, ranked by on-chain curation signal (a popularity proxy). Use this to pick a subgraph_id before querying. By default this runs a tiny PAID x402 query against The Graph network subgraph; set PAYQL_REGISTRY_URL to use a free discovery source. |
| get_payment_infoA | Preflight a subgraph: return the USDC price, asset, payTo and network from the x402 402 challenge WITHOUT paying. Use to estimate cost or to drive a harness-side payment. |
| query_subgraphA | Run a GraphQL query against a subgraph on The Graph, paying per query in USDC over x402 — gasless and keyless. Returns the data plus a payment receipt (tx hash + amount). Respects the per-query spend cap and returns a fund-wallet message if balance is insufficient. |
| get_subgraph_schemaA | List a subgraph's root queryable entities via GraphQL introspection (a paid x402 query). Use to learn what's queryable before composing a real query. |
| wallet_statusA | Report the payment mode, wallet address, USDC/ETH balance on Base, the per-query spend cap and funding instructions. Never reveals the private key. |
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 5 tools
Each tool has a distinct purpose: preflight cost estimation, schema introspection, actual query execution, subgraph search, and wallet status. No overlap or ambiguity.
Most tools follow a clear verb_noun pattern (get_payment_info, get_subgraph_schema, query_subgraph, search_subgraphs). wallet_status deviates slightly but remains clear and consistent in style.
Five tools cover the essential operations for a payment-based subgraph query service: preflight, schema, query, search, and wallet management. The count is well-scoped without unnecessary tools.
The tool set covers the core workflow: discovery, schema exploration, cost estimation, querying, and wallet status. A minor gap is the lack of a direct funding tool, but the query tool handles insufficient balance by returning funding instructions.