Pay-per-access IPFS content via x402 on Pinata gateway (Base Sepolia testnet)
What it does
This endpoint serves IPFS-pinned content behind an x402 paywall on a Pinata dedicated gateway. The resource is identified by the CID `bafkreifqwob76i3msvcy7i5cevl7vjuode2kezzumvjxudnoarbuvwnw3y` and returns `application/json` data upon successful payment. The x402 challenge requires an exact-scheme payment of 1000 base units of USDC (0.001 USDC) on the Base Sepolia testnet, settled to the address `0x387b8264c40FDF64dCc78598246892f3CF3829B6`.
Pinata is an IPFS pinning and gateway service. This particular gateway (`peach.mypinata.cloud`) is a dedicated Pinata gateway configured with x402 payment gating. The root of the gateway returns a 403 with a message indicating the content is not publicly pinned, which is expected behavior for a paywalled gateway. No documentation, OpenAPI spec, or additional metadata is available from the gateway itself, so the exact nature of the JSON payload behind the paywall is unknown.
Because the asset contract (`0x036CbD53842c5426634e7929541eC2318f3dCF7e`) is USDC on Base Sepolia (a testnet), this endpoint is likely intended for development, testing, or demonstration purposes rather than production use. The cost per request is effectively negligible at $0.001 USDC.
Capabilities
Use cases
- —Accessing paywalled IPFS-pinned JSON content via micropayment
- —Testing x402 payment flows against a live IPFS gateway
- —Demonstrating pay-per-access decentralized content delivery
Fit
Best for
- —Developers testing x402 payment integration on Base Sepolia
- —Accessing specific paywalled IPFS content hosted on Pinata
- —Experimenting with micropayment-gated decentralized storage
Not for
- —Production payment flows (this is on Base Sepolia testnet)
- —Browsing or discovering arbitrary IPFS content
- —High-throughput bulk data retrieval
Quick start
curl -X GET \
-H "X-Payment: <x402-payment-token>" \
https://peach.mypinata.cloud/x402/cid/bafkreifqwob76i3msvcy7i5cevl7vjuode2kezzumvjxudnoarbuvwnw3yEndpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is no documentation, no OpenAPI schema, no description of the payload behind the paywall, and the crawl yielded only error pages. The testnet-only settlement and single-CID scope further limit utility. Effectively a stub listing.
Warnings
- —No documentation or OpenAPI spec available from the gateway
- —The payload behind the paywall is unknown — no description field was provided in the x402 challenge
- —Settlement is on Base Sepolia (testnet), not a production network
- —The gateway root returns 403; all other crawled paths return errors
- —Single CID endpoint — unclear if other CIDs are also paywalled on this gateway
Citations
- —The x402 challenge requires 1000 base units of USDC on Base Sepolia with asset contract 0x036CbD53842c5426634e7929541eC2318f3dCF7ehttps://peach.mypinata.cloud/x402/cid/bafkreifqwob76i3msvcy7i5cevl7vjuode2kezzumvjxudnoarbuvwnw3y
- —The gateway root returns a message indicating the content is not pinned to the owner's Pinata accounthttps://peach.mypinata.cloud
- —The response MIME type is application/json as declared in the x402 challengehttps://peach.mypinata.cloud/x402/cid/bafkreifqwob76i3msvcy7i5cevl7vjuode2kezzumvjxudnoarbuvwnw3y