15trust / 100

Signal

by x402-research-iota.vercel.app in Other

x402 APIFailing, checked 3 h ago

Compact trend signal (bullish/neutral/bearish + score). Assets: btc,eth,sol,xrp,doge,ada,avax,link,dot,ltc,bch,uni,aave,xlm,hbar,shib,sui,near,atom,fil. Free delayed sample: /api/sample/signal

GET
https://x402-research-iota.vercel.app/api/signal/:asset
Price
$0.01
per call in USDC
Uptime
0.0%
last 30 days
Response time
-
no timed checks yet
Last check
Failed
3 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 3 h ago: Expected HTTP 402, got 404

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

How to call it

GET https://x402-research-iota.vercel.app/api/signal/:asset

Each call costs $0.01 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://x402-research-iota.vercel.app/api/signal/:asset

Example response

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

{
  "asset": "ETH",
  "at": "2026-10-24T00:52:56.540Z",
  "disclaimer": "Informational only, not financial advice.",
  "price": 2373.03,
  "rsi14": 37.59,
  "score": -3,
  "signal": "bearish"
}

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

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://x402-research-iota.vercel.app/api/signal/:asset'

# 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://x402-research-iota.vercel.app/api/signal/:asset' \
  | 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.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
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.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fx402-research-iota.vercel.app%2Fapi%2Fsignal%2F%3Aasset
const res = await pay("https://x402-research-iota.vercel.app/api/signal/:asset");
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.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://x402-research-iota.vercel.app/api/signal/:asset")
    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 agoExpected HTTP 402, got 404404257 ms-
12 h agoExpected HTTP 402, got 404404315 ms-
20 h agoExpected HTTP 402, got 404404486 ms-
28 h agoExpected HTTP 402, got 404404244 ms-
36 h agoExpected HTTP 402, got 404404281 ms-
Show 10 older checks
44 h agoExpected HTTP 402, got 404404277 ms-
2 days agoExpected HTTP 402, got 404404245 ms-
3 days agoExpected HTTP 402, got 404404479 ms-
3 days agoExpected HTTP 402, got 4044041.3 s-
3 days agoExpected HTTP 402, got 4044041.1 s-
3 days agoExpected HTTP 402, got 404404442 ms-
4 days agoExpected HTTP 402, got 404404596 ms-
4 days agoExpected HTTP 402, got 404404278 ms-
4 days agoExpected HTTP 402, got 404404440 ms-
5 days agoExpected HTTP 402, got 404404419 ms-