ToolVet
27trust / 100

Data Brief

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

x402 APIFailing, checked 4 h ago

The answer, not the inputs. One call returns a stance for the coin — risk-on, risk-off, fragile or neutral — built from funding and open interest percentiles, sentiment, options implied volatility, the macro regime and what it costs to execute at your size. Every driver comes back with its number and its reading, plus the conditions that would invalidate the call. The rules are deterministic: the same market gives the same verdict.

POST
https://asistent-crypto.vercel.app/api/x402/data/brief
Price
$0.05
per call in USDC
Uptime
5.3%
last 30 days
Response time
143 ms
189 ms slowest 5%
Last check
Failed
4 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 4 h 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/brief

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.

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

{
  "coin": "BTC"
}

Example response

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

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

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 -X POST 'https://asistent-crypto.vercel.app/api/x402/data/brief' \
  -H 'content-type: application/json' \
  --data-raw '{"coin":"BTC"}'

# 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/brief' \
  -H 'content-type: application/json' \
  --data-raw '{"coin":"BTC"}' \
  | 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%2Fasistent-crypto.vercel.app%2Fapi%2Fx402%2Fdata%2Fbrief&method=POST
const res = await pay("https://asistent-crypto.vercel.app/api/x402/data/brief", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "coin": "BTC"
  }),
});
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.post(
        "https://asistent-crypto.vercel.app/api/x402/data/brief",
        json={
            "coin": "BTC",
        },
    )
    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
4 h agoHTTP 402 without a parseable x402 challenge40281 ms-
9 h agoHTTP 402 without a parseable x402 challenge402105 ms-
15 h agoHTTP 402 without a parseable x402 challenge402115 ms-
21 h agoHTTP 402 without a parseable x402 challenge40259 ms-
27 h agoHTTP 402 without a parseable x402 challenge40290 ms-
Show 10 older checks
32 h agoHTTP 402 without a parseable x402 challenge40282 ms-
38 h agoHTTP 402 without a parseable x402 challenge40253 ms-
43 h agoHTTP 402 without a parseable x402 challenge40298 ms-
2 days agoHTTP 402 without a parseable x402 challenge40272 ms-
2 days agoHTTP 402 without a parseable x402 challenge40259 ms-
2 days agoHTTP 402 without a parseable x402 challenge402105 ms-
3 days agoHTTP 402 without a parseable x402 challenge402106 ms-
3 days agoHTTP 402 without a parseable x402 challenge40270 ms-
3 days agoHTTP 402 without a parseable x402 challenge402125 ms-
3 days agoHTTP 402 without a parseable x402 challenge40256 ms-