
Pinata IPFS pricing is plan-based: Free, Picnic at $20 a month, and Fiesta at $100, each with fixed storage, bandwidth, and request quotas plus overage fees. AIOZ Pin has no plans and charges only for use: $20 per TB of storage per month and $20 per TB of bandwidth.
TL;DR:
Updated Oct 19, 2026: rechecked both price lists, added Pinata's request quotas, overage, and agent-based plans, a small-project example, and remote pinning commands.
AIOZ Pin is a pay-as-you-go IPFS pinning service on the AIOZ DePIN, funded from an AIOZ token wallet. Pinata is a subscription pinning service with a free tier and two paid plans. Both implement the IPFS Pinning Service API, so tools written against that standard can switch by changing the endpoint and key.
| AIOZ Pin | Pinata | |
|---|---|---|
| Pricing model | $20/TB per month storage, $20/TB bandwidth, billed daily | Plans: Free, Picnic $20/month, Fiesta $100/month |
| Free allowance | 40,000 pinned files; storage and bandwidth billed from the first GB | 1 GB storage, 500 files, 10 GB bandwidth, 10K requests |
| Requests | No per-request fee listed; 180 requests/min API rate limit | 10K / 1M / 5M a month included, then $0.20 or $0.15 per 10K |
| Files | $0.10 per 1,000 pins past 40,000 | 500 / 5 million / 10 million files by plan |
| Payment | AIOZ token wallet | Monthly subscription |
| Gateways | Public gateway, plus premium gateways with no predefined rate limit | 1 gateway on Free and Picnic, 3 on Fiesta, CDN on paid plans |
| NFT support | NFT API and SDK pinNft: asset and metadata in one call | Minting tutorials on its blog |
Pinata's pricing page on Oct 19, 2026 lists three self-serve plans. Free gives you 1 GB of storage, 500 files, 10 GB of bandwidth, and 10,000 requests a month. Picnic costs $20 a month for 1 TB of storage, 5 million files, 500 GB of bandwidth, and 1 million requests. Fiesta costs $100 a month for 5 TB, 10 million files, 2.5 TB of bandwidth, and 5 million requests.
Past those caps, Picnic charges $0.07 per GB of storage, $0.10 per GB of bandwidth, and $0.20 per 10,000 requests. Fiesta drops those to $0.035, $0.08, and $0.15. The page now also leads each plan with an agent count (0, 1, or 3), which comes from Pinata's newer agents product. If you only need pinning, you can ignore that line and compare the storage numbers.
The AIOZ Pin payment docs list $20 per TB per month for storage and $20 per TB for bandwidth, billed as a daily rate from your wallet. The first 40,000 pinned files are free, then each extra 1,000 costs $0.10. You fund the wallet with AIOZ tokens, with a minimum deposit of just over 0.01 AIOZ, credited at the AIOZ/USDT rate when the deposit lands.
The docs list no per-request charge; instead, the limit page caps the API at 180 requests per minute, or 60 per minute for the users and API-key routes. Our AIOZ Pin pricing breakdown works through a full bill.
These examples count storage and bandwidth only, and assume you stay inside Pinata's file and request quotas:
| Monthly usage | AIOZ Pin | Pinata |
|---|---|---|
| 50 GB stored, 20 GB served | $1.00 + $0.40 = $1.40 | $20 (Picnic; Free stops at 1 GB) |
| 500 GB stored, 200 GB served | $10 + $4 = $14 | $20 (Picnic) |
| 6 TB stored, 3 TB served | $120 + $60 = $180 | $100 + $35 + $40 = $175 (Fiesta plus overage) |
A Pinata plan costs the same whether you use a tenth of it or all of it, so small and mid-size projects pay for headroom they don't use. Once you pass Fiesta's caps, Pinata's lower overage rates catch up, and at 6 TB it comes out $5 cheaper.
Two more lines can change your result. Heavy API traffic adds request overage on Pinata, for example $15 for each extra million requests on Fiesta. Millions of tiny files favor Pinata's file allowance, since AIOZ Pin charges $0.10 per 1,000 pins past 40,000. Run your real numbers for both before you commit.
NFT management is one of the three components on the AIOZ Pin infrastructure page. In practice, that means POST /api/nft/, which uploads an asset and its metadata JSON in one request and returns both CIDs. The Node.js SDK, @aioznetwork/aioz-pin-sdk, wraps it as pinNft, so you never end up with an image pinned and its metadata missing.
Pinata doesn't sell a separate NFT product, and its blog publishes step-by-step minting tutorials instead, such as minting with Foundry, Viem, and Pinata. If you want one call that pins NFT data correctly, AIOZ Pin is more direct. If you are building a custom minting stack, Pinata's tutorials go deeper. NFT.Storage Classic stopped taking uploads in 2024, so it is no longer a third option; our NFT.Storage alternatives guide covers what replaced it.
AIOZ Pin gives you a public gateway for testing, limited to 15 requests per minute per CID and 200 per minute per IP. Its premium gateways have no predefined rate limit and serve from 200+ edge caching locations. Pinata includes one gateway on Free and Picnic and three on Fiesta, with CDN on the paid plans, and its feature list includes custom gateway domains.
Both services resize and convert images at the gateway through URL parameters, so you don't store a copy per size. AIOZ Pin's image resizing parameters include fit modes, a device-pixel-ratio option for sharp images on Hi-DPI screens, and a switch to keep GIF animation. Feature for feature, the two are close here.
Pick AIOZ Pin if your usage sits below Pinata's plan caps, you want to pay only for what you use, and you are comfortable funding the account with AIOZ tokens. It also fits if you want NFT assets and metadata pinned in one call. Pick Pinata if you want a free tier to prototype on, or you run well past 5 TB a month where its overage rates win. Its minting tutorials help too. Because both follow the same pinning standard, the honest test is to pin a sample of your own files on each.
We implement the IPFS Pinning Services API, so you can add AIOZ Pin next to Pinata in the same Kubo node and compare them on real CIDs. These commands come from the AIOZ Pin Pinning Services API docs, where YOUR_AUTH_JWT is the access token from your email login:
ipfs pin remote service add pin https://api.aiozpin.network/api/psa/ YOUR_AUTH_JWT
ipfs pin remote add --service=pin --name=<human-readable-name> YOUR_CID
ipfs pin remote ls --service=pin
ipfs pin remote ls --service=pin --status=queued,pinning,failedPinning by CID keeps the same content address when you move, so your existing ipfs:// links keep working. To watch costs while you test, GET /api/billing/thisMonthUsage returns your storage and bandwidth usage and cost so far this month.
Next step: the AIOZ Pin Quick Start covers top-up and your first pin.
Is AIOZ Pin cheaper than Pinata? Below Pinata's plan caps it usually is: 500 GB stored and 200 GB served costs about $14 on AIOZ Pin against $20 for Picnic. Past 5 TB, the two come within a few dollars.
Does Pinata charge for API requests? Yes, each plan includes a monthly request quota of 10K, 1M, or 5M, and extra requests cost $0.20 per 10,000 on Picnic or $0.15 on Fiesta.
Does AIOZ Pin have a free tier? Not for storage or bandwidth, which are billed from the first GB, but the first 40,000 pinned files carry no pin fee.
What are agents on Pinata's pricing page? They belong to Pinata's newer agents product, and each plan lists 0, 1, or 3; they don't change the pinning quotas.
Can I migrate from Pinata to AIOZ Pin without rewriting my code? Mostly, since both implement the IPFS Pinning Service API, but vendor-specific features such as Pinata's groups or AIOZ Pin's NFT endpoint need their own changes.
Does AIOZ Pin support NFT metadata pinning? Yes, POST /api/nft/ pins an asset and its metadata JSON together and returns both CIDs.

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.