Discover / backend-production-69ff.up.railway.app

backend-production-69ff.up.railway.app

■ Challenge detected

Live directional read from a real-money Kalshi BTC hourly (KXBTCD) trading model: current near-the-money strike, model probability vs market price, and computed edge. Informational model output, not investment advice — the strategy's real historical win rate / P&L is public at the bot's dashboard, good and bad stretches included.

Challenge detected
1 of the last check
Median response
109 ms
Last checked
4 Oct, 05:05 UTC
In our index since
4 Oct 2026

Endpoint

curl -i https://backend-production-69ff.up.railway.app/x402/signal/btc-hourly
# 402 Payment Required: pay with an x402 client (USDC on Base),
# then send the same request again with the payment attached.

Agents can find it through the Superstables MCP server and JSON API: GET /api/v1/services/backend-production-69ff.up.railway.app

Recent checks

4 Oct 2026One bar per check, showing up to 20 recent checks. Coloured bars show relative response time, with a minimum visible height; full-height grey bars mean no challenge was detected. “Challenge detected” means HTTP 402 or another detected payment-challenge signal.4 Oct 2026
All 1 checks
When (UTC)ResultHTTPResponse
4 Oct, 05:05 UTCChallenge detected402109ms

Questions

Did our last probe detect a payment challenge?

At our last probe on 4 Oct, 05:05 UTC, it returned HTTP 402 or another detected payment-challenge signal. This check did not test payment, delivery or compatibility with the Superstables client.

What payment terms does backend-production-69ff.up.railway.app advertise?

The listing advertises x402, Base and USDC. It names cdp as its facilitator. Check the seller's current payment challenge and authentication requirements before paying.

Where is backend-production-69ff.up.railway.app listed?

In x402 Bazaar. Superstables first indexed it on 4 Oct 2026.

Something wrong on this page? Tell us.