A-Pay Protocol
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APAY_NETWORK | No | The Base network to use for settlement (e.g., base-mainnet or base-sepolia testnet). | base-mainnet |
| APAY_CURRENCY | No | The settlement currency. Supports dual-currency settlement in USDC or the $APAY token (DUAL). | DUAL |
| APAY_DAILY_BUDGET | No | Maximum USDC amount the agent may spend per day (daily spending guardrail). | 2.00 |
| APAY_MAX_PER_CALL | No | Maximum USDC amount allowed per single API call (per-call spending cap). | 0.05 |
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 |
|---|---|
| apay_requestB | Make an HTTP request (GET, POST, etc.) to any API or website. If the endpoint returns an HTTP 402 Payment Required challenge, A-Pay automatically signs the cryptographic payment authorization within your budget limits and unlocks the data in <25ms. |
| apay_get_wallet_statusA | Inspect the agent's active non-custodial wallet address, current spending guardrails, and total spent in USDC and $APAY. |
| apay_set_budgetC | Configure agent safety invariants and spending guardrails. Prevents runaway loops or overcharging. |
| apay_inspect_endpointA | Inspect an endpoint to check if it requires an A-Pay micropayment, inspect the exact price quote, currency, and payout receiver without spending any funds. |
| apay_get_balanceA | Inspect the agent's live on-chain balances on Base Layer 2, including native ETH (for gas), USDC, and $APAY tokens. |
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 targets a distinct action: inspecting an endpoint, checking balances, making a paid request, viewing wallet status/guardrails, and setting budget. The dry-run inspect tool is clearly separated from the actual payment request tool, and balance vs wallet status are differentiated by their descriptions.
All tools use a consistent apay_ prefix and mostly follow a verb_noun pattern (inspect_endpoint, get_balance, get_wallet_status, set_budget). apay_request is the lone verb-only name, a minor deviation but still readable and predictable.
Five tools are well-scoped for a micropayment protocol agent surface: inspect, request, balance, status, and budget. Each tool earns its place with no obvious redundancy or missing core operation.
The toolset covers the essential lifecycle: checking payment requirements, executing paid requests, viewing balances, inspecting wallet state, and configuring spending limits. Minor gaps exist around transaction history or explicit wallet funding/withdrawal, but agents can work around these.