Pay-per-request IPFS content retrieval via x402 on Base Sepolia (USDC)
What it does
This endpoint serves IPFS-pinned content behind an x402 paywall, hosted on a Pinata IPFS gateway (dev-mypinata.cloud). When a GET request is made without payment, the server returns a 402 challenge requiring an x-payment header with a USDC payment on the Base Sepolia testnet. Once payment is verified, the endpoint delivers the content identified by the CID `bafkreihqoybdolvloa6pqlksh6sggaf24vncv2kynn77mfblx3nue67qye` as `application/json`.
The price per request is 1000 base units of USDC (6 decimals), which equals $0.001 — a fraction of a cent per call. Payment is settled on Base Sepolia using the USDC contract at `0x036CbD53842c5426634e7929541eC2318f3dCF7e`, with funds sent to `0x6135561038e7c676473431842e586c8248276aed`. The x402 protocol version is 1, using the "exact" payment scheme with a maximum timeout of 60 seconds.
Documentation is essentially nonexistent — the origin returns generic Pinata gateway errors for all non-CID paths, and no OpenAPI spec, README, or description is provided. The CID-specific content type is declared as `application/json`, but the actual payload structure is unknown without completing a payment. This appears to be a testnet demonstration or experimental deployment rather than a production service.
Capabilities
Use cases
- —Monetizing IPFS-pinned JSON content with per-request micropayments
- —Demonstrating x402 protocol integration with IPFS gateways
- —Gating access to specific pinned content behind crypto payments
Fit
Best for
- —Developers experimenting with x402 payment protocol on testnet
- —Monetizing individual IPFS-pinned files via micropayments
- —Learning how x402 paywalls work with IPFS content
Not for
- —Production workloads (uses Base Sepolia testnet, not mainnet)
- —Bulk IPFS content retrieval without payment overhead
- —Users who need documentation or guaranteed SLAs
Quick start
curl -X GET \
-H "X-Payment: <x402-payment-header>" \
https://purple-peculiar-wolf-522.dev-mypinata.cloud/x402/cid/bafkreihqoybdolvloa6pqlksh6sggaf24vncv2kynn77mfblx3nue67qyeEndpoint
Quality
The endpoint is live and returns a valid x402 challenge, but there is zero documentation, no description field in the challenge, no OpenAPI spec, and the actual response payload is unknown. The testnet settlement and anonymous deployment make this a stub-level listing.
Warnings
- —No documentation available — all non-CID paths return Pinata gateway errors
- —Payment settles on Base Sepolia (testnet), not a production network
- —The x402 challenge description field is empty — no indication of what the content contains
- —Actual response payload structure is unknown; mimeType is declared as application/json but content is unverified
- —No OpenAPI schema or API description provided
Citations
- —Endpoint returns a 402 challenge with x402Version 1, exact scheme, on base-sepolia networkhttps://purple-peculiar-wolf-522.dev-mypinata.cloud/x402/cid/bafkreihqoybdolvloa6pqlksh6sggaf24vncv2kynn77mfblx3nue67qye
- —USDC asset contract is 0x036CbD53842c5426634e7929541eC2318f3dCF7e with maxAmountRequired of 1000 base unitshttps://purple-peculiar-wolf-522.dev-mypinata.cloud/x402/cid/bafkreihqoybdolvloa6pqlksh6sggaf24vncv2kynn77mfblx3nue67qye
- —Origin root returns 400 with 'No CID provided' errorhttps://purple-peculiar-wolf-522.dev-mypinata.cloud