
AIOZ Pin has exactly three line items on a bill: storage, bandwidth, and pinned files past a free threshold. No plan names to choose between, no annual-vs-monthly decision, no feature gate locked behind a higher tier. This article covers the real numbers, how billing actually runs against a wallet, and how the whole structure holds up against Pinata and Filebase.
TL;DR:
Three numbers, per AIOZ's own payment documentation: $20 per TB per month for storage, $20 per TB for bandwidth, and the first 40,000 pinned files free, then $0.10 per additional 1,000. That's the entire rate card. No per-request fees, no separate charge for API calls, no volume discount tiers published anywhere. What you store, what you serve, and how many distinct files you pin are the only three things AIOZ Pin bills for.
Both storage and bandwidth are billed daily, not monthly, per AIOZ's own documentation: the $20/TB monthly rate gets divided across the days in that month and deducted incrementally as usage accrues, rather than charged as one lump sum on a billing date. Pinned-file count works differently, it's a running total against the 40,000-file free threshold, billed once you cross it, independent of storage or bandwidth.
Funding works through a wallet, not a credit card. AIOZ Pin auto-generates a wallet address for every account, and depositing AIOZ tokens to it converts to usable credit at the AIOZ/USDT market rate at the moment of deposit, not a fixed rate and not the rate whenever the credit eventually gets spent. The documented minimum deposit is just over 0.01 AIOZ; smaller amounts aren't discarded, they accumulate until the combined total crosses that threshold.
Say a project stores 2TB and serves 1TB of bandwidth in a month, with 60,000 pinned files. Storage runs 2TB × $20 = $40. Bandwidth runs 1TB × $20 = $20. Pinned files: 20,000 over the 40,000-file free threshold, so 20 × $0.10 = $2. Total for the month: $62, deducted from the wallet in roughly $2/day increments rather than billed as one invoice. Double the storage to 4TB with the same bandwidth and pin count, and the bill becomes $80 + $20 + $2 = $102. Because storage and bandwidth are both flat and linear, cost scales directly with usage, no step-function jump at a plan boundary.
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 the pinned files can still be accessed through the public gateway. What the docs still don't specify is what happens to the pins themselves: no minimum-balance requirement, no stated grace period, no documented deletion policy. That remaining gap is worth knowing about directly rather than assuming a specific outcome. The practical move is monitoring spend proactively through the Billing API rather than finding out empirically what happens at zero.
| Provider | Entry Cost | Storage | Bandwidth | Pinned Files |
|---|---|---|---|---|
| AIOZ Pin | $0 (pay-as-you-go) | $20/TB/month | $20/TB | 40,000 free, then $0.10/1,000 |
| Pinata Picnic | $20/month | 1TB included, then $0.07/GB (~$70/TB) | 500GB included, then $0.10/GB (~$100/TB) | 5 million files (Pinata pricing page, checked Oct 19, 2026) |
| Pinata Fiesta | $100/month | 5TB included, then $0.035/GB (~$35/TB) | 2.5TB included, then $0.08/GB (~$80/TB) | 10 million files (Pinata pricing page, checked Oct 19, 2026) |
| Filebase Pro | $7.50/month | 500GB included, then $0.015/GB (~$15/TB) | 250GB IPFS egress included, then $0.015/GB (~$15/TB) | Unlimited |
At low, pay-as-you-go usage, AIOZ Pin's lack of a monthly minimum is the clearest win, a project storing a few hundred GB pays for exactly that, with no $7.50-$20 floor before the first byte. Against Pinata specifically, AIOZ Pin's $20/TB storage rate beats Picnic's effective overage rate outright and is competitive with Fiesta's. Against Filebase, the picture flips: Filebase's $15/TB overage rate on both storage and bandwidth, plus a genuinely unlimited pin count with no per-file fee at any volume, undercuts AIOZ Pin for a project pinning millions of small files, exactly the scenario AIOZ Pin's 40,000-free-then-per-1,000 model starts costing real money for reasons unrelated to actual storage or bandwidth used.
How much does AIOZ Pin cost per TB? $20 per TB per month for storage and $20 per TB for bandwidth, both prorated daily, per AIOZ's official payment documentation.
Does AIOZ Pin have a free tier? Not for storage or bandwidth, both are billed from the first byte. The only free allowance is the first 40,000 pinned files.
Are there subscription plans to choose between? No. AIOZ Pin runs entirely pay-as-you-go, funded by a wallet, there are no named Basic/Pro/Enterprise tiers.
What happens if my AIOZ Pin wallet balance hits zero? AIOZ's premium gateways documentation says 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 publicly documented, so rather than assume a grace period exists, monitor usage through the Billing API and top up proactively.
Is AIOZ Pin cheaper than Pinata? On storage and bandwidth rates, generally yes, especially against Pinata's Picnic tier overage pricing. Pinata's paid plans include a file allowance with no per-file fee (5 million files on Picnic and 10 million on Fiesta, per Pinata's pricing page on Oct 19, 2026), unlike AIOZ Pin's threshold.
Is AIOZ Pin the cheapest IPFS pinning option available? No. Filebase's Pro tier currently publishes lower per-GB overage rates and unlimited pinned files at any volume, undercutting AIOZ Pin specifically for projects pinning very large numbers of files.

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.