aeron-wallet
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RPC_URL | No | The RPC endpoint for the Robinhood Chain. | https://rpc.mainnet.chain.robinhood.com |
| CHAIN_ID | No | The chain ID. | 4663 |
| USDG_ADDRESS | No | The USDG token contract address. | 0x5fc5360d0400a0fd4f2af552add042d716f1d168 |
| DAILY_CAP_USD | No | Maximum total payments per UTC day in USD. | 1 |
| AERON_WALLET_DIR | No | Directory where the wallet key is stored. | ~/.aeron/wallet |
| AERON_WALLET_KEY | No | Private key override; if set, used instead of the stored key. | |
| MAX_PER_CALL_USD | No | Maximum payment allowed per single call in USD. | 0.05 |
| AERON_WALLET_SESSION | No | Session token that binds the server to a specific session scope. |
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 |
|---|---|
| get_addressB | The wallet address on Robinhood Chain. Fund it with USDG to pay for services. |
| get_balanceA | ETH and USDG balances of this wallet. |
| payB | Call a machine-payable (x402) endpoint and pay in USDG if it answers 402. Budget caps apply. |
| historyC | Recent payments made by this wallet. |
| create_sessionA | Create a scoped session: allowed hosts, a total budget, a per-call cap, and an expiry. Returns a token that binds an agent to that scope. |
| list_sessionsA | Every session, with what it has spent and whether it is still live. |
| revoke_sessionB | Revoke a session by id. It stops paying on its next call. |
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 7 tools
Each tool targets a distinct concern: wallet address, balances, payment execution, payment history, and session lifecycle. There is no meaningful overlap between payment history and session listing because one is about transactions and the other about scoped spending sessions.
Most tools follow a clear verb_noun pattern: get_address, get_balance, create_session, list_sessions, revoke_session. The single exception is 'history', which is a noun rather than a verb-led name like 'get_history' or 'list_payments'.
Seven tools is well-scoped for a wallet and session-management server. Each tool earns its place and the size is neither bloated nor overly thin.
The core wallet capabilities and session lifecycle are covered: address, balance, payment, history, create, list, and revoke. Minor gaps remain, such as no way to retrieve full session configuration details or individual payment records, but agents can work around this with the current surface.