Pay-per-fetch IPFS content gateway via x402 on Base Sepolia (0.002005 USDC)
What it does
This endpoint serves IPFS-pinned content behind an x402 paywall, hosted on Pinata's Grapevine dev gateway. When a client sends a GET request to the resource URL containing a specific IPFS CID (bafkreihewrz2zq6ifo34bsivan3p5ufp3lzajri2jmsyzqdupzgirkgo2m), the server returns HTTP 402 with a payment challenge. The client must supply a valid `x-payment` header containing an on-chain payment proof for 0.002005 USDC on the Base Sepolia testnet to receive the content.
The payment scheme is "exact", meaning the caller pays a fixed amount (2005 units in USDC's smallest denomination) to the specified payTo address. The content is delivered as `application/octet-stream`, indicating raw binary data — likely an IPFS-pinned file. The USDC asset contract used is 0x036CbD53842c5426634e7929541eC2318f3dCF7e on Base Sepolia, and the x402 protocol version is 1.
Because this runs on Base Sepolia (a testnet), it is suitable for development, testing, and prototyping pay-per-access IPFS content delivery rather than production use. No documentation, OpenAPI spec, or additional API routes were found on the gateway; the crawled pages all return error messages indicating the gateway expects a CID in the URL path.
Capabilities
Use cases
- —Prototyping pay-per-access IPFS content delivery on a testnet
- —Testing x402 payment flows against a live 402 challenge endpoint
- —Building agents that purchase and retrieve IPFS-pinned files programmatically
- —Demonstrating micropayment-gated decentralized storage access
Fit
Best for
- —Developers testing x402 payment integrations on Base Sepolia
- —Agent builders experimenting with pay-per-fetch content retrieval
- —Prototyping monetized IPFS content distribution
Not for
- —Production content delivery (this is a testnet endpoint)
- —Serving large-scale or high-throughput file downloads
- —Users who need free or unauthenticated IPFS access
Quick start
curl -X GET \
-H "x-payment: <valid-x402-payment-proof>" \
https://grapevine.dev-mypinata.cloud/x402/cid/bafkreihewrz2zq6ifo34bsivan3p5ufp3lzajri2jmsyzqdupzgirkgo2mEndpoint
Quality
The endpoint is live and returns a well-formed x402 challenge, but there is no documentation, no OpenAPI schema, no examples, and no information beyond what the 402 challenge itself provides. The crawled pages all return errors. This is effectively a stub listing built entirely from the payment challenge metadata.
Warnings
- —No documentation or OpenAPI spec found on the gateway
- —All crawled pages return error responses; gateway only serves CID-based paths
- —Runs on Base Sepolia testnet — not suitable for production use
- —Content type is application/octet-stream with no description of what the file actually contains
- —payTo address and asset contract are unverified beyond the challenge payload
Citations
- —Endpoint returns HTTP 402 with x402 version 1 challenge requiring 0.002005 USDC on Base Sepoliahttps://grapevine.dev-mypinata.cloud/x402/cid/bafkreihewrz2zq6ifo34bsivan3p5ufp3lzajri2jmsyzqdupzgirkgo2m
- —USDC asset contract is 0x036CbD53842c5426634e7929541eC2318f3dCF7e on Base Sepoliahttps://grapevine.dev-mypinata.cloud/x402/cid/bafkreihewrz2zq6ifo34bsivan3p5ufp3lzajri2jmsyzqdupzgirkgo2m
- —Content MIME type is application/octet-streamhttps://grapevine.dev-mypinata.cloud/x402/cid/bafkreihewrz2zq6ifo34bsivan3p5ufp3lzajri2jmsyzqdupzgirkgo2m
- —Root gateway returns 'No CID provided' errorhttps://grapevine.dev-mypinata.cloud