IPFS Content Gateway by Apoth3osis

Name: IPFS Content Gateway
Brand: Apoth3osis
SKU: 68c368f066ed2f66afff5c99
Price: 0.20 USD
Availability: InStock

IPFS Content Gateway

Connector

Available ActionsEach successful request consumes credits as outlined below.

retrieve^20crupload^20crlist^20cr

Details

IPFS Content Gateway provides access to the InterPlanetary File System, a decentralized peer-to-peer network for storing and sharing content using content-addressed identifiers. The retrieval function fetches data from IPFS by CID (Content Identifier) with automatic failover across seven public gateways including ipfs.io, Cloudflare IPFS, and Pinata, ensuring high availability even when individual gateways are slow or unavailable. Content retrieval automatically detects whether the response is text or binary data and returns appropriate previews with full metadata including content type, size, and response headers. The upload function accepts base64-encoded files up to 10MB and pins them to IPFS through pinning services that ensure content remains available on the network. Users can provide their own API credentials for Pinata, Web3.Storage, or NFT.Storage, or use shared infrastructure for convenience. Each upload returns the permanent CID along with multiple gateway URLs for immediate access. The list function provides a complete history of uploads including filenames, sizes, upload dates, and ready-to-use gateway links, with aggregate statistics on total storage used.

Use Cases

IPFS content retrieval, decentralized storage access, CID content lookup, IPFS gateway access, content-addressed file retrieval, distributed file download, IPFS file upload, decentralized file hosting, permanent content storage, immutable file storage, NFT metadata hosting, NFT asset storage, Web3 content storage, blockchain data storage, decentralized application storage, dApp file hosting, Pinata file upload, Web3.Storage integration, NFT.Storage upload, IPFS pinning service, content pinning, permanent file hosting, censorship-resistant storage, distributed content delivery, peer-to-peer file sharing, IPFS CID generation, content hash storage, verifiable content storage, AI agent decentralized storage, LLM Web3 integration, automation IPFS upload, workflow decentralized storage, multi-gateway IPFS access, reliable IPFS retrieval, IPFS upload tracking, decentralized asset management, Web3 file management, blockchain file storage, immutable document storage, distributed backup storage

Actions(3)

retrieve^20cr1 param(1 required)

Fetch content from IPFS by its Content Identifier (CID). Supports both CIDv0 (Qm...) and CIDv1 (bafy...) formats. Multiple gateways are tried automatically for reliability.

cidrequiredstring

IPFS Content Identifier. Supports CIDv0 (Qm...) and CIDv1 (bafy...) formats. Example: 'QmYwAPJzv5CZsnA625s3Xf2nemtYgPpHdWEz79ojWnPbdG'

upload^20cr4 params(2 required)

Upload a file to IPFS. The file is pinned so it remains available on the network. Maximum file size is 10MB. Files must be base64-encoded before uploading.

contentrequiredstring

Base64-encoded file content. Maximum file size: 10MB. Encode your file content as base64 before sending.

filenamerequiredstring

Original filename with extension. Example: 'document.pdf' or 'image.png'

pinning_api_keystring

Optional API key for your own pinning service (Pinata, Web3.Storage, or NFT.Storage). If not provided, shared service credentials will be used.

pinning_servicestring

Pinning service to use with pinning_api_key. Required if pinning_api_key is provided.

Values:

pinataweb3storagenftstorage

list^20cr0 params

List all files previously uploaded through this tool, sorted by most recent first. Returns upload history with CIDs, filenames, sizes, dates, and gateway URLs.

No parameters for this action.

Connect Your Agent In 5 Min

Use hosted MCP first, or install the local STDIO fallback when your client requires a command

Hosted Streamable HTTPS

Use the hosted endpoint directly in clients that support remote MCP. Store your Bearer token in the client config or secret field.

Endpoint: https://api.agentpmt.com/mcp
Authorization: Bearer <AGENTPMT_BEARER_TOKEN>

Full connection guide

Local STDIO Fallback

Use the local router for Claude Code, Codex, Cursor, Zed, and other clients that require a command-based MCP server. The router forwards requests to the hosted endpoint and does not execute tools locally.

npm install -g @agentpmt/mcp-routeragentpmt-setup

curl -X POST "https://api.agentpmt.com/products/purchase" \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer ********" \
  -d '{
    "product_id": "68c368f066ed2f66afff5c99",
    "parameters": {
      "action": "retrieve",
      "cid": "example_cid"
    }
  }'

import requests
import json

url = "https://api.agentpmt.com/products/purchase"

headers = {
    "Content-Type": "application/json",
    "Authorization": "Bearer ********"
}

data = {
    "product_id": "68c368f066ed2f66afff5c99",
    "parameters": {
        "action": "retrieve",
        "cid": "example_cid"
    }
}

response = requests.post(url, headers=headers, json=data)
print(response.status_code)
print(response.json())

const url = "https://api.agentpmt.com/products/purchase";

const headers = {
  "Content-Type": "application/json",
  "Authorization": "Bearer ********"
};

const data = {
  product_id: "68c368f066ed2f66afff5c99",
  parameters: {
    "action": "retrieve",
    "cid": "example_cid"
  }
};

fetch(url, {
  method: "POST",
  headers,
  body: JSON.stringify(data)
})
  .then(response => response.json())
  .then(data => console.log(data))
  .catch(error => console.error("Error:", error));

const axios = require('axios');

const url = "https://api.agentpmt.com/products/purchase";

