Pay-per-access JPEG image served via x402 on Pinata/IPFS for 0.10 USDC (Base Sepolia).
What it does
This endpoint serves a specific IPFS-pinned JPEG image (CID: bafybeiczoniae6yteqfxvhvqbhxd4joertnaletcl5fc7z6xwfaukisyzu) behind an x402 paywall. The content is hosted on a Pinata IPFS gateway (grapevine.dev-mypinata.cloud) and requires a one-time payment of 0.10 USDC on the Base Sepolia testnet to access. The x402 protocol version 1 challenge uses the "exact" payment scheme, meaning the caller must submit a valid `x-payment` header with the correct payment proof to retrieve the image.
The endpoint responds to GET requests and returns content with MIME type `image/jpeg`. Payment is directed to wallet address 0x640b9f244C15e950302180341cA02254ffD5EbD0 using the USDC token contract at 0x036CbD53842c5426634e7929541eC2318f3dCF7e on Base Sepolia. The maximum timeout for payment verification is 60 seconds.
Because this operates on Base Sepolia (a testnet), the USDC used has no real monetary value. This makes the endpoint suitable for testing x402 payment flows, prototyping pay-per-content applications, or experimenting with IPFS-gated content delivery. No documentation, OpenAPI schema, or additional API surface was found on the host — the crawled pages all return error messages indicating the gateway expects a valid CID path.
Capabilities
Use cases
- —Testing x402 payment protocol integrations against a live testnet endpoint
- —Prototyping pay-per-view image delivery over IPFS
- —Demonstrating crypto-gated content access for decentralized applications
- —Agent-driven content purchasing workflows on Base Sepolia
Fit
Best for
- —Developers testing x402 payment flows on a testnet
- —Prototyping pay-per-content IPFS applications
- —Learning how x402 challenges and payment headers work
Not for
- —Production content delivery (uses testnet USDC with no real value)
- —Serving dynamic or non-image content
- —High-throughput or low-latency media streaming
Quick start
curl -X GET \
https://grapevine.dev-mypinata.cloud/x402/cid/bafybeiczoniae6yteqfxvhvqbhxd4joertnaletcl5fc7z6xwfaukisyzu \
-H "x-payment: <valid-x402-payment-proof>"Endpoint
Quality
The endpoint is live and returns a well-formed x402 challenge with clear pricing and MIME type information. However, there is no documentation, no OpenAPI schema, no examples, and the host returns errors on all non-CID paths. The endpoint is on a testnet, limiting practical utility. Most fields had to be inferred from the 402 challenge alone.
Warnings
- —Operates on Base Sepolia testnet — USDC has no real monetary value
- —No documentation or OpenAPI schema found on the host
- —All non-CID paths on the gateway return error messages
- —Single static asset — no broader API surface detected
- —Payment proof generation requires an x402-compatible client library
Citations
- —The endpoint returns a 402 challenge with x402Version 1, exact scheme, 0.10 USDC on Base Sepolia, and MIME type image/jpeghttps://grapevine.dev-mypinata.cloud/x402/cid/bafybeiczoniae6yteqfxvhvqbhxd4joertnaletcl5fc7z6xwfaukisyzu
- —maxAmountRequired is 100000 base units (0.10 USDC with 6 decimals) paid to 0x640b9f244C15e950302180341cA02254ffD5EbD0https://grapevine.dev-mypinata.cloud/x402/cid/bafybeiczoniae6yteqfxvhvqbhxd4joertnaletcl5fc7z6xwfaukisyzu
- —Root domain returns 'No CID provided' error, indicating it is a CID-based gatewayhttps://grapevine.dev-mypinata.cloud