Pay-per-access IPFS content retrieval via x402 on Base Sepolia (0.5 USDC per fetch).
What it does
This endpoint serves IPFS-pinned content behind an x402 paywall hosted on a Pinata-based gateway (grapevine.dev-mypinata.cloud). When a GET request is made to the resource URL containing a specific CID (bafkreih55jnxbawbrgrkr4fmjducyp3ma27gcmhhdelhszatgcgdfxrpzm), the server returns an HTTP 402 challenge requiring payment of 0.5 USDC on the Base Sepolia testnet. Once a valid x-payment header is provided, the endpoint delivers the content as text/plain.
The x402 challenge specifies the "exact" payment scheme, accepting USDC (contract 0x036CbD53842c5426634e7929541eC2318f3dCF7e) with a maximum timeout of 60 seconds. Payment is directed to address 0x99935f281d3ED1E804bF1413b76E0B03e1fed4F9. The gateway appears to be built on Pinata's IPFS infrastructure, acting as a pay-gated content delivery layer for pinned files.
Documentation is effectively absent — all non-CID paths return generic error messages. There is no OpenAPI spec, no robots.txt, and no agents.txt. The endpoint is live and responds correctly with a well-formed x402 challenge, but the lack of surrounding documentation limits confidence in the broader service capabilities beyond this single CID.
Capabilities
Use cases
- —Monetizing IPFS-pinned text content with per-access micropayments
- —Gating access to specific CIDs behind cryptocurrency payments
- —Agent-driven retrieval of paid decentralized content
Fit
Best for
- —Developers experimenting with x402 payment flows on testnets
- —Monetizing individual IPFS-pinned files without a traditional paywall backend
- —AI agents that need to programmatically purchase and retrieve gated content
Not for
- —Production use — this runs on Base Sepolia testnet, not mainnet
- —Bulk or high-throughput IPFS content retrieval (single CID endpoint, 60s timeout)
- —Users needing documentation or API discovery (none available)
Quick start
curl -X GET \
https://grapevine.dev-mypinata.cloud/x402/cid/bafkreih55jnxbawbrgrkr4fmjducyp3ma27gcmhhdelhszatgcgdfxrpzm \
-H 'x-payment: <valid-x402-payment-header>'Endpoint
Quality
The endpoint is live and returns a well-formed x402 challenge, but there is zero documentation, no OpenAPI spec, no examples, and no information beyond what the 402 challenge itself provides. The service runs on a testnet, and the crawl yielded only error pages. This is effectively a stub listing.
Warnings
- —No documentation found — all crawled paths return error messages
- —Runs on Base Sepolia testnet; not suitable for production payments
- —Only a single CID is referenced; unclear if the gateway supports arbitrary CIDs behind paywalls
- —No OpenAPI spec, agents.txt, or robots.txt available
- —Response content is unknown — mime type is text/plain but actual payload cannot be verified without payment
Citations
- —Endpoint returns HTTP 402 with a valid x402 challenge requiring 0.5 USDC on Base Sepoliahttps://grapevine.dev-mypinata.cloud/x402/cid/bafkreih55jnxbawbrgrkr4fmjducyp3ma27gcmhhdelhszatgcgdfxrpzm
- —USDC asset contract is 0x036CbD53842c5426634e7929541eC2318f3dCF7e on Base Sepoliahttps://grapevine.dev-mypinata.cloud/x402/cid/bafkreih55jnxbawbrgrkr4fmjducyp3ma27gcmhhdelhszatgcgdfxrpzm
- —Payment is directed to 0x99935f281d3ED1E804bF1413b76E0B03e1fed4F9https://grapevine.dev-mypinata.cloud/x402/cid/bafkreih55jnxbawbrgrkr4fmjducyp3ma27gcmhhdelhszatgcgdfxrpzm
- —Root and other paths return 'Invalid URL' or 'No CID provided' errorshttps://grapevine.dev-mypinata.cloud