This guide covers deploying the proxy-router on Akash Network. The deployment provides API access via Swagger interface — no GUI or wallet components.

​
Pre-requisites

  • AI model reachable on a private endpoint (e.g. http://model.example:8080).
  • Funded wallet (MOR + ETH on BASE) and its private key.
  • Akash account with deployment experience.
The final endpoint URL is only available after provider selection and Akash deployment.

​
Configuration model

Unlike a typical Docker run, on Akash the proxy-router uses environment variables instead of volume mounts for improved reliability:
VariablePurpose
COOKIE_CONTENTAPI authentication: username:password
MODELS_CONFIG_CONTENTSingle-line JSON for model endpoints (see models-config)
WALLET_PRIVATE_KEYFor blockchain interactions
Plus chain ID, contract addresses, etc.See Env: proxy-router

​
Deployment

1

Prepare the SDL

Download and customize docs/02.2-proxy-router-akash.yml. Minimum proxy-router image version: v2.3.0 (use a newer release tag for current features). Configure:
  • Wallet private key
  • API credentials (COOKIE_CONTENT)
  • MODELS_CONFIG_CONTENT (single-line JSON)
Save securely — the SDL contains sensitive data.
2

Deploy

In the Akash Dashboard: Deploy → Custom Container. Upload your SDL. Select a provider and deploy. Verify status and logs.
3

Configure endpoints

Update WEB_PUBLIC_URL with the provider URL and port. Note both API port (8082) and proxy-router port (3333). Format: http://provider.example:port.
4

Register provider on chain

Open http://provider.example:port/swagger/index.html. Authenticate with your COOKIE_CONTENT credentials. Update the provider endpoint via POST /blockchain/providers:
{
  "endpoint": "provider.example:proxy_port",
  "stake": "123000000000"
}
Verify with GET /blockchain/providers. Continue with model + bid registration in Register on chain.

​
Sample logs

A successful Akash startup looks like the screenshot at docs/images/akash_good_start.png.