const headers = {
  "Content-Type": "application/json",
  "Authorization": "Bearer ********"
};

const data = {
  product_id: "68c368f066ed2f66afff5c99",
  parameters: {
    "action": "retrieve",
    "cid": "example_cid"
  }
};

axios.post(url, data, { headers })
  .then(response => {
    console.log(response.status);
    console.log(response.data);
  })
  .catch(error => {
    console.error("Error:", error.message);
  });

Login to view your API and budget keys. The example above uses placeholder values. Sign in to see personalized code with your bearer token.

Usage Instructions

Usage guidance provided directly by the developer for this product.

IPFS Content Gateway

Store and retrieve files on the InterPlanetary File System (IPFS) -- a decentralized, content-addressed storage network. Upload files up to 10MB, retrieve content by CID, and list your upload history.

Actions

retrieve

Fetch content from IPFS by its Content Identifier (CID). Supports both CIDv0 (Qm...) and CIDv1 (bafy...) formats. Multiple gateways are tried automatically for reliability.

Required fields:

action — "retrieve"
cid — The IPFS Content Identifier to retrieve

Example:

{
  "action": "retrieve",
  "cid": "QmYwAPJzv5CZsnA625s3Xf2nemtYgPpHdWEz79ojWnPbdG"
}

Response includes: content (text preview up to 10,000 chars or binary indicator), content_type, content_length, gateway_url, and ipfs_url.

upload

Upload a file to IPFS. The file is pinned so it remains available on the network. Maximum file size is 10MB.

Required fields:

action — "upload"
content — Base64-encoded file content
filename — Original filename with extension (e.g., "report.pdf")

Optional fields:

pinning_api_key — Your own pinning service API key for unlimited uploads
pinning_service — Which service your API key is for. Required when pinning_api_key is provided. One of: "pinata", "web3storage", "nftstorage"

Example (using shared service):

{
  "action": "upload",
  "content": "SGVsbG8gV29ybGQh",
  "filename": "hello.txt"
}

Example (using your own Pinata key):

{
  "action": "upload",
  "content": "SGVsbG8gV29ybGQh",
  "filename": "hello.txt",
  "pinning_api_key": "your-pinata-jwt-token",
  "pinning_service": "pinata"
}

Response includes: cid, filename, file_size_bytes, file_size_mb, ipfs_url, and multiple gateway_urls for accessing the content.

list

List all files you have previously uploaded through this tool, sorted by most recent first.

Required fields:

action — "list"

Example:

{
  "action": "list"
}

Response includes: array of uploads (each with cid, filename, file_size, upload_date, ipfs_url, gateway_url), plus totals for upload count and combined size.

Common Workflows

Store a document permanently

Base64-encode your file content
Use upload with the encoded content and filename
Save the returned CID -- this is the permanent address of your content

Retrieve previously stored content

Use retrieve with the CID you received from an upload or found elsewhere
Text content is returned directly; binary content is identified by type

Review your upload history

Use list to see all files you have uploaded
Each entry includes the CID and gateway URL for easy access

Important Notes

File size limit: 10MB maximum per upload
Content encoding: Files must be base64-encoded before uploading
CID formats: Both CIDv0 (Qm...) and CIDv1 (bafy...) are supported for retrieval
Persistence: Uploaded content is pinned to IPFS, meaning it will remain available as long as the pinning service maintains it
Gateway fallback: Retrieval automatically tries multiple gateways if the first one fails
Own credentials: For heavy usage, provide your own API key from Pinata, Web3.Storage, or NFT.Storage to avoid shared service limits

Frequently Asked Questions

How do I connect this tool to an external agent?

You can install the local MCP server by opening a terminal and running:

Install commands

npm install -g @agentpmt/mcp-router
agentpmt-setup

This will connect you to local agents like Claude Code, Windsurf, Grok Build, Cursor, etc.

Alternatively you can connect to the hosted version with this config block, no installation required:

Hosted MCP config

{
  "mcpServers": {
    "agentpmt": {
      "type": "streamable-http",
      "url": "https://api.agentpmt.com/mcp",
      "headers": {
        "Authorization": "Bearer <AGENTPMT_BEARER_TOKEN>",
        "x-instance-metadata": "{\"client\":\"generic-mcp\",\"platform\":\"remote\"}"
      }
    }
  }
}

View MCP Connection Instructions for more details.

How does an external agent use this tool?

After the external agent is connected to an Agent Group that can use this tool, paste this prompt into the agent:

Agent prompt

Call the AgentPMT-Tool-Search-and-Execution tool with action 'get_schema' and tool_id 68c368f066ed2f66afff5c99 ("IPFS Content Gateway"). Then call the same tool with action 'call_tool', tool_id 68c368f066ed2f66afff5c99, and the parameters needed for my request.

The agent should fetch the tool schema first, collect the required parameters for your request, and then call the tool through AgentPMT.

IPFS Content Gateway

Available ActionsEach successful request consumes credits as outlined below.

Details

Use Cases

Actions(3)

Connect Your Agent In 5 Min

Hosted Streamable HTTPS

Local STDIO Fallback

Credit-Based Access Using AgentAddress

Direct x402 Payment

Usage Instructions

IPFS Content Gateway

Actions

retrieve

upload

list

Common Workflows

Store a document permanently

Retrieve previously stored content

Review your upload history

Important Notes

Frequently Asked Questions

How do I connect this tool to an external agent?

How does an external agent use this tool?

Looking for help integrating AI into your business? Set up a free consultation.