AIOZ Pin: The Ultimate Web3 IPFS Storage Solution

AIOZ Pin: The Ultimate Web3 IPFS Storage Solution

AIOZ Pin is an IPFS pinning and storage service on AIOZ DePIN. You upload a file or pin an existing CID, AIOZ Pin keeps it pinned on IPFS, and you serve it through a public or premium gateway, with an API, Node.js SDK, CLI and NFT API on top.

Updated Nov 5, 2026: rewritten against the current AIOZ Pin docs. We removed the 2024 "unlimited pinned files" claim, added gateway limits, image optimization, the NFT API, SDK, CLI and billing rules, and replaced old app screenshots with a diagram.

AIOZ Pin was formerly called W3IPFS, as the note on our AIOZ Network Vision Paper records. This version follows the AIOZ Pin docs as they stand today.

What Is AIOZ Pin?

IPFS finds files by their content identifier (CID), a hash of the data, rather than by a server address. Nodes cache content that passes through them, but caches fill up and garbage collection clears them. Pinning tells a node to keep a CID so it stays online. If those terms are new, our IPFS glossary of CIDs, pinning and gateways defines them in plain language.

AIOZ Pin runs the pinning nodes for you, so you don't have to manage and monitor your own IPFS node. The docs describe three core parts: file pinning, NFT management and premium gateways. Around them sit scoped API keys, a Node.js SDK, a command line tool, image optimization on the gateway and a billing API. For a longer walkthrough, see how AIOZ Pin works from upload to gateway.

Diagram of how AIOZ Pin works: web upload, Pinning API, pin by CID, Pinning Service API, SDK, CLI and NFT API feed AIOZ Pin on AIOZ DePIN nodes, which serve files through public and premium gateways with image optimization
How AIOZ Pin works, based on the AIOZ Pin docs as of November 5, 2026.

How Do You Pin Files on AIOZ Pin?

You have three routes in, and they all end with a CID you can share.

  • Web app: the Quick Start walks you through sign-in, a token top-up, and the Add files then Upload flow.
  • API upload: the Pinning API takes a file or a directory at POST /api/pinning, with optional metadata and options such as cid_version and wrap_with_directory.
  • Pin by CID: if the content is already on IPFS, POST /api/pinning/pinByHash with hash_to_pin pins it without a re-upload.

The same API lets you get a pin by ID, list your pins with filters and sorting, and unpin. Each request carries a pinning_api_key and pinning_secret_key header pair. Keys can be scoped, for example to listing pins, pinning by hash or unpinning, and the secret is shown only once. Our guide to AIOZ Pin API keys and scopes covers how to store and limit them.

AIOZ Pin also supports the IPFS Pinning Service API, the shared spec that lets IPFS tools talk to any pinning service. The AIOZ Pin PSA page gives the endpoint https://api.aiozpin.network/api/psa/. You sign in with a code sent to your email, get an access token, then register the service in the IPFS CLI with ipfs pin remote service add. After that, ipfs pin remote add --service=pin pins a CID from your own node. These commands come from the docs (not run for this update).

The Limit page sets the API at 180 requests per minute, while routes under /users/ and /apiKeys/, and the PSA list endpoint, allow 60 per minute. To see how pinning services compare as a category, read what an IPFS pinning service does and how to choose one.

Gateways and Image Optimization

A gateway turns /ipfs/<CID> into a normal HTTPS link, so browsers and apps without IPFS support can load your files. AIOZ Pin has a public gateway for testing and a premium gateway for production.

The public gateway at public.aiozpin.network needs no account, and the docs reserve it for testing or very low traffic. Each CID has a global limit of 15 requests per minute, and each IP address gets 200 requests per minute.

A premium gateway, which our 2025 roadmap calls a dedicated gateway, is the one to use in production. It has no set rate limit and serves from more than 200 edge-caching locations. Bandwidth is the data your gateway sends, and the file type does not change the count. Free plan users get a limited premium gateway that serves single files such as images, video and audio, but not HTML or scripts. If your balance runs out, the premium gateway switches off and your pins stay reachable through the public gateway. The trade-offs are laid out in free versus paid IPFS gateways on AIOZ Pin.

Image optimization works through query parameters on the gateway URL, so you can set img-width, img-height, img-fit (scale-down, contain, cover, crop or pad), img-quality from 1 to 100, and img-format=webp. Other options handle pixel ratio, sharpening, animation and EXIF metadata. It covers bmp, gif, jpg, jpeg, png and webp files, and at least one option must be set. That lets you store one original image and serve a thumbnail, a card and a full-size view from the same CID.

The NFT API, SDK and CLI

