x402base-sepoliaquality 0.20

Pay-per-access IPFS content retrieval via x402 on Pinata gateway (base-sepolia)

Price
1.00 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint serves IPFS content gated behind an x402 payment challenge. It is hosted on a Pinata-based gateway (grapevine.dev-mypinata.cloud) and resolves a specific CID (bafkreigorlw5bfctawuuzkdsh3ta47fxlsyfoem2fylnqy456fj6grkyae). The listed price is 1 USDC on the Base Sepolia testnet, indicating this is likely a development or demonstration deployment rather than a production service.

The endpoint follows the x402 protocol pattern: unauthenticated requests are expected to receive an HTTP 402 response containing a payment challenge, which the caller satisfies by submitting a signed payment. However, during probing the endpoint returned HTTP 429 (rate limited) on GET and 405 (method not allowed) on POST, so the 402 challenge was not directly captured. The root domain returns generic error messages ("No CID provided" or "Invalid URL") for all non-CID paths, and no documentation, OpenAPI schema, or agents.txt was found.

Given the sparse information available — no docs, no captured 402 challenge, no schema, and only a Bazaar listing description — this listing should be treated as a stub. The endpoint may be functional but rate-limited or intermittently available. Callers should expect to provide an x402-compatible payment header when making GET requests to the full CID URL.

Capabilities

ipfs-content-retrievalx402-payment-gatingpinata-gatewaybase-sepolia-usdccid-resolution

Use cases

  • Retrieving pay-gated IPFS content via x402 micropayment
  • Testing x402 payment flows on Base Sepolia testnet
  • Monetizing individual IPFS-pinned files behind a paywall

Fit

Best for

  • Developers testing x402 payment integrations on testnet
  • Gating access to specific IPFS content behind micropayments
  • Experimenting with pay-per-file decentralized storage access

Not for

  • Production-grade content delivery (this uses a testnet token)
  • Bulk or high-throughput IPFS retrieval (rate limiting observed)
  • Discovering or searching IPFS content (serves a single CID)

Quick start

curl -i https://grapevine.dev-mypinata.cloud/x402/cid/bafkreigorlw5bfctawuuzkdsh3ta47fxlsyfoem2fylnqy456fj6grkyae

Endpoint

Transporthttp
Protocolx402
Pay to0xbc03df2D9F44Cc552EbbFF39860f2CC4fC751d0E
CurrencyUSDC

Quality

0.20/ 1.00

No 402 challenge was captured (429 on GET, 405 on POST). No documentation, no schema, no examples exist. The Bazaar listing provides only a price and network. This is effectively a stub with uncertain liveness.

Warnings

  • 402 challenge was NOT captured during probing — endpoint returned 429 (GET) and 405 (POST)
  • No documentation, OpenAPI schema, or usage examples found anywhere on the domain
  • All non-CID paths return generic error messages; no docs endpoint exists
  • Uses Base Sepolia testnet USDC — this is a test/dev deployment, not production
  • Rate limiting (429) suggests the endpoint may throttle or block automated probes

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-18 19:20:20Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-18
Last seen2026-04-22

Agent access