13trust / 100

Price

by FTSO Yggdrassil in Onchain & crypto

x402 APIFailing, checked 3 h ago

Real-time cryptocurrency price from the FTSO Yggdrassil value provider

GET
https://api.ftso-yggdrassil.com/v1/price/:symbol
Price
$0.002
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://api.ftso-yggdrassil.com/v1/price/:symbol

Each call costs $0.002 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.ftso-yggdrassil.com/v1/price/:symbol

Example response

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

{
  "currency": "USD",
  "price": {
    "BTC": 76850.0127909
  },
  "timestamp": "2026-09-17T12:24:47.597Z"
}

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

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://api.ftso-yggdrassil.com/v1/price/:symbol'

# 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.ftso-yggdrassil.com/v1/price/:symbol' \
  | 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.002 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.002" });
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.002 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.ftso-yggdrassil.com%2Fv1%2Fprice%2F%3Asymbol
const res = await pay("https://api.ftso-yggdrassil.com/v1/price/:symbol");
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.002 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.002"})
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.ftso-yggdrassil.com/v1/price/:symbol")
    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 404404644 ms-
8 h agoExpected HTTP 402, got 404404641 ms-
13 h agoExpected HTTP 402, got 404404549 ms-
18 h agoExpected HTTP 402, got 404404564 ms-
23 h agoExpected HTTP 402, got 404404538 ms-
Show 10 older checks
28 h agoExpected HTTP 402, got 404404619 ms-
32 h agoExpected HTTP 402, got 404404591 ms-
37 h agoExpected HTTP 402, got 404404540 ms-
42 h agoExpected HTTP 402, got 404404629 ms-
47 h agoExpected HTTP 402, got 404404662 ms-
2 days agoExpected HTTP 402, got 404404609 ms-
2 days agoExpected HTTP 402, got 404404551 ms-
3 days agoExpected HTTP 402, got 404404563 ms-
3 days agoExpected HTTP 402, got 404404677 ms-
3 days agoExpected HTTP 402, got 404404537 ms-