Pay-per-access video file (MP4) served via x402 on Pinata/IPFS for 0.01 USDC on Base Sepolia.
What it does
This x402-enabled endpoint serves a specific IPFS-pinned video file (MP4) gated behind a micropayment of 0.01 USDC on the Base Sepolia testnet. The content is identified by its IPFS CID (`bafkreifmx3xajsrbfpzsrq2bbmwznnbkcnicuzdydi6yixuubd3c325x2e`) and is hosted on a Pinata-based gateway (`grapevine.dev-mypinata.cloud`). To access the file, a caller must include a valid `x-payment` header conforming to the x402 protocol (version 1, "exact" scheme).
The payment is routed to address `0x9F137a6134B62437813E4eF88bac89f6Cb408511` using the USDC token contract at `0x036CbD53842c5426634e7929541eC2318f3dCF7e` on Base Sepolia. The maximum amount required is 10,000 units (0.01 USDC with 6 decimals), and the payment timeout is 60 seconds. Upon successful payment verification, the endpoint returns the video content directly as `video/mp4`.
This appears to be a demonstration or early-stage deployment of pay-per-content delivery over IPFS using the x402 protocol. Documentation, OpenAPI specs, and additional context about the provider ("Grapevine") are not available — the crawled pages all return error messages. The endpoint itself is live and responds with a well-formed 402 challenge.
Capabilities
Use cases
- —Purchasing access to a specific IPFS-hosted MP4 video file via micropayment
- —Testing x402 payment flows on Base Sepolia testnet
- —Demonstrating pay-per-content delivery over decentralized storage
Fit
Best for
- —Developers experimenting with x402 payment-gated content
- —Testing micropayment flows on Base Sepolia
- —Accessing a specific paywalled video file on IPFS
Not for
- —Production/mainnet paid content delivery (this uses a testnet)
- —Querying or searching across multiple files — this serves a single CID
- —Streaming or adaptive bitrate video delivery
Quick start
curl -X GET \
-H "x-payment: <valid-x402-payment-header>" \
https://grapevine.dev-mypinata.cloud/x402/cid/bafkreifmx3xajsrbfpzsrq2bbmwznnbkcnicuzdydi6yixuubd3c325x2e \
--output video.mp4Endpoint
Quality
The endpoint is live and returns a well-formed x402 challenge with clear payment parameters and MIME type. However, there is no documentation, no OpenAPI spec, no examples, and all crawled pages return errors. The listing is essentially derived entirely from the 402 challenge itself, with significant context inferred.
Warnings
- —No documentation or OpenAPI spec available — all crawled pages return errors
- —Uses Base Sepolia testnet, not mainnet — payments use testnet USDC with no real monetary value
- —Single-CID endpoint: serves exactly one file, not a general-purpose API
- —Provider identity ('Grapevine') is unclear with no discoverable information
Citations
- —Endpoint returns a 402 challenge with x402Version 1, exact scheme, on base-sepolia for 0.01 USDChttps://grapevine.dev-mypinata.cloud/x402/cid/bafkreifmx3xajsrbfpzsrq2bbmwznnbkcnicuzdydi6yixuubd3c325x2e
- —MIME type of the gated content is video/mp4https://grapevine.dev-mypinata.cloud/x402/cid/bafkreifmx3xajsrbfpzsrq2bbmwznnbkcnicuzdydi6yixuubd3c325x2e
- —Payment is routed to 0x9F137a6134B62437813E4eF88bac89f6Cb408511 using USDC at 0x036CbD53842c5426634e7929541eC2318f3dCF7ehttps://grapevine.dev-mypinata.cloud/x402/cid/bafkreifmx3xajsrbfpzsrq2bbmwznnbkcnicuzdydi6yixuubd3c325x2e