
The AIOZ Pin wallet is a deposit address created automatically with your account. You fund it with AIOZ tokens, and each deposit becomes credit at the AIOZ/USDT rate at the time it arrives. There is no card option. The billing mechanics post covers prices; this one covers deposits.
TL;DR:
Most cloud storage runs on a familiar pattern: enter a card, get billed monthly, cancel when you're done. AIOZ Pin runs on a different model entirely, pay-as-you-go against a balance you top up yourself, funded with AIOZ tokens rather than fiat currency. There's no monthly invoice, no recurring charge that hits your card automatically, and no subscription tier to upgrade or downgrade between. You put value in, usage draws it down, and when the balance gets low, you send more.
When an account is created, AIOZ Pin automatically generates a wallet address dedicated to receiving deposits for that account. This isn't a shared address or a manually configured one, it's provisioned specifically for your account the moment you sign up, and any AIOZ tokens sent there are attributed to your balance directly. Funding the account is then just a matter of sending AIOZ tokens to that address from wherever you're holding them, an exchange, another wallet, doesn't matter, as long as the tokens are AIOZ.
The documented minimum is just over 0.01 AIOZ tokens. What's less obvious, and worth knowing before assuming a small test deposit vanished, is what happens below that threshold: a deposit under 0.01 AIOZ doesn't get discarded, it gets recorded, and stays pending. Send another small amount later, and once the combined total of everything you've sent crosses 0.01 AIOZ, the full accumulated amount credits to your balance at once. This matters in practice mostly for anyone testing the funding flow with a deliberately small amount first, that test deposit isn't lost, it's just waiting for enough to join it.
AIOZ's own documentation is explicit about this, and it's worth repeating plainly rather than burying it: sending any cryptocurrency other than AIOZ to your deposit address can result in permanent loss of funds. This isn't a general-purpose multi-currency wallet that happens to accept AIOZ, it's provisioned specifically to receive AIOZ tokens, and sending the wrong asset to it isn't a mistake the system is built to recover from. Double-checking the token before sending is a five-second step against an unrecoverable one.
When AIOZ tokens land in your wallet, they convert to usable credit based on the AIOZ/USDT market rate at that exact moment, not at some fixed reference rate and not at whatever the rate happens to be when you eventually spend the credit. This has a real, practical consequence: if AIOZ's price moves significantly after you deposit, your credit balance in dollar terms was locked in at deposit time, it doesn't fluctuate afterward the way holding the raw token would. Depositing during a period of high volatility is worth being aware of for exactly this reason, the conversion is a one-time snapshot, not an ongoing peg.
This series' billing-mechanics article already covers that storage and bandwidth are both billed daily, divided across the days in a month rather than charged as one lump sum. The wallet side of that is straightforward: your credit balance gets deducted directly, incrementally, based on that day's actual usage. There's no separate "invoice" step between usage and deduction, the balance itself is the running total of what you have left, and it drops in near-real-time as storage and bandwidth accrue rather than waiting for a billing cycle to close.
AIOZ's premium gateways documentation answers part of this: if the premium gateway is on and the account runs out of money, the premium gateway option turns off automatically, and pinned files can still be accessed through the public gateway. The payment documentation still doesn't specify what happens to the pins themselves at zero, whether there's a grace period, a warning threshold, or any removal of pinned content. Filling that remaining gap with a confident-sounding assumption would be exactly the kind of unverified claim worth avoiding. The practical answer, until AIOZ's documentation says otherwise, is not to run a balance down to find out: the Billing API exposes current-month usage and historical spend as read endpoints specifically so a project can monitor its own burn rate and top up proactively, rather than treating the wallet balance as something to only check after something's already gone wrong.
Wallet-based billing isn't AIOZ Pin's only option here so much as a deliberate fit for who it's built for: Web3-native projects that already hold and move crypto as a matter of course, for whom depositing AIOZ tokens is a more natural action than entering a card number tied to a traditional payment processor. It also sidesteps the recurring-subscription commitment entirely, there's no tier to overcommit to, no cancellation flow, just a balance that reflects exactly what's been funded and exactly what's been used.
Can I pay for AIOZ Pin with a credit card? No. Funding an AIOZ Pin account works by depositing AIOZ tokens to an auto-generated wallet address, there's no card-based payment option.
What is the minimum deposit for AIOZ Pin? Just over 0.01 AIOZ tokens. Deposits below that aren't lost, they're recorded and accumulate until the combined total crosses the threshold.
What exchange rate is used to convert my AIOZ deposit to credit? The AIOZ/USDT market rate at the exact moment the deposit is received, not a fixed rate and not the rate at whatever point you later spend the credit.
What happens if I send the wrong cryptocurrency to my AIOZ Pin wallet address? It can result in permanent loss of funds, per AIOZ's own documentation. The address is provisioned specifically for AIOZ tokens, not general-purpose crypto.
What happens if my AIOZ Pin wallet balance hits zero? AIOZ's docs say a premium gateway turns off automatically when the account runs out of money, and pinned files can still be accessed through the public gateway. What happens to the pins themselves isn't documented publicly, so rather than assume a grace period exists, monitor usage proactively through the Billing API and top up before the balance runs out.
Is AIOZ Pin's wallet billing the same as a subscription? No. There's no recurring charge or tier to commit to. You fund a balance directly with AIOZ tokens, and usage draws it down daily based on actual storage and bandwidth consumed.

ERC-1155 metadata on IPFS breaks when filenames ignore the {id} rule. Here is the exact 64-character format, a working folder layout, and the per-token option.

AIOZ Pin rate limits in one place: 180 requests per minute for the API, 15 per CID on the public gateway, and no predefined limit on premium gateways.

IPFS pin stuck on Pinning? Here is what Pinning, Pinned, and Failed mean on AIOZ Pin, why big directories can sit there, and how to read a pin's real state.

Two identical files, three IPFS tools, three different CIDs. Here is why that happened for years, and how IPIP-0499 made content addressing deterministic.

AIOZ Pin MCP server setup has two paths: llms.txt lets a super intelligence assistant read the API, the MCP server lets it call 11 tools. Here is each one.

AIOZ Pin bills three flat rates against a token wallet, with no tiers to pick between. Here is what storage, bandwidth and pinned files cost, with examples.