Pay-per-access IPFS content retrieval via x402 on Base Sepolia (0.1 USDC)
What it does
This endpoint serves IPFS content gated behind an x402 payment wall, hosted on a Pinata-based gateway (grapevine.dev-mypinata.cloud). The specific resource is identified by the CID `bafkreidwyumcs54onjc65mmfoxam6npbugu2boyxuossl3vaawunrkluze`. According to the Bazaar listing, access costs 0.1 USDC on the Base Sepolia testnet.
The endpoint appears to be built on Pinata's IPFS pinning and gateway infrastructure, with an x402 payment layer added to gate content retrieval. The URL structure (`/x402/cid/{cid}`) suggests a pattern where any pinned CID could be served behind a paywall. However, during probing the endpoint returned HTTP 429 (Too Many Requests) rather than the expected 402 Payment Required challenge, which may indicate rate limiting or a temporary issue.
Documentation is essentially nonexistent — all crawled paths returned error messages ("Invalid URL" or "No CID provided"). There is no OpenAPI schema, no API documentation, and no additional context beyond the Bazaar listing title and description. The endpoint's liveness and correct behavior cannot be confirmed from the available probe data.
Capabilities
Use cases
- —Monetizing IPFS-hosted content by gating access behind micropayments
- —Testing x402 payment flows on Base Sepolia testnet
- —Serving pay-per-view decentralized content to agents or users
Fit
Best for
- —Developers experimenting with x402 payment protocol on testnet
- —Gating access to specific IPFS content behind USDC micropayments
- —Prototyping paid decentralized content delivery
Not for
- —Production use (Base Sepolia is a testnet)
- —Retrieving free or publicly available IPFS content
- —High-throughput content delivery (rate limiting observed)
Quick start
curl -X GET https://grapevine.dev-mypinata.cloud/x402/cid/bafkreidwyumcs54onjc65mmfoxam6npbugu2boyxuossl3vaawunrkluze
# Expect a 402 response with payment challenge headers;
# submit x402 payment (0.1 USDC on Base Sepolia) to access content.Endpoint
Quality
The endpoint returned 429 instead of the expected 402 challenge on both GET and POST, so liveness cannot be confirmed. No documentation, no schema, no examples, and no crawlable content exist. The listing is effectively a stub with only a title and price from the Bazaar record.
Warnings
- —Endpoint returned HTTP 429 (Too Many Requests) instead of 402 on both GET and POST — liveness unconfirmed
- —No documentation, OpenAPI schema, or API description available
- —Base Sepolia is a testnet; this is not a production payment endpoint
- —All crawled paths returned error messages; the provider site has no discoverable docs
- —Cannot verify the content behind the CID or its format/size
Citations
- —The endpoint is listed as costing 0.1 USDC on Base Sepoliahttps://grapevine.dev-mypinata.cloud/x402/cid/bafkreidwyumcs54onjc65mmfoxam6npbugu2boyxuossl3vaawunrkluze
- —Root page returns 'No CID provided' errorhttps://grapevine.dev-mypinata.cloud
- —Probe returned HTTP 429 on both POST and GET attemptshttps://grapevine.dev-mypinata.cloud/x402/cid/bafkreidwyumcs54onjc65mmfoxam6npbugu2boyxuossl3vaawunrkluze