Install provider-services CLI

Get set up with the provider-services CLI to deploy on Akash Network.

This guide walks you through installing the CLI, creating a wallet, and funding your account.

Install provider-services

Select your operating system:

brew tap akash-network/tap
brew install akash-provider-services

cd ~/Downloads

# Download the latest release
curl -sfL https://raw.githubusercontent.com/akash-network/provider/main/install.sh | bash

sudo mv ./bin/provider-services /usr/local/bin

provider-services version

v0.10.0

cd ~

# Install dependencies
apt install jq -y
apt install unzip -y

# Download and install provider-services
curl -sfL https://raw.githubusercontent.com/akash-network/provider/main/install.sh | bash

vi /etc/environment

/root/bin

. /etc/environment

provider-services version

v0.10.0

provider-services version

$ go get -d github.com/akash-network/provider
$ cd $GOPATH/src/github.com/akash-network/provider
$ AKASH_NET="https://raw.githubusercontent.com/akash-network/net/main/mainnet"
$ AKASH_VERSION="$(curl -s https://api.github.com/repos/akash-network/provider/releases/latest | jq -r '.tag_name')"
$ git checkout "$AKASH_VERSION"
$ make deps-install
$ make install

provider-services version

Create an Account

Configure the name of your key:

AKASH_KEY_NAME=my-wallet

Verify the variable is set:

echo $AKASH_KEY_NAME

Set the keyring backend:

AKASH_KEYRING_BACKEND=os

Create an Akash account:

provider-services keys add $AKASH_KEY_NAME

Read the output and save your mnemonic phrase in a safe place.

Set your account address as a variable:

export AKASH_ACCOUNT_ADDRESS="$(provider-services keys show $AKASH_KEY_NAME -a)"

echo $AKASH_ACCOUNT_ADDRESS

Note that if you close your Terminal window this variable will not be saved.

Fund your Account

A minimum deposit of 0.5 AKT is required to deploy on Akash. A small transaction fee is also applied to deployment leases.

Get AKT tokens:

• Buying AKT from an exchange / swapping to AKT
• Join the Akash Community

Configure your Network

Configure the base URL for the Akash Network:

AKASH_NET="https://raw.githubusercontent.com/akash-network/net/main/mainnet"

Version

AKASH_VERSION="$(curl -s https://api.github.com/repos/akash-network/provider/releases/latest | jq -r '.tag_name')"

Chain ID

export AKASH_CHAIN_ID="$(curl -s "$AKASH_NET/chain-id.txt")"

Network Node

export AKASH_NODE="$(curl -s "$AKASH_NET/rpc-nodes.txt" | shuf -n 1)"

Confirm Network Variables

echo $AKASH_NODE $AKASH_CHAIN_ID $AKASH_KEYRING_BACKEND

You should see something similar to:

http://135.181.60.250:26657 akashnet-2 os

Set Additional Environment Variables

export AKASH_GAS=auto
export AKASH_GAS_ADJUSTMENT=1.25
export AKASH_GAS_PRICES=0.025uakt
export AKASH_SIGN_MODE=amino-json

Check your Account Balance

provider-services query bank balances --node $AKASH_NODE $AKASH_ACCOUNT_ADDRESS

You should see a response similar to:

balances:
- amount: "93000637"
  denom: uakt
pagination:
  next_key: null
  total: "0"

Note: Balance is denominated in uAKT (AKT x 10^-6). In the example above, the account has a balance of 93 AKT.

Your account must have a minimum balance of 0.5 AKT to create a deployment.

Authentication

Akash provider services support two authentication methods:

JWT Authentication (Default - Recommended)

JWT (JSON Web Tokens) is the default and recommended authentication method for provider-services v0.10.0+.

Advantages:

• No blockchain transactions required
• No certificate expiration to manage
• Simpler setup
• No additional costs

JWT tokens are automatically generated and managed by provider-services CLI. No setup required!

When you run deployment commands, the CLI automatically:

1. Signs requests with your account’s private key
2. Creates JWT tokens
3. Sends authenticated requests to providers

You’re ready to deploy! Jump to Next Steps.

mTLS Certificate Authentication (Optional)

mTLS (mutual TLS) certificates are an alternative authentication method.

When to use mTLS:

• You require certificate-based authentication
• You’re integrating with systems that require X.509 certificates
• You prefer blockchain-stored credentials

Generate Certificate

provider-services tx cert generate client --from $AKASH_KEY_NAME

Note: If it errors with Error: certificate error: cannot overwrite certificate, add --overwrite flag.

Publish Certificate to Blockchain

provider-services tx cert publish client --from $AKASH_KEY_NAME

Certificate Notes:

• Certificates cost transaction fees (~0.01 AKT)
• Valid for one year, then must be renewed
• Stored on the Akash blockchain
• Can be revoked and regenerated

Next Steps

Now that you’re set up, you can:

• CLI Configuration - Configure networks and advanced settings
• CLI Commands Reference - Learn all available commands
• Core Concepts - Understand how Akash works

Troubleshooting

”command not found: provider-services”

The binary isn’t in your PATH. Try:

# Find where it's installed
which provider-services

# Add to PATH (Linux/macOS)
export PATH=$PATH:/path/to/provider-services

“account not found”

Your wallet hasn’t been created or funded yet. Go back to Create an Account and Fund your Account.

”insufficient fees”

Increase your gas prices:

export AKASH_GAS_PRICES=0.05uakt

RPC Node Issues

If the default RPC node is down, try an alternative:

export AKASH_NODE=https://rpc.akash.forbole.com:443
# or
export AKASH_NODE=https://akash-rpc.polkachu.com:443

Need Help?

• Akash Discord - Get help from the community
• GitHub Issues - Report bugs