13trust / 100

Brief

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

x402 APIFailing, checked 6 h ago

BTC/ETH technical + sentiment research brief (price, 24h/7d change, RSI14, SMA20/50, trend, Fear & Greed)

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

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 6 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/brief/:asset

Each call costs $0.05 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/brief/:asset

Example response

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

{
  "asset": "BTC",
  "change24hPct": -0.55,
  "change7dPct": -0.92,
  "price": 80631.35,
  "rsi14": 43.71,
  "sentiment": {
    "classification": "Neutral",
    "fearGreedIndex": 51
  },
  "sma20": 82531.74,
  "sma50": 81794.82,
  "trend": {
    "rsiState": "neutral",
    "score": -1,
    "signal": "neutral"
  }
}

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

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/brief/: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/brief/: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.05 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.05" });
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.05 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fx402-research-iota.vercel.app%2Fapi%2Fbrief%2F%3Aasset
const res = await pay("https://x402-research-iota.vercel.app/api/brief/: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.05 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.05"})
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/brief/: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
6 h agoExpected HTTP 402, got 404404260 ms-
15 h agoExpected HTTP 402, got 404404263 ms-
23 h agoExpected HTTP 402, got 404404486 ms-
31 h agoExpected HTTP 402, got 404404246 ms-
39 h agoExpected HTTP 402, got 404404429 ms-
Show 10 older checks
47 h agoExpected HTTP 402, got 404404291 ms-
2 days agoExpected HTTP 402, got 404404238 ms-
3 days agoExpected HTTP 402, got 404404369 ms-
3 days agoExpected HTTP 402, got 404404264 ms-
3 days agoExpected HTTP 402, got 404404406 ms-
4 days agoExpected HTTP 402, got 404404924 ms-
4 days agoExpected HTTP 402, got 404404357 ms-
4 days agoExpected HTTP 402, got 404404376 ms-
4 days agoExpected HTTP 402, got 4044041.2 s-
5 days agoExpected HTTP 402, got 404404241 ms-