Hedwig
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NETWORK | No | `hedera-testnet` or `hedera-mainnet` | hedera-testnet |
| MAX_PER_DAY | No | Highest USDC amount the wallet will spend per UTC day | 20.00 |
| MAX_PER_CALL | No | Highest USDC amount the wallet will spend at a time | 0.10 |
| HEDERA_ACCOUNT_ID | Yes | Your Hedera account ID, e.g. `0.0.12345` | |
| HEDERA_PRIVATE_KEY | Yes | ECDSA or ED25519 private key (hex or DER) |
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 |
|---|---|
| check_balanceA | Return HBAR and USDC balances for the configured Hedera account, plus a HashScan link. Reads from the Hedera Mirror Node REST API for reliability. |
| transfer_hbarA | Send HBAR from the configured account to another Hedera account. Amount is in HBAR (e.g. "0.5"), not tinybars. |
| transfer_usdcA | Send USDC (HTS token) from the configured account to another Hedera account. Both accounts must be associated with the USDC token. |
| payA | Sign an x402 payment authorization for a USDC transfer on Hedera. Returns the header value your HTTP client should attach when retrying the paid request. |
| x402_fetchA | Fetch a URL that may be x402-gated. If the server returns 402, sign a Hedera USDC payment, retry with the payment header, and return the final response body. Includes diagnostic info in the response for debugging. |
| spending_reportA | Return the current session's USDC spending summary, budget caps, and full history of x402 payments and transfers. |
| request_fundingA | Return a fundable receiving address for the configured Hedera account, plus a testnet faucet link (testnet 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 7 tools
Each tool targets a distinct operation: balance checking, two asset transfers, payment signing, spending analysis, gated fetch, and funding request. No two tools have overlapping purposes; x402_fetch uses pay internally but is clearly for HTTP retrieval.
Mostly verb_noun (check_balance, transfer_hbar, transfer_usdc, request_funding), but 'pay' is a bare verb, 'spending_report' is a noun phrase, and 'x402_fetch' puts the object first. This mixed style reduces predictability.
Seven tools is well-scoped for a payment and x402 server—enough to cover core operations without bloat.
Covers balances, transfers for both HBAR and USDC, x402 payment authorization and retrieval, spending reports, and funding. Missing a budget management tool (only reports caps, doesn't set them) but core workflows are complete.