Pay-per-fetch IPFS content via x402 on Base Sepolia (USDC)
What it does
This endpoint serves IPFS-pinned content behind an x402 paywall hosted on Pinata's Grapevine dev gateway. Callers issue a GET request with a valid `x-payment` header containing an x402 payment proof to retrieve the content identified by the IPFS CID `bafkreie5aeo72m5xmgeeqtlzhqz4vc5qii2tgni6lqtj7xwbpcnaayczru`. The cost is 0.002006 USDC on the Base Sepolia testnet, paid to address `0x6e62FF0591d4D8a0E5A1C274AbCFd2D716F1035E`.
The gateway follows the x402 protocol (version 1, "exact" scheme). Without a valid payment header the endpoint returns HTTP 402 with a JSON challenge describing the accepted payment parameters, asset contract, network, and timeout. Once payment is verified, the resource is returned with MIME type `application/octet-stream`, meaning the underlying content is delivered as a raw binary blob. The maximum payment timeout is 60 seconds.
Because this runs on Base Sepolia (a testnet), it is suitable for development, testing, and experimentation with x402-gated IPFS content delivery rather than production commerce. No OpenAPI spec, documentation pages, or additional API surface were found on the host—every non-CID path returns an error. The endpoint itself is live and responds correctly to the x402 handshake.
Capabilities
Use cases
- —Testing x402 payment flows against IPFS-hosted content on a testnet
- —Prototyping pay-per-download models for decentralized file storage
- —Agent-driven retrieval of paywall-gated binary blobs via IPFS CIDs
- —Demonstrating micropayment-gated content delivery pipelines
Fit
Best for
- —Developers experimenting with x402 protocol integrations
- —Testing micropayment-gated IPFS content retrieval on Base Sepolia
- —Building agent workflows that pay for and fetch decentralized content
Not for
- —Production commerce (this is a testnet endpoint)
- —Serving large-scale or high-throughput file downloads
- —Browsing or discovering available IPFS content (single CID only)
Quick start
curl -X GET \
-H "x-payment: <x402-payment-proof>" \
https://grapevine.dev-mypinata.cloud/x402/cid/bafkreie5aeo72m5xmgeeqtlzhqz4vc5qii2tgni6lqtj7xwbpcnaayczruExample
Response
{
"error": "Provide a valid x-payment header to access this content",
"accepts": [
{
"asset": "0x036CbD53842c5426634e7929541eC2318f3dCF7e",
"extra": {
"name": "USDC",
"version": "2"
},
"payTo": "0x6e62FF0591d4D8a0E5A1C274AbCFd2D716F1035E",
"scheme": "exact",
"network": "base-sepolia",
"mimeType": "application/octet-stream",
"resource": "https://grapevine.dev-mypinata.cloud/x402/cid/bafkreie5aeo72m5xmgeeqtlzhqz4vc5qii2tgni6lqtj7xwbpcnaayczru",
"description": "0.002006 USDC on base-sepolia",
"maxAmountRequired": "2006",
"maxTimeoutSeconds": 60
}
],
"x402Version": 1
}Endpoint
Quality
The x402 challenge is live and well-formed, confirming the endpoint works. However, there is no documentation, no OpenAPI spec, no description of the underlying content, and the crawl returned errors on every auxiliary path. All details are inferred solely from the 402 challenge payload.
Warnings
- —Testnet only (Base Sepolia) — not suitable for real-value transactions
- —No documentation or OpenAPI spec found on the host
- —Underlying content behind the CID is unknown (application/octet-stream with no description)
- —All non-CID paths on the gateway return errors; no discoverability
Citations
- —Endpoint returns HTTP 402 with x402 version 1 challenge on GEThttps://grapevine.dev-mypinata.cloud/x402/cid/bafkreie5aeo72m5xmgeeqtlzhqz4vc5qii2tgni6lqtj7xwbpcnaayczru
- —Payment is 0.002006 USDC (maxAmountRequired 2006) on base-sepolia networkhttps://grapevine.dev-mypinata.cloud/x402/cid/bafkreie5aeo72m5xmgeeqtlzhqz4vc5qii2tgni6lqtj7xwbpcnaayczru
- —Content MIME type is application/octet-streamhttps://grapevine.dev-mypinata.cloud/x402/cid/bafkreie5aeo72m5xmgeeqtlzhqz4vc5qii2tgni6lqtj7xwbpcnaayczru
- —Pay-to address is 0x6e62FF0591d4D8a0E5A1C274AbCFd2D716F1035Ehttps://grapevine.dev-mypinata.cloud/x402/cid/bafkreie5aeo72m5xmgeeqtlzhqz4vc5qii2tgni6lqtj7xwbpcnaayczru