Pay 0.10 USDC on Base to unlock protected content via the x402 protocol.
What it does
This x402-enabled endpoint gates access to protected content behind a USDC micropayment on the Base network. When a caller sends a POST request without a valid X-PAYMENT header, the endpoint returns an HTTP 402 challenge specifying the payment terms: 0.10 USDC (represented as 100000 in the asset's smallest unit) paid to address 0x81A8AF3fFdf56927930C80D80fb143a2B31b0355 using the USDC contract on Base (0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913). The payment scheme is "exact" and the maximum timeout is 60 seconds.
The endpoint is hosted on Vercel at x402-ivory.vercel.app and appears to be a minimal demonstration or template of the x402 payment protocol. The landing page confirms the price (0.10 USDC), network (Base), and protocol (x402). No additional documentation, API reference, or detailed description of the protected content itself is available — the site has no /docs, /pricing, or README pages.
Because the nature of the "exclusive content" returned after successful payment is not documented anywhere in the crawled material, consumers should treat this as a generic x402 demo endpoint. There is no OpenAPI schema, no description of response format beyond what the x402 challenge's outputSchema hints at (HTTP POST, discoverable), and no information about rate limits or SLAs.
Capabilities
Use cases
- —Demonstrating x402 protocol integration for pay-per-access content
- —Testing agent-driven USDC micropayments on the Base network
- —Prototyping paywall flows using the x402 standard
Fit
Best for
- —Developers experimenting with the x402 payment protocol
- —Agents that need a live x402 endpoint for integration testing
- —Learning how 402 Payment Required challenges work with USDC on Base
Not for
- —Production content delivery with SLA guarantees (no docs or uptime commitments)
- —Users who need detailed API documentation or response schema
Quick start
curl -X POST http://x402-ivory.vercel.app/api/protected-content
# Returns 402 with x402 challenge JSON.
# Include a valid X-PAYMENT header with a signed USDC payment to unlock content.Example
Request
{
"url": "http://x402-ivory.vercel.app/api/protected-content",
"method": "POST",
"headers": {
"X-PAYMENT": "<signed-x402-payment-token>"
}
}Response
{
"error": "X-PAYMENT header is required",
"accepts": [
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0x81A8AF3fFdf56927930C80D80fb143a2B31b0355",
"scheme": "exact",
"network": "base",
"mimeType": "",
"resource": "http://x402-ivory.vercel.app/api/protected-content",
"description": "Access to protected content",
"maxAmountRequired": "100000",
"maxTimeoutSeconds": 60
}
],
"x402Version": 1
}Endpoint
Quality
The endpoint is live and returns a well-formed x402 402 challenge, but there is no documentation, no OpenAPI schema, no description of what the protected content actually is, and no information about the successful response format. This is effectively a minimal demo with only the payment challenge as documentation.
Warnings
- —No documentation available — /docs, /pricing, and /README all return 404
- —The nature of the 'protected content' returned after payment is completely undocumented
- —No OpenAPI or response schema provided; successful response format is unknown
- —Appears to be a demo/template project rather than a production service
- —mimeType in the challenge is empty, giving no hint about the content type returned
Citations
- —Price is 0.10 USDC on the Base networkhttp://x402-ivory.vercel.app
- —Payment address is 0x81A8AF3fFdf56927930C80D80fb143a2B31b0355 using USDC contract 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913http://x402-ivory.vercel.app/api/protected-content
- —maxAmountRequired is 100000 (0.10 USDC) with maxTimeoutSeconds of 60http://x402-ivory.vercel.app/api/protected-content