Pay-per-access IPFS content retrieval via x402 on Pinata gateway (base-sepolia)
What it does
This endpoint provides x402-gated access to a specific IPFS content identifier (CID) hosted on a Pinata IPFS gateway (grapevine.dev-mypinata.cloud). The CID in the URL (bafkreibp4rn4bi4lyupel36x7dnmqnp7kuk6m2k2ehhprvyfcerfuvw4wa) points to a particular piece of content stored on IPFS, and the x402 payment layer requires 0.5 USDC on the Base Sepolia testnet to unlock access.
Based on the probe, the endpoint returned HTTP 429 (Too Many Requests) rather than the expected 402 Payment Required challenge on both GET and POST methods. The root domain returns generic error messages ("No CID provided" or "Invalid URL") for all crawled paths, indicating this is a minimal Pinata gateway wrapper with no public documentation, API spec, or pricing page. There is no OpenAPI schema, no agents.txt, and no robots.txt available.
Given the sparse information, this appears to be a testnet-only x402 endpoint for gated IPFS content delivery via Pinata's infrastructure. The 429 response instead of 402 may indicate rate limiting, misconfiguration, or that the endpoint is temporarily throttled. Without documentation or a working 402 challenge, the exact payload format and response structure cannot be confirmed.
Capabilities
Use cases
- —Monetizing individual IPFS-hosted files behind a micropayment wall
- —Gating access to specific decentralized content for authorized payers
- —Testing x402 payment flows on Base Sepolia testnet with IPFS content
Fit
Best for
- —Developers experimenting with x402 payment-gated IPFS content on testnet
- —Monetizing specific IPFS-pinned files via micropayments
- —Prototyping pay-per-download decentralized storage access
Not for
- —Production mainnet usage (this is on base-sepolia testnet)
- —Bulk or high-throughput IPFS content retrieval (no documentation on rate limits, and 429 observed)
Quick start
curl -X GET https://grapevine.dev-mypinata.cloud/x402/cid/bafkreibp4rn4bi4lyupel36x7dnmqnp7kuk6m2k2ehhprvyfcerfuvw4wa
# Expected: 402 with x402 payment challenge (0.5 USDC on base-sepolia)
# Note: Probe returned 429; endpoint may be rate-limited or misconfiguredEndpoint
Quality
The endpoint did not return the expected 402 challenge (returned 429 instead), there is no documentation, no OpenAPI schema, no examples, and all crawled pages return error messages. Only the Bazaar listing title provides pricing info (0.5 USDC on base-sepolia). This is effectively a stub with uncertain liveness.
Warnings
- —Endpoint returned 429 (Too Many Requests) instead of expected 402 Payment Required on both GET and POST — may be rate-limited, misconfigured, or temporarily unavailable
- —No documentation, OpenAPI schema, or API description available from the provider
- —Testnet only (Base Sepolia) — not suitable for production use
- —All crawled paths on the domain return generic error messages; no public docs exist
- —Cannot confirm the content type or size behind the gated CID
Citations
- —Endpoint returned HTTP 429 on both POST and GET attemptshttps://grapevine.dev-mypinata.cloud/x402/cid/bafkreibp4rn4bi4lyupel36x7dnmqnp7kuk6m2k2ehhprvyfcerfuvw4wa
- —Root domain returns 'No CID provided' errorhttps://grapevine.dev-mypinata.cloud
- —All documentation paths return 'Invalid URL' errorshttps://grapevine.dev-mypinata.cloud/docs