Pay 0.1 USDC (Base Sepolia) to retrieve IPFS content via a Pinata-powered x402 gateway.
What it does
This x402-enabled endpoint serves IPFS content gated behind a micropayment. It is hosted on a Pinata development gateway (grapevine.dev-mypinata.cloud) and returns content identified by its CID (Content Identifier) upon receiving a valid x-payment header. The specific resource at CID `bafkreigmbakfwzhh747zrgmiaztruzfkxbwm4u4id7kblekvdrbcsdunmm` costs 0.1 USDC on the Base Sepolia testnet.
The endpoint uses the x402 protocol (version 1) with an "exact" payment scheme. Callers issue a GET request and must include a valid `x-payment` header containing a payment proof. The content is served as `text/plain` MIME type. The payment is directed to address `0x99935f281d3ED1E804bF1413b76E0B03e1fed4F9` using the USDC token contract at `0x036CbD53842c5426634e7929541eC2318f3dCF7e` on Base Sepolia. The maximum timeout for payment verification is 60 seconds.
Note that this endpoint operates on the Base Sepolia testnet, meaning it uses test USDC rather than real funds. The crawled site provides no documentation, API reference, or additional context beyond the x402 challenge itself. The gateway appears to be a development/staging instance of a Pinata-based IPFS gateway with x402 payment gating.
Capabilities
Use cases
- —Retrieving paywalled IPFS content by CID with a USDC micropayment
- —Testing x402 payment flows against a live testnet endpoint
- —Gating access to pinned IPFS files behind on-chain payments
- —Prototyping paid content distribution on decentralized storage
Fit
Best for
- —Developers testing x402 payment integrations on Base Sepolia
- —Agents that need to fetch paywalled IPFS-hosted text content
- —Prototyping micropayment-gated content delivery pipelines
Not for
- —Production use with real funds (this is a testnet endpoint)
- —Retrieving large binary files or non-text content (MIME type is text/plain)
- —Users without Base Sepolia testnet USDC
Quick start
curl -X GET \
-H "x-payment: <valid-x402-payment-header>" \
https://grapevine.dev-mypinata.cloud/x402/cid/bafkreigmbakfwzhh747zrgmiaztruzfkxbwm4u4id7kblekvdrbcsdunmmEndpoint
Quality
The endpoint is live and returns a well-formed x402 challenge, but there is zero documentation, no OpenAPI schema, no examples, and no information about the provider or the content behind the CID. The crawled pages all return errors. This is effectively a testnet stub with minimal context.
Warnings
- —Testnet only: operates on Base Sepolia with test USDC, not suitable for production
- —No documentation or API reference available from the provider
- —All crawled pages return errors; the gateway appears to be a bare development instance
- —Content behind the CID is unknown; MIME type is text/plain but actual payload is unverified
- —Provider identity unclear beyond being a Pinata dev gateway
Citations
- —Endpoint returns a 402 challenge with x402 version 1, exact scheme, 0.1 USDC on Base Sepoliahttps://grapevine.dev-mypinata.cloud/x402/cid/bafkreigmbakfwzhh747zrgmiaztruzfkxbwm4u4id7kblekvdrbcsdunmm
- —Payment is directed to address 0x99935f281d3ED1E804bF1413b76E0B03e1fed4F9 using USDC contract 0x036CbD53842c5426634e7929541eC2318f3dCF7ehttps://grapevine.dev-mypinata.cloud/x402/cid/bafkreigmbakfwzhh747zrgmiaztruzfkxbwm4u4id7kblekvdrbcsdunmm
- —Content MIME type is text/plain with a 60-second payment timeouthttps://grapevine.dev-mypinata.cloud/x402/cid/bafkreigmbakfwzhh747zrgmiaztruzfkxbwm4u4id7kblekvdrbcsdunmm