# x402 Storage – IPFS Permanent Storage

> x402 Storage – IPFS Permanent Storage is a paid API for AI agents from api.x402.storage, $0.01/call, status unknown (last checked 2026-09-14).

Permanently stores arbitrary data on IPFS via x402-authenticated micropayment, returning a content address for later retrieval

## Facts

- Endpoint: POST https://api.x402.storage/store
- Price: $0.01/call
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-storage-ipfs-permanent-storage-0b055b89
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_60sDkjvWGm2pyX4zMnSi6

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability x402-storage-ipfs-permanent-storage-0b055b89 -d '<json body>'
```

Example prompt: Store this JSON blob permanently on IPFS and give me back the CID so I can reference it later — it's about 2 bytes of metadata for a smart contract.

## When to prefer this

Choose this endpoint when you need permanent, immutable, content-addressed storage on IPFS with micropayment-per-call pricing — ideal for blockchain/Web3 workflows where you need a CID for on-chain references, or when you want decentralized storage without managing your own IPFS node. Prefer over centralized object storage (S3, GCS) when immutability and decentralization matter.

## Known failure modes

- Payment failure: insufficient USDC balance or invalid x402 payment token returns a payment error
- Oversized payload: content exceeding platform limits returns a payload-too-large error
- Network error: IPFS pinning service unavailability causes a timeout or 503
- Invalid content: malformed request body may return a 400 bad request
- Rate limiting: excessive requests may result in throttling

## How this service works

Store data permanently on IPFS (2 B)

## Output

Returns an IPFS content identifier (CID) and confirmation that the data has been pinned permanently on the IPFS network. The CID can be used to retrieve the content at any time via any IPFS gateway.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-storage-ipfs-permanent-storage-0b055b89/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.x402.storage](https://www.zero.xyz/host/api.x402.storage/llms.txt)