Akash Network

Service overview

What is Akash Network?

peaqOS exposes Akash through a native adapter — the operator brings their own Akash Console API key and sends it request-scoped as `providerCredentials.akash.consoleApiKey`; no Akash credential is configured inside peaqOS. Akash usage is billed through the operator’s Akash Console account, and peaqOS records the order, execution, outcome, and audit trail. Akash itself is a decentralized GPU and CPU marketplace running on its own Cosmos-SDK L1 (chain migration under evaluation). Tenants describe workloads in an SDL manifest, providers bid in a reverse auction, and the winning lease runs on H100s, A100s, RTX 4090s, RTX A6000s, or CPU-only nodes anywhere in the world — typically 70-80% cheaper than centralized clouds. Under Burn-Mint Equilibrium (activated March 2026), AKT is burned to mint Akash Compute Token (ACT) for stable USD-denominated pricing.

Adapter operations

Behind peaqOS — operator calls peaqOS, peaqOS calls Akash Console.

• GETlist-deployments

  List the operator’s active and historical deployments on Akash Console.

• POSTcreate-deployment

  Submit an SDL manifest and open an escrow deposit — Akash returns a deployment sequence (dseq).

• GETlist-bids

  List provider bids received for a deployment sequence.

• POSTcreate-lease

  Accept a winning bid and start the lease using the manifest, dseq, gseq, and provider.

• POSTdeposit-deployment

  Top up the escrow on an active deployment so the lease keeps running.

• GETget-deployment

  Fetch deployment status, active leases, and remaining escrow balance.

• PATCHupdate-deployment

  Update the SDL manifest for an active deployment.

• DELETEclose-deployment

  Close the deployment and release the remaining escrow.

Integration fields

Wire Akash Network into peaqOS

serviceId

akash:console-deployment:native

skillKey

akash-compute-deployment

serviceType

compute.marketplace

executionMode

native

credential path

providerCredentials.akash.consoleApiKey

FAQ

Questions agents ask about Akash Network

• Does it require manual setup?+

  Yes. Follow the provider’s setup docs to create an account and obtain the required API credentials. Send them as request-scoped provider credentials when your agent calls peaqOS, and peaqOS routes calls to the provider on your behalf.

• How does payment work?+

  No peaqOS marketplace payment runs for this service. Usage is billed by the provider on your account at whatever rate they set. peaqOS still records the order, execution, and audit receipt so robots have provable history.

• How deterministic are responses?+

  Akash deployment state is deterministic once a lease is created, but bids, selected provider, lease URI, and startup time depend on provider availability. peaqOS records the final order, run, outcome, and audit trail.

• What happens if a request fails?+

  The provider returns its own error response — auth, rate-limit, quota, etc. peaqOS surfaces it to the agent, which can retry, refresh credentials, or fall back to another service.