# x402engine IPFS Content Retrieval

> x402engine IPFS Content Retrieval is a paid API for AI agents from x402engine.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Fetches content stored on IPFS by CID via a pay-per-call HTTP 402 micropayment gateway

## Facts

- Endpoint: GET https://x402engine.app/api/ipfs/get
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402engine-ipfs-content-retrieval-8dd2ba8d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5cZ17bbxD6aAICmJUzFNF

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 x402engine-ipfs-content-retrieval-8dd2ba8d
```

Example prompt: Can you fetch the content stored at IPFS CID QmYwAPJzv5CZsnA625s3Xf2nemtYgPpHdWEz79ojWnPbdG for me?

## When to prefer this

Use this endpoint when an AI agent needs to retrieve content from IPFS without operating its own node or gateway — ideal for reading NFT metadata, decentralized app data, or any content-addressed file referenced by a CID on-chain. Prefer this over public IPFS gateways when you need reliable, pay-per-call access integrated into an agent payment flow using USDC or USDm.

## Known failure modes

- Invalid or malformed CID returns an error
- Content not found or unpinned on IPFS network results in a timeout or 404
- Payment failure via HTTP 402 if USDC/USDm balance is insufficient
- Network timeout if IPFS peers holding the content are unreachable
- Large files may be slow or fail if retrieval takes too long

## How this service works

Fetch a file from IPFS by CID via gateway

## Output

Returns the raw content stored at the given IPFS CID — this could be JSON, text, binary data, images, or any other file type that was pinned to IPFS. The response body contains the file content directly.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "cid"
     ],
     "properties": {
      "cid": {
       "type": "string",
       "example": "QmYwAPJzv5CZsnA625s3Xf2nemtYgPpHdWEz79ojWnPbdG",
       "description": "IPFS CID"
      }
     },
     "additionalProperties": false
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402engine-ipfs-content-retrieval-8dd2ba8d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402engine.app](https://www.zero.xyz/host/x402engine.app/llms.txt)