13trust / 100

Analyze Crypto

by TickersFeed in Onchain & crypto

x402 APIFailing, checked 3 h ago

AI-generated cryptocurrency analysis for any coin or token — momentum read, key risks, market context, and outlook as structured JSON. Use for: crypto research brief, token due diligence, momentum check, automated coin analysis. $0.02 USDC per call.

GET
https://api.tickersfeed.net/analyze/crypto/:symbol
Price
$0.02
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

How to call it

GET https://api.tickersfeed.net/analyze/crypto/:symbol

Each call costs $0.02 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://api.tickersfeed.net/analyze/crypto/:symbol?symbol=AAPL

Parameters

ParameterTypeRequiredDescription
symbolstringNoCrypto symbol (e.g. BTC, ETH, SOL)

Example response

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

{
  "analysis": {
    "momentum": "Strong upward",
    "outlook": "Bullish continuation",
    "risk_level": "Medium",
    "summary": "Bitcoin is trading at $98,000..."
  },
  "symbol": "BTC"
}

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

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://api.tickersfeed.net/analyze/crypto/:symbol?symbol=AAPL'

# 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://api.tickersfeed.net/analyze/crypto/:symbol?symbol=AAPL' \
  | 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.02 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.02" });
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.02 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.tickersfeed.net%2Fanalyze%2Fcrypto%2F%3Asymbol
const res = await pay("https://api.tickersfeed.net/analyze/crypto/:symbol?symbol=AAPL");
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.02 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.02"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://api.tickersfeed.net/analyze/crypto/:symbol?symbol=AAPL")
    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 404404587 ms-
8 h agoExpected HTTP 402, got 404404446 ms-
12 h agoExpected HTTP 402, got 404404460 ms-
17 h agoExpected HTTP 402, got 404404132 ms-
21 h agoExpected HTTP 402, got 404404441 ms-
Show 10 older checks
26 h agoExpected HTTP 402, got 404404391 ms-
30 h agoExpected HTTP 402, got 404404557 ms-
34 h agoExpected HTTP 402, got 404404411 ms-
38 h agoExpected HTTP 402, got 404404408 ms-
42 h agoExpected HTTP 402, got 404404503 ms-
46 h agoExpected HTTP 402, got 404404376 ms-
2 days agoExpected HTTP 402, got 404404362 ms-
2 days agoExpected HTTP 402, got 404404405 ms-
2 days agoExpected HTTP 402, got 404404442 ms-
3 days agoExpected HTTP 402, got 404404146 ms-