Pay-per-file IPFS content retrieval via x402 on Base Sepolia for 0.01 USDC
What it does
This endpoint serves IPFS-pinned content behind an x402 paywall, hosted on a Pinata-based gateway (grapevine.dev-mypinata.cloud). Callers issue a GET request with a valid `x-payment` header to retrieve a specific file identified by its CID (Content Identifier). The resource returns `text/plain` content for the CID `bafkreigi6rzz44hzcdgaf2uyxnprg5nho6fsa6q25lp26k2iyicbklv5vm` at a cost of 0.01 USDC on the Base Sepolia testnet.
The payment scheme uses the "exact" method, requiring a one-time payment of 10,000 units (0.01 USDC, 6 decimals) to the address `0xbc03df2D9F44Cc552EbbFF39860f2CC4fC751d0E`. The USDC asset contract on Base Sepolia is `0x036CbD53842c5426634e7929541eC2318f3dCF7e`. The x402 challenge specifies a maximum timeout of 60 seconds for payment verification.
Documentation is essentially nonexistent — the crawled pages all return error messages, and no OpenAPI spec, README, or pricing page is available. The gateway appears to be a CID-routing service where each path under `/x402/cid/` maps to a specific pinned file. The endpoint is live and returns a well-formed x402 challenge, but without further documentation it is difficult to determine the broader capabilities of the gateway or whether other CIDs are available behind similar paywalls.
Capabilities
Use cases
- —Retrieving pay-gated IPFS-pinned text content via a single micropayment
- —Testing x402 payment flows on Base Sepolia testnet
- —Monetizing pinned IPFS files with per-request USDC payments
Fit
Best for
- —Developers experimenting with x402 payment protocol on testnets
- —Monetizing individual IPFS-pinned files behind a paywall
- —Agents that need to fetch specific gated text content by CID
Not for
- —Production use requiring mainnet payments (this is Base Sepolia testnet only)
- —Bulk or batch IPFS file retrieval at scale
- —Fetching non-text or large binary content (mimeType is text/plain)
Quick start
curl -X GET \
-H "x-payment: <valid-x402-payment-header>" \
https://grapevine.dev-mypinata.cloud/x402/cid/bafkreigi6rzz44hzcdgaf2uyxnprg5nho6fsa6q25lp26k2iyicbklv5vmEndpoint
Quality
The endpoint is live and returns a well-formed x402 challenge with clear payment parameters. However, there is zero documentation — no OpenAPI spec, no README, no docs pages, and no information about the broader service. The content type and CID are known but the actual response body is unknown. This is effectively a stub listing.
Warnings
- —No documentation available — all crawled pages return errors
- —Base Sepolia is a testnet; this endpoint is not suitable for production use
- —Unknown response body content — only mimeType (text/plain) is specified
- —No OpenAPI or schema documentation found
- —Single-CID endpoint — unclear if other CIDs are available on this gateway
Citations
- —Endpoint returns a 402 challenge with x402Version 1, exact scheme, on base-sepolia for 0.01 USDChttps://grapevine.dev-mypinata.cloud/x402/cid/bafkreigi6rzz44hzcdgaf2uyxnprg5nho6fsa6q25lp26k2iyicbklv5vm
- —Payment address is 0xbc03df2D9F44Cc552EbbFF39860f2CC4fC751d0E and USDC asset is 0x036CbD53842c5426634e7929541eC2318f3dCF7ehttps://grapevine.dev-mypinata.cloud/x402/cid/bafkreigi6rzz44hzcdgaf2uyxnprg5nho6fsa6q25lp26k2iyicbklv5vm
- —Root page returns 'No CID provided' error, all other crawled pages return 'Invalid URL' errorshttps://grapevine.dev-mypinata.cloud