ToolVet
75trust / 100

Signal Btc Hourly

by Kalshi BTC Hourly Signal in Markets & finance

x402 APIPassing, checked 5 h ago

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.

GET
https://backend-production-69ff.up.railway.app/x402/signal/btc-hourly
Price
$0.02
per call in USDC
Uptime
100%
last 30 days
Response time
355 ms
429 ms slowest 5%
Last check
Passed
5 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

GET https://backend-production-69ff.up.railway.app/x402/signal/btc-hourly

Each call costs $0.02 in USDC on Base, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

GET https://backend-production-69ff.up.railway.app/x402/signal/btc-hourly

Example response

The provider's example. We can't check it without paying.

{
  "annualizedVolatility": 0.42,
  "generatedAt": "2026-10-03T19:00:00.000Z",
  "note": null,
  "signal": {
    "closeTime": "2026-10-03T18:00:00.000Z",
    "edge": 0.11,
    "eventTicker": "KXBTCD-26OCT0318",
    "marketProbability": 0.6,
    "marketTicker": "KXBTCD-26OCT0318-B84500",
    "modelProbability": 0.71,
    "side": "yes",
    "strike": 84500
  },
  "spot": 84638
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.02.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://backend-production-69ff.up.railway.app/x402/signal/btc-hourly'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://backend-production-69ff.up.railway.app/x402/signal/btc-hourly' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.02 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.02" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.02 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fbackend-production-69ff.up.railway.app%2Fx402%2Fsignal%2Fbtc-hourly
const res = await pay("https://backend-production-69ff.up.railway.app/x402/signal/btc-hourly");
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.02 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.02"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://backend-production-69ff.up.railway.app/x402/signal/btc-hourly")
    print(res.status_code, res.text)

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
5 h agoPassed402374 ms$0.02
10 h agoPassed402344 ms$0.02
14 h agoPassed402342 ms$0.02
19 h agoPassed402298 ms$0.02
24 h agoPassed402355 ms$0.02
Show 10 older checks
28 h agoPassed402367 ms$0.02
32 h agoPassed402405 ms$0.02
36 h agoPassed402378 ms$0.02
40 h agoPassed402345 ms$0.02
45 h agoPassed402355 ms$0.02
2 days agoPassed402391 ms$0.02
2 days agoPassed402339 ms$0.02
2 days agoPassed402443 ms$0.02
3 days agoPassed402335 ms$0.02
3 days agoPassed402339 ms$0.02