Pay 0.1 USDC (Base Sepolia) to retrieve IPFS content by CID via x402 paywall.
What it does
This x402-enabled endpoint on grapevine.dev-mypinata.cloud serves IPFS content gated behind a micropayment. When a client requests a specific CID (Content Identifier), the server returns an x402 payment challenge requiring 0.1 USDC on the Base Sepolia testnet. Once a valid `x-payment` header is provided with the correct payment proof, the server delivers the content as `application/octet-stream`.
The endpoint follows the x402 protocol (version 1) using the "exact" payment scheme. Payments are directed to the address `0xbc03df2D9F44Cc552EbbFF39860f2CC4fC751d0E` using the USDC token contract at `0x036CbD53842c5426634e7929541eC2318f3dCF7e` on Base Sepolia. The maximum timeout for payment verification is 60 seconds. The URL pattern is `/x402/cid/{CID}`, where the CID is a standard IPFS content identifier.
Documentation is essentially nonexistent — all non-CID paths return error messages, and no OpenAPI spec, README, or docs page was found. The service appears to be a Pinata-based IPFS gateway with an x402 payment layer. Because this uses the Base Sepolia testnet, it is likely a development or demonstration deployment rather than a production service.
Capabilities
Use cases
- —Retrieving IPFS-pinned content behind a micropayment wall
- —Testing x402 payment flows on Base Sepolia testnet
- —Monetizing individual files stored on IPFS
- —Agent-driven purchase of content-addressed data
Fit
Best for
- —Developers testing x402 protocol integrations on a testnet
- —Agents that need to programmatically purchase IPFS-hosted content
- —Experimenting with micropayment-gated file delivery
Not for
- —Production use requiring mainnet payments (this is Base Sepolia testnet)
- —Browsing or discovering available content (no listing/search capability)
- —Large-scale bulk file retrieval (single-CID, single-payment model)
Quick start
curl -i https://grapevine.dev-mypinata.cloud/x402/cid/bafkreihas25vf6s5g2bezjjgm452g54xylg2lowmnt7ppmsqpft7hiqham
# Returns 402 with x402 challenge JSON.
# Supply a valid x-payment header to receive the content.Example
Response
{
"error": "Provide a valid x-payment header to access this content",
"accepts": [
{
"asset": "0x036CbD53842c5426634e7929541eC2318f3dCF7e",
"extra": {
"name": "USDC",
"version": "2"
},
"payTo": "0xbc03df2D9F44Cc552EbbFF39860f2CC4fC751d0E",
"scheme": "exact",
"network": "base-sepolia",
"mimeType": "application/octet-stream",
"resource": "https://grapevine.dev-mypinata.cloud/x402/cid/bafkreihas25vf6s5g2bezjjgm452g54xylg2lowmnt7ppmsqpft7hiqham",
"description": "0.1 USDC on base-sepolia",
"maxAmountRequired": "100000",
"maxTimeoutSeconds": 60
}
],
"x402Version": 1
}Endpoint
Quality
The x402 challenge provides basic payment and protocol details, but there is no documentation, no OpenAPI spec, no usage examples, and all crawled pages returned errors. The service appears to be a testnet demo with minimal discoverability.
Warnings
- —No documentation or OpenAPI spec found; all non-CID paths return errors.
- —Uses Base Sepolia testnet — likely a development/demo deployment, not production.
- —Content behind the paywall is opaque (application/octet-stream); no metadata about what the CID contains.
- —No robots.txt or agents.txt present.
Citations
- —x402 challenge requires 0.1 USDC (100000 units) on Base Sepolia with exact schemehttps://grapevine.dev-mypinata.cloud/x402/cid/bafkreihas25vf6s5g2bezjjgm452g54xylg2lowmnt7ppmsqpft7hiqham
- —Payment is directed to address 0xbc03df2D9F44Cc552EbbFF39860f2CC4fC751d0E using USDC contract 0x036CbD53842c5426634e7929541eC2318f3dCF7ehttps://grapevine.dev-mypinata.cloud/x402/cid/bafkreihas25vf6s5g2bezjjgm452g54xylg2lowmnt7ppmsqpft7hiqham
- —Content is served as application/octet-stream with a 60-second payment timeouthttps://grapevine.dev-mypinata.cloud/x402/cid/bafkreihas25vf6s5g2bezjjgm452g54xylg2lowmnt7ppmsqpft7hiqham
- —Root and other paths return 'No CID provided' or 'Invalid URL' errorshttps://grapevine.dev-mypinata.cloud