Pay-per-access IPFS content gate: fetch a CID for 0.01 USDC on Base Sepolia via x402.
What it does
This endpoint serves IPFS-pinned content behind an x402 paywall hosted on a Pinata gateway (grapevine.dev-mypinata.cloud). When a GET request is made without payment, the server returns an HTTP 402 challenge requiring 0.01 USDC on the Base Sepolia testnet. Once a valid `x-payment` header is supplied with the correct payment proof, the endpoint delivers the content identified by the CID `bafkreicyv2z2vmpa5wp5vhi5xadnkwefkzj35k7i4gll4kdpd7gkgbapse` as `application/octet-stream`.
The x402 challenge specifies the "exact" payment scheme, accepting payment to address `0xbc03df2D9F44Cc552EbbFF39860f2CC4fC751d0E` using the USDC token contract at `0x036CbD53842c5426634e7929541eC2318f3dCF7e` on Base Sepolia. The maximum timeout for payment verification is 60 seconds. This is a testnet deployment, so the USDC used has no real monetary value — it is suitable for development, testing, and demonstration of x402 pay-per-content flows.
Documentation is essentially absent: the crawled pages all return error messages ("No CID provided" or "Invalid URL"), and there is no OpenAPI spec, agents.txt, or README available. All information in this listing is derived from the x402 challenge response itself. The underlying infrastructure appears to be a Pinata IPFS gateway with an x402 middleware layer.
Capabilities
Use cases
- —Testing x402 payment flows against a live testnet endpoint
- —Prototyping pay-per-download decentralized content delivery
- —Demonstrating IPFS content gating with USDC micropayments
- —Building agents that can autonomously purchase and retrieve IPFS-pinned files
Fit
Best for
- —Developers experimenting with x402 protocol integrations
- —Testing micropayment-gated content retrieval on Base Sepolia
- —Prototyping agent-to-service payment workflows with IPFS content
Not for
- —Production use requiring mainnet payments and real value transfer
- —Retrieving content without cryptocurrency payment capability
- —High-throughput bulk IPFS content fetching
Quick start
curl -X GET \
https://grapevine.dev-mypinata.cloud/x402/cid/bafkreicyv2z2vmpa5wp5vhi5xadnkwefkzj35k7i4gll4kdpd7gkgbapse \
-H "x-payment: <your-x402-payment-proof>"Endpoint
Quality
The endpoint is live and returns a well-formed x402 challenge, but there is zero documentation, no OpenAPI spec, no examples, and no information beyond what the 402 response itself provides. The testnet-only nature and single-CID scope further limit utility. This is effectively a stub listing.
Warnings
- —No documentation found — all crawled pages return errors
- —Testnet only (Base Sepolia) — USDC has no real monetary value
- —Single CID endpoint — unclear if other CIDs are available on this gateway
- —No OpenAPI or schema beyond the x402 challenge itself
- —Provider landing page returns HTTP 400
Citations
- —Endpoint returns HTTP 402 with x402 version 1 challenge requiring 0.01 USDC on Base Sepoliahttps://grapevine.dev-mypinata.cloud/x402/cid/bafkreicyv2z2vmpa5wp5vhi5xadnkwefkzj35k7i4gll4kdpd7gkgbapse
- —Payment is to address 0xbc03df2D9F44Cc552EbbFF39860f2CC4fC751d0E using USDC contract 0x036CbD53842c5426634e7929541eC2318f3dCF7ehttps://grapevine.dev-mypinata.cloud/x402/cid/bafkreicyv2z2vmpa5wp5vhi5xadnkwefkzj35k7i4gll4kdpd7gkgbapse
- —Content MIME type is application/octet-stream with max timeout of 60 secondshttps://grapevine.dev-mypinata.cloud/x402/cid/bafkreicyv2z2vmpa5wp5vhi5xadnkwefkzj35k7i4gll4kdpd7gkgbapse
- —Root page returns 'No CID provided' errorhttps://grapevine.dev-mypinata.cloud