aqb-agent
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AQB_KEY | Yes | Private key used by the AQB MCP server (e.g. "0x…") to sign agent operations such as paying, funding, redeeming, and registering. |
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 |
|---|---|
| aqb_discoverC | Fetch AQB discovery doc from an agent host |
| aqb_balanceC | Get AQB and USDC balances for an address (read-only) |
| aqb_is_agentC | Check whether an address is a registered agent |
| aqb_quoteC | Quote 1 AQB in USDC from the vault (1.0) and the Uniswap V2 pool |
| aqb_registerC | Register a PQSmartAccount as an agent (caller must be the account) |
| aqb_update_cardC | Publish a new agent card hash from a PQSmartAccount |
| aqb_fundB | Mint AQB against USDC, 1:1 (usd in human units, e.g. 10.5) |
| aqb_payC | Pay AQB to another agent (amount in human units, e.g. 1.5) |
| aqb_redeemC | Redeem AQB for USDC, 1:1 (amount in human units) |
| aqb_cash_outD | Alias for aqb_redeem |
| aqb_announce_stealthC | Publish a stealth address for a payer from a PQSmartAccount |
| aqb_wellknownC | Generate your own /.well-known/agent-coin.json |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
TDQS
Scored across 12 tools
Most tools target a clearly distinct action or resource: quote, register, fund, pay, redeem, balance, discover, and well-known generation are separable. The main ambiguity is aqb_cash_out, which is explicitly an alias for aqb_redeem and therefore redundant rather than functionally distinct.
All names consistently use the aqb_ prefix and snake_case, giving a predictable surface. Most are verb_noun, though a few such as aqb_balance, aqb_is_agent, and aqb_wellknown are less verb-like while still readable.
Twelve tools is well within the appropriate range for a payment/agent-identity server. Each tool broadly corresponds to a useful operation, with only the redeem/cash_out alias being unnecessary duplication.
The surface covers the core lifecycle: registration, card updates, funding, paying, redeeming, quoting, balances, discovery, and well-known generation. Minor gaps remain, such as deregistration/revocation, on-chain card retrieval, or stealth-address consumption beyond announcement.