bullpen hyperliquid agent revoke¶
Last updated: July 13, 2026
Revoke an agent wallet by name, or by address after resolving the name from Hyperliquid
Usage¶
Live Help¶
Revoke an agent wallet by name, or by address after resolving the name from Hyperliquid
Usage: bullpen hyperliquid agent revoke [OPTIONS] <TARGET>
Arguments:
<TARGET>
Agent name, or an existing agent wallet address to resolve and revoke
Options:
--name <NAME>
Expected agent name when revoking by address. The CLI fails closed if it does not match Hyperliquid
--no-multi-wallet-warning
Suppress the table-mode warning shown when multiple EVM wallet accounts exist
--output <OUTPUT>
Output format for command results
[possible values: table, json]
--env <ENV>
Target environment to connect to (overrides config.toml)
[env: BULLPEN_ENV=]
[possible values: staging, production]
-y, --yes
Required confirmation flag for live Hyperliquid agent revoke
--config <CONFIG>
Path to a custom config.toml file (overrides $BULLPEN_CONFIG and the default location).
Explicit --config and BULLPEN_CONFIG paths fail closed: if the file is missing, the CLI exits validation instead of silently loading defaults. Credentials still resolve via BULLPEN_HOME, so set BULLPEN_HOME too when isolating a session.
--preview
Show the planned revoke without signing or submitting
--read-only
Enable read-only mode: blocks all mutating commands
--non-interactive
Suppress interactive prompts; does NOT imply --yes for money-moving commands
[env: BULLPEN_NON_INTERACTIVE=]
-h, --help
Print help (see a summary with '-h')
EXAMPLES:
# Preview revoking an agent wallet by name
bullpen hyperliquid agent revoke bot1 --preview
# Export the agent revoke preview as JSON
bullpen hyperliquid agent revoke bot1 --preview --output json
AGENT WALLET BOUNDARY:
This is delegated-agent management. Normal Hyperliquid trades do not create,
approve, or consume Hyperliquid API/agent wallet slots; use revoke only when
intentionally removing delegated trading authority.
BACKEND REGISTRY NOTE:
This command manages Hyperliquid extraAgents directly. It is not the
Bullpen-managed agent-wallet revoke flow; run `bullpen hl agent list --output
json` before and after live use to compare exchange state with the Bullpen
backend registry.
Example Commands¶
bullpen hyperliquid agent revoke bot1 --preview
bullpen hyperliquid agent revoke bot1 --preview --output json
JSON Output¶
Contract: JSON Output Contract.
Preview (--preview --output json)¶
Preview output is a single JSON document emitted only when --preview --output json is passed. It includes explicit no-submit safety fields; live submit output uses the corresponding Hyperliquid mutation-report schema.
Schema version: 1 when a command emits schema_version; otherwise treat the current command shape as contract version 1.
Top-level Keys¶
| key | type | nullable | notes |
|---|---|---|---|
schema_version |
integer | yes | Mutation preview/report schema version when emitted |
kind |
string | yes | hyperliquid_mutation_preview for preview JSON |
action |
string | no | Always agent-revoke |
account |
string | no | Active Hyperliquid master account |
scope |
string | yes | Human-readable account context |
would_submit |
boolean | yes | False in preview output |
signature_requested |
boolean | yes | False in preview output |
exchange_request_submitted |
boolean | yes | False in preview output |
intent.agent_address |
string | yes | Agent wallet address that would be revoked |
intent.agent_name |
string | yes | Agent name resolved or supplied for the revoke |
Example¶
{
"schema_version": 1,
"kind": "hyperliquid_mutation_preview",
"action": "agent-revoke",
"account": "0x1111111111111111111111111111111111111111",
"scope": "primary 0x1111111111111111111111111111111111111111",
"coin": null,
"would_submit": false,
"signature_requested": false,
"exchange_request_submitted": false,
"summary": "Preview only - no signature requested and no Hyperliquid exchange request submitted. Planned revoke of agent bot1.",
"intent": {
"action": "agent-revoke",
"account": "0x1111111111111111111111111111111111111111",
"agent_name": "bot1",
"agent_address": "0x2222222222222222222222222222222222222222",
"reduce_only": false,
"builder_fee_bps": 0.0
}
}
Stability¶
Patch releases may add nullable or optional fields. Minor releases may add required fields or increment schema_version. Major releases may remove or rename fields.