Pay 1 USDC on Base to retrieve content by CID from the Grapevine gateway.
What it does
This x402-enabled endpoint on the Grapevine gateway serves content addressed by CID (Content Identifier) in exchange for a micropayment of 1 USDC on the Base network. The endpoint follows the x402 protocol: an unauthenticated GET request returns a 402 Payment Required challenge, and once a valid `x-payment` header is supplied, the gateway delivers the requested content as `application/octet-stream`.
The specific CID served is `bafkreie6t4rl5jij2vyxp4hp4gkpqexnklavf3p43zet23sj4b6eybuaca`. The payment is routed to address `0x5ba9355a10611Ed4339526472a59bEfed3549bAD` using the USDC token contract on Base (`0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913`). The maximum amount required is 1,000,000 units (1 USDC at 6 decimals), with a payment timeout of 60 seconds.
Documentation for the Grapevine gateway is sparse. The root domain returns an error indicating a missing CID, and no docs, API reference, or pricing pages were found. The gateway appears to be a content-addressed paywall service, but details beyond what the x402 challenge provides are unavailable.
Capabilities
Use cases
- —Purchasing access to a specific piece of content identified by CID
- —Programmatic content retrieval behind a crypto paywall
- —Agent-driven acquisition of paid digital assets via x402
Fit
Best for
- —Agents that need to fetch paywalled content-addressed data
- —Workflows requiring on-chain micropayments for content access
- —Automated retrieval of specific CID-referenced files
Not for
- —Browsing or discovering available content (no catalog or search exposed)
- —Users who need fiat payment options
- —Bulk or batch content downloads (single CID per endpoint)
Quick start
curl -X GET \
https://gateway.grapevine.fyi/x402/cid/bafkreie6t4rl5jij2vyxp4hp4gkpqexnklavf3p43zet23sj4b6eybuaca \
-H 'x-payment: <valid-x402-payment-token>'Endpoint
Quality
The endpoint is live and returns a well-formed x402 challenge, but there is virtually no documentation, no OpenAPI schema, no examples, and no information about what the content actually is. All metadata is inferred solely from the 402 challenge payload.
Warnings
- —No documentation found at any crawled path on gateway.grapevine.fyi
- —Content behind the paywall is opaque — the CID and mime type (application/octet-stream) give no indication of what is being sold
- —Provider description is minimal ('1 USDC on base') with no further context
- —No OpenAPI or API schema available
Citations
- —Endpoint returns HTTP 402 with x402 version 1 challenge requiring 1 USDC on Basehttps://gateway.grapevine.fyi/x402/cid/bafkreie6t4rl5jij2vyxp4hp4gkpqexnklavf3p43zet23sj4b6eybuaca
- —Payment is routed to 0x5ba9355a10611Ed4339526472a59bEfed3549bAD using USDC contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913https://gateway.grapevine.fyi/x402/cid/bafkreie6t4rl5jij2vyxp4hp4gkpqexnklavf3p43zet23sj4b6eybuaca
- —Content is served as application/octet-stream with a 60-second payment timeouthttps://gateway.grapevine.fyi/x402/cid/bafkreie6t4rl5jij2vyxp4hp4gkpqexnklavf3p43zet23sj4b6eybuaca
- —Root domain returns error 'No CID provided'https://gateway.grapevine.fyi