The NFT API pins an NFT's asset and its metadata JSON in one multipart request to POST /api/nft/. The asset can be a file, or a CID you pass as a query parameter. The metadata holds a name, a description and properties such as traits. The response returns both an asset CID and a metadata CID, which your contract can reference. You can then fetch an NFT by ID or list all of yours. The docs also include tutorials for ERC-1155 metadata and custom metadata.

For code, the SDKs page lists the official Node.js SDK, published on npm as @aioznetwork/aioz-pin-sdk. It is an ES module, so your project needs "type": "module", and methods such as pinFilesToIPFS and pinFolderToIPFS cover single files and whole folders.

If you prefer a terminal, the pinning CLI on GitHub is a Go tool you build from source. It logs in with your key and secret, pins a file, a folder or a hash, lists pins, and unpins by ID, with results printed as JSON. The docs also describe an AIOZ Pin MCP server that connects MCP-compatible super intelligence clients to the same pinning, NFT, gateway and billing tools.

How Much Does AIOZ Pin Cost?

AIOZ Pin bills daily from a token wallet, and here is what the Payment page says, as of November 5, 2026:

  • A wallet is created with your account, and it accepts only AIOZ tokens.
  • Deposits are credited at the AIOZ/USDT market rate at the time of deposit. The minimum is more than 0.01 AIOZ; smaller deposits are recorded and credited once they add up.
  • Billing is calculated from daily storage and bandwidth use. Storage costs $20 per 1 TB per month, divided by the days in the month. Bandwidth costs $20 per 1 TB, divided the same way.
  • The first 40,000 pinned files are free. After that, each extra 1,000 pinned files costs $0.10.

Your balance is deducted daily, and a usage history tab shows each day's storage, bandwidth and cost. The Billing API returns the same data: this month's usage, historical usage and top-ups. For worked examples at different sizes, see the AIOZ Pin pricing breakdown.

How AIOZ Pin Runs on AIOZ DePIN

AIOZ Pin is the top layer of AIOZ DePIN, our network of nodes run by operators around the world. Operators share spare storage, bandwidth and compute from their own computers, and they may receive AIOZ token rewards based on verified work and uptime. On November 5, 2026, the AIOZ DePIN page listed 330,675 total DePINs, a count that covers every AIOZ product on the network, Pin included.

The infrastructure page names what Pin gets from that network: smart caching keeps frequently requested content close to users, and smart routing sends each request to the nearest available node. Built-in CDN capabilities spread delivery across the network, and the docs add that using spare resources across many computers lowers the cost of storing and delivering content.

What Changed Since the 2024 Version

  • The 2024 post promised unlimited pinned files. Today the first 40,000 are free and extra files cost $0.10 per 1,000.
  • The old "300,000+ edge nodes" line is replaced by a dated count: 330,675 total DePINs on November 5, 2026.
  • Gateway sections now give the public gateway limits, the premium gateway's 200+ locations and the free plan's limited gateway.
  • New sections cover image optimization, the Pinning Service API endpoint, the Node.js SDK, the Go CLI, the Billing API and the MCP server.
  • We cut claims the docs don't support, such as IPFS being "cold storage", and the speculative "future" section.

FAQ

Do I need to run my own IPFS node to use AIOZ Pin?

No, because AIOZ Pin runs the pinning nodes for you. You only need your own IPFS node if you want to pin from it through the Pinning Service API.

Can I pin content that is already on IPFS?

Yes. Send its CID to POST /api/pinning/pinByHash, or use ipfs pin remote add through the Pinning Service API, so you don't need to upload the file again.

Is AIOZ Pin free to start?

Partly. The first 40,000 pinned files have no per-file fee, and free plan users get a limited premium gateway. Storage and bandwidth are billed daily from your AIOZ token balance at the Payment page rates.

What happens if my balance runs out?

The docs say your premium gateway switches off automatically, and your pinned files stay reachable through the public gateway.

Which image formats can the gateway optimize?

The docs list bmp, gif, jpg, jpeg, png and webp, and you resize or convert them by adding img- query parameters to the gateway URL.

What are the API rate limits?

The API allows 180 requests per minute in general and 60 per minute for /users/, /apiKeys/ and the Pinning Service API list endpoint, while premium gateways have no set limit.

About the AIOZ Network

AIOZ Network is a DePIN for AIOZ AI, AIOZ Storage and AIOZ Stream.

AIOZ empowers a fast, secure and decentralized future.

Powered by a global network of DePINs, AIOZ rewards you for sharing your computational resources for storing, transcoding, and streaming digital media content and powering decentralized AI computation.

Find Us

Website | AIOZ Block Explorer | Twitter | Telegram