Pay-per-access IPFS content gateway serving a PNG image via x402 on Base Sepolia.
What it does
This endpoint is an x402-enabled IPFS content gateway hosted on Pinata infrastructure. It serves a specific piece of IPFS-pinned content — an image/png file identified by the CID `bafybeibpxcpq74uhen4tkeu4jw4bwimqsnpvjidogea4yuvelvhlfbkmyu` — behind a micropayment wall. Callers must provide a valid `x-payment` header to unlock the content.
The payment scheme uses the "exact" method on the Base Sepolia testnet, accepting USDC (contract `0x036CbD53842c5426634e7929541eC2318f3dCF7e`) with a maximum amount of 1,000,000 units (1 USDC at 6 decimals). Payments are directed to address `0x941f29fddA2CB16649b70D1C28aA5933DBba6295`. The x402 version is 1, and the timeout for payment verification is 60 seconds.
No documentation, OpenAPI spec, or additional context is available from the host beyond the x402 challenge itself. The root domain returns error messages indicating a CID is required, suggesting this is a purpose-built gateway that routes requests by CID path. This appears to be a hackathon project (as suggested by the subdomain name) and uses a testnet, so it should not be relied upon for production use.
Capabilities
Use cases
- —Purchasing access to a specific IPFS-pinned PNG image via micropayment
- —Demonstrating x402 payment flows on Base Sepolia testnet
- —Testing agent-driven content purchasing against an IPFS gateway
Fit
Best for
- —Developers experimenting with x402 protocol integration
- —Testing micropayment-gated content retrieval on a testnet
- —Hackathon demos of pay-per-access IPFS content
Not for
- —Production content delivery (testnet only, hackathon project)
- —Accessing arbitrary IPFS CIDs (endpoint is for a single specific CID)
- —High-availability or SLA-dependent workflows
Quick start
curl -X GET \
-H "x-payment: <valid-x402-payment-header>" \
https://x402hackathon.mypinata.cloud/x402/cid/bafybeibpxcpq74uhen4tkeu4jw4bwimqsnpvjidogea4yuvelvhlfbkmyuEndpoint
Quality
The x402 challenge is live and well-formed, providing clear payment details (network, asset, amount, payTo address, mimeType). However, there is no documentation, no OpenAPI spec, no examples, and no additional context beyond the challenge payload. The project appears to be a hackathon entry on a testnet.
Warnings
- —No documentation or OpenAPI schema available from the host
- —Uses Base Sepolia testnet — not suitable for production
- —Appears to be a hackathon project; longevity and maintenance are uncertain
- —Serves a single specific CID; not a general-purpose gateway
- —Root domain and all crawled paths return error messages
Citations
- —The endpoint returns a 402 challenge with x402Version 1, accepting USDC on base-sepolia with maxAmountRequired 1000000https://x402hackathon.mypinata.cloud/x402/cid/bafybeibpxcpq74uhen4tkeu4jw4bwimqsnpvjidogea4yuvelvhlfbkmyu
- —The response mimeType is image/pnghttps://x402hackathon.mypinata.cloud/x402/cid/bafybeibpxcpq74uhen4tkeu4jw4bwimqsnpvjidogea4yuvelvhlfbkmyu
- —Payment is directed to address 0x941f29fddA2CB16649b70D1C28aA5933DBba6295https://x402hackathon.mypinata.cloud/x402/cid/bafybeibpxcpq74uhen4tkeu4jw4bwimqsnpvjidogea4yuvelvhlfbkmyu
- —Root domain returns 'No CID provided' error, suggesting CID-based routinghttps://x402hackathon.mypinata.cloud