Staging x402 payment-link endpoint on Merit Systems (currently offline).
What it does
This endpoint at staging-echo.merit.systems is listed as an x402-protocol payment-link resource under the path /api/v1/base/payment-link. The existing description states it provides "access to protected content," suggesting it is meant to gate content behind an x402 micropayment challenge.
However, all probe and crawl attempts returned Vercel DEPLOYMENT_NOT_FOUND errors (HTTP 404) across every path tested, including the root, /docs, /api, /pricing, and /README. The x402 challenge probe also returned a 404 rather than the expected 402 status. This indicates the Vercel deployment backing this staging environment is either not yet deployed, has been torn down, or is misconfigured.
No OpenAPI schema, agents.txt, robots.txt, or any other documentation was recoverable. Without a live endpoint or documentation, the actual capabilities, pricing, request/response formats, and authentication requirements remain entirely unknown. This listing is effectively a stub pending the deployment becoming available.
Capabilities
Use cases
- —Gating digital content behind x402 micropayments
- —Generating payment links for on-demand content access
- —Agent-initiated pay-per-request content retrieval
Fit
Best for
- —Developers experimenting with x402 payment protocols
- —Agents that need to pay for gated content programmatically
- —Testing x402 integration in staging environments
Not for
- —Production workloads (this is a staging endpoint and is currently offline)
- —Anyone needing reliable, always-available content access
Quick start
# Endpoint is currently offline (DEPLOYMENT_NOT_FOUND).
# When live, a GET request should return a 402 challenge:
curl -i https://staging-echo.merit.systems/api/v1/base/payment-linkEndpoint
Quality
The deployment is completely offline—every probed URL returns Vercel DEPLOYMENT_NOT_FOUND 404 errors. No schema, documentation, pricing, or live x402 challenge could be retrieved. This is effectively a broken stub.
Warnings
- —Deployment is offline: all URLs return Vercel DEPLOYMENT_NOT_FOUND (404).
- —No x402 challenge was returned; the endpoint did not respond with HTTP 402.
- —No documentation, OpenAPI spec, or any recoverable metadata exists.
- —This is explicitly a staging environment and should not be relied upon for production use.
Citations
- —All crawled pages return Vercel DEPLOYMENT_NOT_FOUND 404 errors.https://staging-echo.merit.systems
- —The x402 challenge probe returned 404 instead of 402.https://staging-echo.merit.systems/api/v1/base/payment-link