75trust / 100

Backtest

by nsgoods Crypto Signals (Kraken) in Onchain & crypto

x402 APIPassing, checked 3 h ago

Walk-forward replay of the live multi-timeframe strategy over recent 1m history: win-rate and average forward return per BUY/SELL signal. Lets an agent measure recent edge before subscribing to the live signal stream (USDC on Base). Free preview: GET /signals/preview

GET
https://signals.nsgoods.org/backtest
Price
$0.25
per call in USDC
Uptime
100%
last 30 days
Response time
398 ms
644 ms slowest 5%
Last check
Passed
3 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://signals.nsgoods.org/backtest

Each call costs $0.25 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://signals.nsgoods.org/backtest?forward=30&pair=BTC%2FUSD&step=5

Parameters

ParameterTypeRequiredDescription
forwardintegerNoForward window in 1m bars to score each signal against (5-120). Default: 30.
pairstringNoKraken */USD pair, e.g. BTC/USD, ETH/USD. Default: "BTC/USD".
stepintegerNoWalk-forward step in 1m bars (1-15). Smaller = denser sample but slower. Default: 5.

Example response

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

{
  "avg_return_pct": 0.18,
  "best_pct": 1.42,
  "forward_minutes": 30,
  "generated_at": "2026-06-13T21:00:00+00:00",
  "pair": "BTC/USD",
  "sample": [
    {
      "entry": 64120.4,
      "future": 64235.1,
      "return_pct": 0.179,
      "signal": "BUY",
      "ts": "2026-06-13T18:25:00"
    }
  ],
  "signals_evaluated": 14,
  "step_minutes": 5,
  "win_rate_pct": 64.3,
  "window_hours": 12,
  "worst_pct": -0.71
}

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.25.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://signals.nsgoods.org/backtest?forward=30&pair=BTC%2FUSD&step=5'

# 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://signals.nsgoods.org/backtest?forward=30&pair=BTC%2FUSD&step=5' \
  | 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.25 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.25" });
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.25 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fsignals.nsgoods.org%2Fbacktest
const res = await pay("https://signals.nsgoods.org/backtest?forward=30&pair=BTC%2FUSD&step=5");
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.25 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.25"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://signals.nsgoods.org/backtest?forward=30&pair=BTC%2FUSD&step=5")
    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
3 h agoPassed402406 ms$0.25
8 h agoPassed402356 ms$0.25
12 h agoPassed402404 ms$0.25
16 h agoPassed402396 ms$0.25
20 h agoPassed402651 ms$0.25
Show 10 older checks
24 h agoPassed402394 ms$0.25
29 h agoPassed402400 ms$0.25
33 h agoPassed402400 ms$0.25
37 h agoPassed402398 ms$0.25
41 h agoPassed402360 ms$0.25
46 h agoPassed402398 ms$0.25
2 days agoPassed402391 ms$0.25
2 days agoPassed402387 ms$0.25
2 days agoPassed402118 ms$0.25
3 days agoPassed402384 ms$0.25