ToolVet
27trust / 100

Data Market History

by asistent-crypto.vercel.app in Onchain & crypto

x402 APIFailing, checked 5 min ago

Whether the current reading is actually high or low, from a series captured every ~10 minutes: funding, open interest, Fear & Greed and BTC dominance, each as current, median, min, max and percentile over the window. A funding rate of 0.006% means nothing on its own; at the 89th percentile of the last 24 hours it means something. This is the question a snapshot endpoint cannot answer, whoever you buy it from.

POST
https://asistent-crypto.vercel.app/api/x402/data/market-history
Price
$0.04
per call in USDC
Uptime
5.1%
last 30 days
Response time
146 ms
199 ms slowest 5%
Last check
Failed
5 min ago, next in 55 min

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 5 min ago: HTTP 402 without a parseable x402 challenge

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

How to call it

POST https://asistent-crypto.vercel.app/api/x402/data/market-history

Each call costs $0.04 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.

POST https://asistent-crypto.vercel.app/api/x402/data/market-history
content-type: application/json

{
  "hours": 24
}

Example response

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

{
  "data": {},
  "ok": true,
  "tool": "get_market_history"
}

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

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://asistent-crypto.vercel.app/api/x402/data/market-history' \
  -H 'content-type: application/json' \
  --data-raw '{"hours":24}'

# 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 - -X POST 'https://asistent-crypto.vercel.app/api/x402/data/market-history' \
  -H 'content-type: application/json' \
  --data-raw '{"hours":24}' \
  | 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.04 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.04" });
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.04 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fasistent-crypto.vercel.app%2Fapi%2Fx402%2Fdata%2Fmarket-history&method=POST
const res = await pay("https://asistent-crypto.vercel.app/api/x402/data/market-history", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "hours": 24
  }),
});
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.04 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.04"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://asistent-crypto.vercel.app/api/x402/data/market-history",
        json={
            "hours": 24,
        },
    )
    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 min agoHTTP 402 without a parseable x402 challenge40274 ms-
4 h agoHTTP 402 without a parseable x402 challenge40296 ms-
10 h agoHTTP 402 without a parseable x402 challenge40281 ms-
15 h agoHTTP 402 without a parseable x402 challenge402113 ms-
21 h agoHTTP 402 without a parseable x402 challenge40294 ms-
Show 10 older checks
27 h agoHTTP 402 without a parseable x402 challenge40277 ms-
33 h agoHTTP 402 without a parseable x402 challenge40253 ms-
38 h agoHTTP 402 without a parseable x402 challenge402117 ms-
44 h agoHTTP 402 without a parseable x402 challenge40279 ms-
2 days agoHTTP 402 without a parseable x402 challenge402105 ms-
2 days agoHTTP 402 without a parseable x402 challenge402102 ms-
3 days agoHTTP 402 without a parseable x402 challenge40248 ms-
3 days agoHTTP 402 without a parseable x402 challenge40285 ms-
3 days agoHTTP 402 without a parseable x402 challenge402117 ms-
3 days agoHTTP 402 without a parseable x402 challenge40277 ms-