get_v1_wallets
Returns the caller org's wallets, newest first, optionally NARROWED within the org by project, agent or account.
Returns the caller org's wallets, newest first, optionally NARROWED within the org by project, agent or account. The org is always the bound isolation boundary — the filters only ever narrow inside it, so a caller can never widen past its own org.
| Tool | get_v1_wallets |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 3 |
| Operation | GET /v1/wallets |
| Product | wallets |
Arguments
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
account | string | — | — | Account narrows to wallets under one account id. Must be a url-safe segment. |
agent | string | — | — | Agent narrows to wallets scoped to one agent. Must be a url-safe segment. |
project | string | — | — | Project narrows to wallets scoped to one project. Must be a url-safe segment. |
This tool's schema does not declare which fields are required, nor any default, nor any enumerated value set. The columns above are empty because the door publishes nothing there, not because the answer is "none" — where a field is constrained, the constraint is stated in that field's own description.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Every declared argument is shown, because the door marks none of them required.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "get_v1_wallets",
"arguments": {
"account": "<account>",
"agent": "<agent>",
"project": "<project>"
}
}
}'Values are placeholders derived from each field's declared type. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →
The operation behind it
| Operation | Route | Product | Summary |
|---|---|---|---|
cloud_get_v1_wallets | GET /v1/wallets | wallets | Returns the caller org's wallets, newest first, optionally NARROWED within the org by proj |
The same capability over plain HTTP is in the wallets API reference, on https://api.hanzo.ai.
All 834 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 834 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).
How is this guide?