Pay-per-access IPFS image retrieval via x402 on Base Sepolia (1 USDC per fetch)
What it does
This endpoint serves an IPFS-pinned image (PNG) identified by its CID (bafkreiefb2zp43pcvlbcorkleopnxlyezr6jcyf3i4kxzsmjiqw3hysvjq) through a pay-per-request x402 gateway hosted on Pinata's dev infrastructure (grapevine.dev-mypinata.cloud). To retrieve the content, a caller must include a valid `x-payment` header containing an x402 payment proof. The payment scheme is "exact," requiring 1 USDC (1,000,000 base units) on the Base Sepolia testnet, sent to the specified payTo address.
The gateway appears to be a Pinata-based IPFS gateway augmented with x402 payment gating. Each request is a simple HTTP GET; the response MIME type is `image/png`. The x402 challenge is version 1 and allows a maximum timeout of 60 seconds for payment settlement. The asset used for payment is the USDC contract on Base Sepolia (0x036CbD53842c5426634e7929541eC2318f3dCF7e).
Documentation is effectively absent — all non-CID paths on the origin return error messages. There is no OpenAPI spec, no agents.txt, and no robots.txt. The endpoint is live and returns a well-formed 402 challenge, but the lack of surrounding documentation and the use of a testnet suggest this is a development or demonstration deployment rather than a production service.
Capabilities
Use cases
- —Paying to retrieve a specific IPFS-pinned PNG image via x402
- —Demonstrating x402 payment flows on Base Sepolia testnet
- —Agent-driven purchase of gated digital content stored on IPFS
Fit
Best for
- —Developers testing x402 payment integrations on a testnet
- —Agents that need to programmatically purchase IPFS-hosted images
- —Prototyping pay-per-access content delivery over IPFS
Not for
- —Production workloads requiring mainnet settlement
- —Bulk or batch retrieval of many IPFS objects (single CID endpoint)
- —Users needing free or unauthenticated IPFS access
Quick start
curl -X GET \
-H "x-payment: <x402_payment_proof>" \
https://grapevine.dev-mypinata.cloud/x402/cid/bafkreiefb2zp43pcvlbcorkleopnxlyezr6jcyf3i4kxzsmjiqw3hysvjq \
--output image.pngEndpoint
Quality
The endpoint is live and returns a valid x402 challenge with clear payment parameters and MIME type. However, there is zero documentation, no OpenAPI spec, no examples, and the deployment is on a testnet dev subdomain, suggesting it is a demo or test instance rather than a stable production service.
Warnings
- —No documentation found — all non-CID paths return errors
- —Uses Base Sepolia testnet, not mainnet; USDC is testnet USDC
- —Appears to be a development/demo deployment (dev-mypinata.cloud subdomain)
- —Single hardcoded CID — not a general-purpose gateway endpoint
- —No OpenAPI schema or agents.txt available
Citations
- —The endpoint returns a 402 challenge requiring 1 USDC on base-sepolia with scheme 'exact'https://grapevine.dev-mypinata.cloud/x402/cid/bafkreiefb2zp43pcvlbcorkleopnxlyezr6jcyf3i4kxzsmjiqw3hysvjq
- —The response MIME type is image/pnghttps://grapevine.dev-mypinata.cloud/x402/cid/bafkreiefb2zp43pcvlbcorkleopnxlyezr6jcyf3i4kxzsmjiqw3hysvjq
- —Payment asset is USDC at contract 0x036CbD53842c5426634e7929541eC2318f3dCF7e on Base Sepoliahttps://grapevine.dev-mypinata.cloud/x402/cid/bafkreiefb2zp43pcvlbcorkleopnxlyezr6jcyf3i4kxzsmjiqw3hysvjq
- —Root origin returns 'No CID provided' error with status 400https://grapevine.dev-mypinata.cloud