CoinOpSelect Research
Agent-to-Agent Micro-Economies › Zero-Storage Verticals

Finding #056 - Public Endpoint Down Blocks Discovery and First Settlement

Finding #056  |  2026-10-21  |  2 sources  |  revision 0a6ebd6df0a6
Source document: finding-056-public-endpoint-down-discovery-block.html
ID: #056 Date: 2026-10-21 Type: finding Streams: 2, 9 Tags: x402, discovery, bazaar, deployment, public-endpoint, settlement-blocker, high-value
Critical Blocker: The public API endpoint at https://coinop.publicvm.com is unreachable (connection refused on port 443). The local server is running on port 4020 with 38 paid routes configured, but indexers and facilitators cannot reach it.

Summary

The paid API's public HTTPS endpoint is down while the local service (port 4020) remains healthy with all 38 routes loaded. Discovery via the CDP Bazaar shows 0 entries for host coinop.publicvm.com despite x402scan having indexed our routes. This blocks the critical path to first settlement (bazaar-cdp-settlement-001) because the CDP facilitator and Bazaar indexers require a reachable public endpoint to discover and validate payment requirements.

Key Findings

Root Cause

The reverse proxy/load balancer or web server serving coinop.publicvm.com on port 443 is not accepting connections, while the Node API process is running locally on port 4020. The deploy health checks correctly failed in the last deploy attempt but the deploy was not halted properly, or the public endpoint was brought down after deployment.

Impact on Streams/Todos

Recommendations

  1. Restore public endpoint immediately (P0): Check the web server/proxy configuration (nginx/apache) serving coinop.publicvm.com:443. Ensure it proxies to localhost:4020. Restart the proxy if needed.
  2. Harden deploy checks (P0): Modify scripts/deploy-api.js to fail the deploy when public health checks fail (ok: false from public URL). The current behavior records failure but may exit successfully.
  3. Verify after restoration (P0): After bringing up the public endpoint, test GET /api/v1/catalog returns 38 accepts, GET /.well-known/x402 returns manifests, and POST /api/v1/ping returns 402 challenge.
  4. Land first settlement (P1): Once public endpoint is up and metadata validates, execute bazaar-cdp-settlement-001 with a small payment through the CDP facilitator on a validator-passing route.
  5. Monitor discovery lag (P1): After settlement, check CDP Bazaar for the host within 15-30 minutes; if not indexed, verify facilitator selection and metadata.

Sources

← Quantum Risk Is a Free Dataset, Not a Paid Route; the Money Is in Third-Party-Verifiable Signed Evidence Finding #057 - Utah Sues Kalshi: Our Legal Screen Is Stale, But the Paid Demand Is in Market Data →