This reference covers the akt command groups and the most common Akash and Cosmos SDK operations.
The chain SDK contributes many additional query and transaction leaves. Run akt <command> --help for the exact command tree and flags in your installed release.
Command Structure
akt <command> <subcommand> [arguments] [flags]Global Flags:
--home- Home directory for config, contexts, and keyrings (default:$AKT_HOMEor~/.config/akt)--context- Active context name (overridescurrent-contextin config)--keyring-backend- Keyring backend for this invocation--keyring-dir- Keyring directory for this invocation-o, --output- Output format:pretty(default),json,yaml-v, --verbose- Increase output verbosity (-vverbose,-vvdebug)-q, --quiet- Suppress informational output while keeping results and errors
Commands take their primary values positionally, following the Akash resource hierarchy (owner/dseq/gseq/oseq/provider). Defaults for the node, chain ID, gas settings, and signing account come from the active context.
Context Commands
Create Context
Create a new context. A network is required for keyring contexts and optional for a Console-only context.
akt context create <name> --network <network>Flags:
--network- Network definition to use--auth-method-keyring(default) orconsole-api--default-account- Default signing account--set-current- Make this the active context
Example:
akt context create prod --network mainnet --default-account alice --set-currentconsole-api contexts do not require a keyring or default account. Their API key identifies the Console account and managed wallet. Owner-scoped chain queries still require an explicit owner when no default account is set.
Keyring definitions
Create and manage the named key stores that contexts reference.
# List keyringsakt context keyring list
# Create a file-backed keyring for a headless hostakt context keyring create headless file
# Change an existing backendakt context keyring set headless osThe os backend uses the platform credential store. Other supported backends are file, test, kwallet, pass, and memory.
Switch Context
Set the active context.
akt context use <name>Show Context
Show active context details: resolved network, keyring, store path, and capabilities.
akt context showEdit Context
Change a context’s settings.
akt context edit <name> [flags]Example:
akt context edit prod --default-account bobList, Rename, Delete
# List all contextsakt context list
# Rename a context (moves its stored credentials)akt context rename prod production
# Delete a contextakt context delete staging --yesAction Log
View the per-context log of mutating operations, newest first.
akt context logFlags:
--type- Filter by action type (e.g.,tx)--since- Duration (1h) or timestamp (2026-01-01)--limit- Maximum entries to show--workflow-id- Show every action for one workflow run
Network Commands
Create Network
Create a network definition from a built-in template or custom values.
akt context network create <name> [flags]Flags:
--template- Built-in template:mainnet,testnet,sandbox--chain-id- Custom chain ID--rpc- Custom RPC endpoint--gas-prices- Gas prices (e.g.,0.025uakt)
Example:
# From templateakt context network create mainnet --template mainnet
# Custom networkakt context network create local --chain-id localnet-1 --rpc http://localhost:26657List, show, edit, and delete networks
# List networks and which contexts use themakt context network list
# Show full network detailsakt context network show mainnet
# Edit a network (affects all contexts using it)akt context network edit mainnet --gas-prices 0.025uakt
# Delete an unused networkakt context network delete localThe selected network’s gas price is the minimum used for gas-price-derived fees. Lower flag and environment values are raised to the floor, higher values are preserved, and an explicit --fees value remains authoritative.
Key Commands
Add Key
Add a new key or recover an existing one.
akt context keys add <name>Flags:
--recover- Import from mnemonic--source- Read a mnemonic from a file--ledger- Add a Ledger key--multisig- Create a multisig from existing key names--no-backup- Do not print a generated mnemonic--yes,-y- Accepted for Cosmos CLI compatibility; never overwrites a key
Unless you use --no-backup or recover an existing key, save the mnemonic phrase printed after creation. It cannot be shown again.
Show Key
Display key details.
akt context keys show <name>Flags:
--address- Print only the bech32 address (useful for scripting)
List, Delete, Rename
# List keys in the current context's keyringakt context keys list
# Delete a keyakt context keys delete alice
# Rename a keyakt context keys rename alice alice-old
# Generate a BIP39 mnemonic without creating a keyakt context keys mnemonicExport / Import
# Export a keyakt context keys export alice > alice.key
# Import from an exported keyfileakt context keys import alice-backup alice.keyParse Address
Convert an address between hex and bech32 formats.
akt context keys parse akash1abc...SDL Commands
Every akt sdl subcommand runs entirely locally: no context, no key, no RPC endpoint.
List Scaffolds
List the built-in scaffolds (web, gpu, multi-service, ip-lease) and the flags each honors.
akt sdl scaffoldsGenerate an SDL
Print a deployable SDL to stdout, self-checked against the validator.
akt sdl init <scaffold> [flags]Flags:
--image- Container image (must carry an explicit tag or digest)--cpu,--memory- Compute resources--gpu-model- GPU model for thegpuscaffold--price- Pricing amount
Example:
akt sdl init web --image nginx:1.27 > deploy.yamlValidate an SDL
Validate offline; exit 0 when valid, 1 when not. Use - to read stdin.
akt sdl validate deploy.yamlWorkflow Commands
Workflow commands orchestrate the full deployment lifecycle, routing each step through the active context’s auth method (local signing for keyring, Console API for console-api).
Deploy
Create a deployment, wait for bids, select a provider, create the lease, and send the manifest.
akt deploy <sdl-file>Flags:
--deposit-autofor the live chain minimum, an explicit chain coin, or an explicit Console USD value such as5,5usd, or$5. Console contexts cannot use the defaultautovalue.--bid-timeout- Maximum time to wait for bids (default:5m)--bid-select-interactive(default),cheapest, orprovider=<addr>--ready-timeout- Maximum readiness wait after manifest submission (default:2m)--no-wait-active- Return immediately after manifest submission-y, --yes- Skip confirmation prompts--dry-run- Show the execution plan without broadcasting
Example:
# Automated deployment for CI/CD: one JSONL line per stepakt deploy deploy.yaml --bid-select cheapest --yes -o jsonlUpdate
Update a deployment from a modified SDL file.
akt update <sdl-file> [dseq]Example:
akt update deploy.yaml 12345Close
Close a deployment and return the remaining escrow balance.
akt close [dseq]Example:
akt close 12345Query Commands
Akash queries use a positional filter argument following the resource hierarchy, with smart type detection (a bech32 address is an owner, a number is a dseq). The q alias is equivalent to query.
Deployments
# List your deployments (owner defaults to context account)akt query deployment
# Filter positionally: state, dseq, owner, owner/dseqakt query deployment activeakt query deployment 12345akt query deployment akash1abc...akt query deployment akash1abc.../12345Owner-scoped lists refuse when neither the command nor the context supplies an owner. Paginated deployment queries support --limit, --offset, --page, --page-key, --reverse, and --count-total.
Market (Bids and Leases)
# List active leases (positional state keyword)akt query market lease active
# Leases for a specific deploymentakt query market lease 12345
# Specific lease (owner from context)akt query market lease 12345/1/1/akash1prov...
# Provider-perspective queryakt query market lease --by provider akash1prov...
# Bids for a deploymentakt query market bid 12345
# Orders for a deploymentakt query market order 12345Bank, Staking, Governance
# Check balancesakt query bank balances akash1abc...
# Validatorsakt query staking validators
# Governance proposalakt query gov proposal 42Providers and Certificates
# Query a providerakt query provider akash1prov...
# Certificates for an ownerakt query cert list akash1abc...WASM
# Query a contractakt query wasm contract-state smart akash1contract... '{"get_count":{}}'Transaction Commands
All transaction commands accept --from, --gas, --gas-prices, --fees, --broadcast-mode, --yes, --dry-run, and other standard flags. Defaults come from the active context. Gas-price-derived fees cannot fall below the selected network’s configured price; fixed --fees values bypass that calculation.
Deployments
# Create a deployment from an SDL fileakt tx deployment create deployment.yaml
# Update a deployment (positional sdl and dseq)akt tx deployment update deployment.yaml 12345
# Close a deployment (positional dseq)akt tx deployment close 12345Note: These direct chain transaction commands require a keyring signing account. For a managed wallet, use akt deploy, akt update, and akt close, or the matching akt console deployment command.
Deployment Groups
Modify a specific group within a deployment (positional dseq and gseq):
# Pause a deployment groupakt tx deployment group pause 12345 1
# Resume a paused groupakt tx deployment group start 12345 1
# Close a groupakt tx deployment group close 12345 1Market
# Create a lease (positional dseq and provider; gseq/oseq default to 1)akt tx market lease create 12345 akash1prov...Bank, Staking, Governance
# Send tokensakt tx bank send alice akash1dest... 1000000uakt
# Delegate to a validatorakt tx staking delegate akashvaloper1... 1000000uakt
# Vote on a governance proposalakt tx gov vote 42 yesCertificates
# Generate and publish a client certificateakt tx cert generate clientakt tx cert publish clientMint & Burn ACT (BME)
Convert between AKT and ACT through the Burn-Mint-Equilibrium module:
# Mint ACT by burning AKTakt tx bme mint-act 500000uakt
# Burn ACT to mint/remint AKTakt tx bme burn-act 500000uact
# Generic form: burn tokens to mint another denominationakt tx bme burn-mint 500000uakt uactSee Mint & Burn ACT for background on when and why to convert.
Console Commands
Commands for the Akash Console managed-wallet API. See Console Integration for setup and workflows.
Authentication
# Validate a Console API key and store it for the active contextakt console loginakt console login <key>
# Remove the stored credentialakt console logout
# Show the authenticated accountakt console whoamiDeployments
akt console deployment list [active|closed] --limit 20 --skip 0akt console deployment get <dseq>akt console deployment create <sdl-file> [deposit-usd]akt console deployment update <dseq> <sdl-file>akt console deployment deposit <dseq> [amount-usd]akt console deployment settings <dseq> [true|false]akt console deployment close <dseq>USD amounts must use plain decimal notation with no more than two fractional digits and must be at least $0.50. Deployment mutations validate the positive dseq and reject closed resources before sending a write request. A repeated close is an error.
Bids and Leases
# Inspect provider bidsakt console bid list <dseq>
# Accept a bid by creating a lease and sending the manifestakt console lease create <dseq> [provider]Wallet and Usage
akt console wallet listakt console wallet balanceakt console wallet settings [true|false]akt console wallet cost
# Historical spend and active-deployment counts (positional dates)akt console usage [from] [to]Live Lease Operations
# Stream container logs from the lease's providerakt console logs <dseq> [service] --follow
# Stream Kubernetes eventsakt console events <dseq> --follow
# Live lease status from the provider gatewayakt console status <dseq> --watch --interval 30s
# Open a shell or run a command in a lease containerakt console shell <dseq> <service>akt console shell <dseq> <service> -- ls -laExplicit commands launched from a terminal detach stdin by default. Piped input attaches automatically; use --stdin to force attachment. JSON and YAML output require an explicit command and return stdout and stderr fields.
Marketplace (No API Key Required)
# Provider catalogakt console provider listakt console provider get <provider>akt console provider regionsakt console provider auditors
# GPU availability and pricingakt console gpu
# Deployment templatesakt console template listakt console template get <id>akt console template sdl <id>
# List providers able to run an SDL (bid screening)akt console screen <sdl-file>
# Screen explicit resources, or override values read from an SDLakt console screen --cpu 2 --memory 4Gi --gpu 1 --gpu-model a100Credentials
# Manage Console API keys (the secret is shown ONCE)akt console apikey listakt console apikey create <name> [expires-at]akt console apikey delete <id>
# Mint a provider-scoped JWTakt console jwt createSuccessful Console leaf commands write a Next: hint to stderr. Structured stdout stays pipe-safe, and --quiet suppresses the hint.
Provider Commands
Direct provider gateway operations for keyring contexts. A provider address resolves its gateway URL from the provider’s on-chain record. --provider-url optionally overrides that gateway URL; it is not a chain RPC endpoint. Protected lease operations use jwt (default) or mtls authentication from the context.
Lease-scoped commands resolve the provider, gseq, and oseq from the deployment’s single active lease when possible. Pass --provider to choose when several active leases exist.
Provider Status
akt provider status [provider-addr] --timeout 30sProvider status is public and does not require a wallet or default account.
Lease Status
akt provider lease-status [dseq]Lease Logs
akt provider lease-logs [dseq]Flags:
-f, --follow- Follow log output--service- Filter logs by service name--tail- Number of lines to show from the end of the logs
--tail cannot be combined with --follow.
Lease Events
akt provider lease-events [dseq] --followLease Shell
Open an interactive shell session to a container in a lease. Positional arguments are the remote command, so --dseq and --service are flags here.
akt provider lease-shell --dseq <dseq> --service <service> -- /bin/shFlags:
--dseq- Deployment sequence number--service- Service name (required)--stdin- Force stdin attachment for an explicit terminal command-t, --tty- Allocate a TTY (default: true)
Explicit commands launched from a terminal detach stdin by default. Piped input attaches automatically. Structured output requires an explicit command and returns separate stdout and stderr fields.
Confidential-compute attestation
Request a fresh hardware quote from a confidential-compute lease:
akt provider lease-attestation [dseq]The command verifies the provider transport and nonce freshness. It does not yet validate the hardware evidence signature, endorsement chain, or measurement policy.
Manifests
# Send an SDL manifest to the providerakt provider send-manifest deploy.yaml --dseq 12345
# Retrieve the current manifestakt provider get-manifest [dseq]Without --provider, send-manifest attempts every provider holding an active lease. It reports an error unless all active providers accept the manifest.
Migrations
# Migrate hostnames between deploymentsakt provider migrate-hostnames --dseq 12345 --hostnames example.com,app.example.com
# Migrate endpoints between deploymentsakt provider migrate-endpoints --dseq 12345 --endpoints <endpoints>Store Commands
Manage the per-context local deployment store.
# Display local store informationakt store status
# Reconcile tracked accounts with on-chain deployments, leases, and bidsakt store sync [account]
# Export the local store to YAML or JSONakt store export
# Import records from a previously exported fileakt store import <file>The export format is for inspection and backup. It is not a deployable SDL.
Monitor Commands
Real-time dashboards over an RPC WebSocket connection. See Network Monitor.
# Launch hub (defaults to Network dashboard)akt monitor
# Direct dashboardsakt monitor networkakt monitor providerakt monitor oracleakt monitor bmeInside the Network dashboard, 1 opens Overview, 2 Validators, 3 Governance proposals, and 4 Governance parameters. Tab and Shift-Tab switch dashboards.
Flags:
--rpc- RPC endpoint (also accepted as a positional argument)--insecure- Skip TLS verification--clean-cache- Clear cache and start fresh
MCP Command
Start an MCP server for AI assistant integration. See MCP Server.
# Read-only mode (safe for AI agents)akt mcp
# With write tools enabledakt mcp --enable-writes
# Console tools only, no context neededakt mcp --console-api-key <key>Flags:
--enable-writes- Enable write tools (on-chain transactions and provider mutations)--console-api-key- Console API key; overrides the context credential andAKT_CONSOLE_API_KEY
With both rails configured, read-only mode exposes 27 tools and write-enabled mode exposes 33. Ctrl-C and closed stdin both stop the server cleanly.
A Console API key can start a contextless read-only server. --enable-writes requires an explicitly selected context so mutations have an action-log destination. If an optional chain signer cannot initialize, available read tools remain registered while signing-dependent tools are omitted.
Utility Commands
Version
# Short form: version, commit, build dateakt version
# Full build info: version, commit, build date, Go version, platform, build tagsakt version --longCompletion
# Generate a shell completion script (bash, zsh, fish, powershell)akt completion zshOutput Formats
Control output format with --output (-o):
# Pretty table (default): color-coded states, bold identifiersakt query deployment
# JSONakt query deployment -o json
# YAMLakt query deployment -o yaml
# JSONL (workflow commands, for CI/CD)akt deploy deploy.yaml --bid-select cheapest --yes -o jsonl