x402basequality 0.25

Pay with crypto to retrieve a private IPFS file from Pinata by CID via x402

Price
0.0001 USDC / call
Protocol
x402
Verified
no

What it does

This x402-enabled endpoint lets you retrieve a private file stored on IPFS through Pinata by specifying its Content Identifier (CID). It uses Coinbase's x402 protocol, meaning you pay with cryptocurrency at request time — no Pinata account or API key required. The endpoint is hosted on Pinata's marketing-enterprise Cloudflare Workers domain.

The retrieval flow works as follows: you make a request to the endpoint URL which includes the target CID (in this case `bafkreig64zjue3vnfqejtq2lmzdhgbbsin7gc7dxdebw3exy4ysjkoq62q`). The server responds with an x402 payment challenge, and once payment is settled the private file content is returned. This is part of a broader Pinata x402 offering that also supports public and private IPFS uploads.

Documentation is sparse — the `/docs`, `/api`, `/pricing`, and `/README` paths all return 404. The full documentation is referenced at `https://docs.pinata.cloud/files/x402` but was not crawled. No OpenAPI schema or explicit pricing information was found in the probe. The x402 challenge object returned during probing was empty, which may indicate the challenge is only issued under specific conditions or that the probe did not trigger it correctly.

Capabilities

ipfs-private-file-retrievalx402-paymentcid-based-accessaccount-free-accesscrypto-payment

Use cases

  • Retrieving private IPFS-pinned files without a Pinata account by paying with crypto
  • AI agents autonomously fetching gated IPFS content via micropayments
  • Accessing private decentralized storage content in a permissionless workflow

Fit

Best for

  • Agents or applications that need on-demand access to private IPFS files without managing API keys
  • Crypto-native workflows where pay-per-request file retrieval is preferred
  • Developers prototyping IPFS retrieval without signing up for a Pinata plan

Not for

  • High-volume bulk retrieval where a Pinata subscription would be more cost-effective
  • Users who need to retrieve public IPFS content (use a public gateway instead)

Quick start

import { fetchWithPayment } from 'x402-fetch';

const res = await fetchWithPayment(
  'https://402-server.pinata-marketing-enterprise.workers.dev/v1/retrieve/private/bafkreig64zjue3vnfqejtq2lmzdhgbbsin7gc7dxdebw3exy4ysjkoq62q',
  { method: 'GET' }
);
const data = await res.blob();
console.log(data);

Endpoint

Transporthttp
Protocolx402
Pay to0xc900f41481B4F7C612AF9Ce3B1d16A7A1B6bd96E
CurrencyUSD COIN

Quality

0.25/ 1.00

No OpenAPI schema, no pricing info, empty x402 challenge, and all documentation paths return 404. The endpoint purpose is clear from the landing page and URL structure, but nearly everything else must be inferred. Effectively a stub listing.

Warnings

  • x402 challenge object was empty during probing — payment flow could not be verified
  • No OpenAPI or schema documentation available; /docs, /api, /pricing, /README all return 404
  • Pricing and payment amounts are unknown — no pricing information found
  • Full docs referenced at docs.pinata.cloud/files/x402 were not crawled and could not be verified

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-18 18:34:50Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access