x402-protected endpoint returning JSON content for 100 USDC units on Base
What it does
This is a demo x402-enabled endpoint hosted on Netlify, built with Next.js. It serves protected JSON content behind an HTTP 402 paywall using the x402 protocol (version 1). To access the resource, a client must include a valid X-PAYMENT header satisfying the payment challenge.
The endpoint accepts payment via the "exact" scheme on the Base network. The required asset is USDC (contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) with a maxAmountRequired of 100 (in the token's smallest unit). Payments are directed to address 0x32d19F868559AC212555B41C0Eb35FB2EECD7877, and the payment timeout is 300 seconds. The response MIME type is application/json.
Because this is described as a "fullstack demo," the actual protected content is unknown and likely minimal or illustrative. No documentation, OpenAPI spec, or detailed description of the response payload is available. The site returns 404 for /docs, /api, /pricing, and /README. Treat this as a reference implementation of x402 rather than a production data service.
Capabilities
Use cases
- —Testing x402 client implementations against a live endpoint
- —Demonstrating HTTP 402 payment flows with USDC on Base
- —Prototyping agent-driven micropayment workflows
Fit
Best for
- —Developers building or testing x402-compatible agents
- —Learning how the x402 protocol challenge-response works
- —Verifying USDC payment integration on Base
Not for
- —Production data retrieval — this is a demo with unknown payload
- —Users needing detailed API documentation or guaranteed SLAs
- —High-value transactions — no information on refund or dispute mechanisms
Quick start
curl -i https://x402-next.netlify.app/protected
# Returns 402 with x402 challenge JSON.
# To access, include a valid X-PAYMENT header:
curl -H "X-PAYMENT: <signed-payment-payload>" \
https://x402-next.netlify.app/protectedExample
Response
{
"error": "X-PAYMENT header is required",
"accepts": [
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0x32d19F868559AC212555B41C0Eb35FB2EECD7877",
"scheme": "exact",
"network": "base",
"mimeType": "application/json",
"resource": "https://x402-next.netlify.app/protected",
"description": "Access to protected content",
"maxAmountRequired": "100",
"maxTimeoutSeconds": 300
}
],
"x402Version": 1
}Endpoint
Quality
The endpoint is live and returns a well-formed x402 challenge, but there is no documentation, no OpenAPI schema, no description of the actual protected payload, and the site self-identifies as a demo. Significant inference was required for most listing fields.
Warnings
- —Self-described as a 'fullstack demo' — not a production service
- —No documentation available (all doc/api/pricing/readme paths return 404)
- —Protected content payload is completely unknown
- —No information on refund, dispute, or uptime guarantees
- —maxAmountRequired is '100' but the unit denomination (wei-level or dollar-level) is ambiguous without further context
Citations
- —The endpoint returns an x402 challenge requiring USDC payment on Base network with maxAmountRequired of 100https://x402-next.netlify.app/protected
- —The site describes itself as a 'Fullstack demo powered by Next.js'https://x402-next.netlify.app
- —The USDC asset contract is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 and payTo address is 0x32d19F868559AC212555B41C0Eb35FB2EECD7877https://x402-next.netlify.app/protected