An Akash provider address is not the same record as a wallet
To see whether the directory marks that provider online and how much GPU capacity it advertises, use the provider address. A wallet answers a different question: what that account holds. Do not substitute one for the other.
| Identifier you hold | After you paste it into the Akash monitor | Where to read the original |
|---|---|---|
| Provider address (lowercase akash1) | Opens name, online flag, check time, and GPU capacity from the directory | Provider directory |
| Tenant wallet | Does not become this provider’s directory card | Deployments and leases stay in the official console |
| Deployment id | Not the provider lookup key | That deployment’s own page in the console |
| AKT or USDC in a wallet | The monitor does not show either balance | The official wallet or explorer you use to hold coins; a balance is not directory capacity |
A directory row that will not open is usually the wrong identifier. The Akash monitor looks up one provider record in the provider directory. The key is the provider’s own public address: lowercase, starting with akash1. The official site splits the market in two: providers list hardware and earn from deployments; tenants configure a container, review bids, and open a lease after they accept one. A tenant wallet is the paying side, not the provider record in the directory. One provider address may aggregate several physical hosts; the address alone does not prove a physical device count.
What each address answers
A provider address answers whether the directory lists that provider, how the last check marked it online, how much GPU capacity is advertised, how much of that is marked allocated, and what the model text says. A wallet answers what the account holds. Two strings can both start with akash1 without the wallet being the provider. A deployment id is not a directory key either. It points at one workload, not at the whole provider.
What to check before you paste
- Find the provider record in the provider directory and copy the provider address on that row.
- Match letter case. The monitor accepts the lowercase address. An uppercase copy, or one character dropped from a chat log, will not match the row.
- If you only have a lease email or a deployment page, separate the provider column from your wallet column. Paste only the provider column into the Akash monitor.
- If the question is how much AKT or USDC the account holds, stay in the wallet. The monitor card does not rewrite itself into a balance.
What to do next
- Once the card opens, read the online flag and GPUs with how to read the directory row. Do not treat capacity as money already received.
- If you actually wanted the tokens, see AKT and USDC balances are not on this card. When the same wallet is attached to several saved devices, the balance is one shared holding. It is not copied into income once per device.
- Saved-device quota counts saved device records on your account: five per project on Free, 50 on Pro. It is not proof of the provider’s physical host count. Seeing several provider records under one wallet does not automatically use several slots. Separate saved device records do. Binding Akash more than once on the same saved record still counts as one record.
Illustrative case (not a real address, and not a balance)
The directory row says provider North shed and shows one lowercase akash1 address. Your tenant account is a different akash1 string. Pasting the tenant account does not produce North shed’s online flag or “8 GPUs advertised, 2 allocated.” To see that advertised 8, paste the provider address from the directory row. The two strings stand for a provider directory record and an account. Do not add them together. Those 8 GPUs are not 8 physical hosts.
Limits
The official getting-started page is for someone preparing to run a provider: hardware, a domain, the console, and later lease management. It does not define a tenant wallet as the directory lookup key. This page also cannot sign or transfer tokens for you.
Common questions
The address also starts with akash1. Why does it still not open?
akash1 only means it looks like an Akash account address. The directory card also requires that it is that provider’s own address, in lowercase. A tenant wallet can be an akash1 address too.
If several provider records sit under one wallet, do they use several free slots?
Not automatically. Quota counts saved device records on the account: five per project on Free, 50 on Pro. It does not prove how many physical hosts the provider has. Each provider record counts only when you save a separate device record for it. Binding Akash again on the same saved record does not add a record.
Can I use a deployment id as the provider address?
No. A deployment id points at one workload. The provider card accepts only the provider address from the directory.