Pay 1 USDC on Base to retrieve IPFS content via x402 paywall gateway
What it does
This endpoint serves content-addressed data (identified by a CID) behind an x402 payment wall operated by Grapevine. The specific resource is an IPFS CID (bafkreicuvlxikl6eqkjfw4aegerov6cbepippqpu3caqbalodromkumioe) that costs 1 USDC on the Base network to access. The response MIME type is application/octet-stream, meaning the payload is delivered as raw binary data.
The gateway follows the x402 protocol: an unauthenticated GET request returns a 402 Payment Required response containing a payment challenge. The caller must construct a valid x-payment header (using the "exact" payment scheme) sending 1 USDC (1,000,000 units at 6 decimals) to the specified payTo address on Base. The accepted asset is the USDC contract at 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913. The payment timeout is 60 seconds.
Documentation for the Grapevine gateway is essentially nonexistent — all non-CID routes return error messages. There is no OpenAPI spec, no landing page, and no additional context about what the underlying content is. The endpoint is live and responds correctly with a well-formed x402 challenge, but the lack of documentation means consumers must rely entirely on the protocol-level metadata to understand what they are purchasing.
Capabilities
Use cases
- —Purchasing access to a specific piece of content-addressed (IPFS) data
- —Programmatic agent-driven content retrieval behind a crypto paywall
- —Demonstrating x402 payment flows on the Base network
Fit
Best for
- —Agents that need to purchase and retrieve specific IPFS-hosted binary content
- —Developers experimenting with x402 protocol payments on Base
- —Automated workflows that can sign USDC transactions on Base
Not for
- —Free or low-friction content retrieval — requires an on-chain USDC payment
- —Browsing or discovering available content — only a single CID is served at this URL
- —Users without a Base-compatible wallet holding USDC
Quick start
curl -X GET \
https://gateway.grapevine.fyi/x402/cid/bafkreicuvlxikl6eqkjfw4aegerov6cbepippqpu3caqbalodromkumioe \
-H 'X-Payment: <valid-x402-payment-header>'Endpoint
Quality
The endpoint is live and returns a well-formed x402 challenge, but there is zero documentation, no OpenAPI spec, no description of the underlying content, and all crawled pages return errors. The listing is essentially a stub built from the 402 challenge metadata alone.
Warnings
- —No documentation available — all gateway routes return error messages
- —Content behind the paywall is unknown (application/octet-stream with no description beyond '1 USDC on base')
- —No OpenAPI or schema beyond the x402 challenge outputSchema
- —Provider landing page returns HTTP 400 with 'No CID provided' error
Citations
- —The endpoint returns a 402 challenge requesting 1,000,000 units (1 USDC) on Base via the exact schemehttps://gateway.grapevine.fyi/x402/cid/bafkreicuvlxikl6eqkjfw4aegerov6cbepippqpu3caqbalodromkumioe
- —The accepted USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://gateway.grapevine.fyi/x402/cid/bafkreicuvlxikl6eqkjfw4aegerov6cbepippqpu3caqbalodromkumioe
- —The response MIME type is application/octet-streamhttps://gateway.grapevine.fyi/x402/cid/bafkreicuvlxikl6eqkjfw4aegerov6cbepippqpu3caqbalodromkumioe
- —The root gateway URL returns HTTP 400 with 'No CID provided' errorhttps://gateway.grapevine.fyi