80trust / 100

Stablecoin Supply

by SYNTHORA in Onchain & crypto

x402 APIPassing, checked 11 min ago

SYNTHORA stablecoin-supply: circulating USD supply, price and peg deviation in basis points for the top stablecoins (USDT, USDC, DAI...), with a depeg alert flag above 50 bps. Optional symbol filter. Free source: stablecoins.llama.fi (DefiLlama), no API key, timestamped.

POST
https://api.hergertsynthora.com/v1/stablecoin-supply
Price
$0.01
per call in USDC
Uptime
100%
last 30 days
Response time
239 ms
424 ms slowest 5%
Last check
Passed
11 min ago, next in 16 min

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed

How to call it

POST https://api.hergertsynthora.com/v1/stablecoin-supply

Each call costs $0.01 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://api.hergertsynthora.com/v1/stablecoin-supply
content-type: application/json

{
  "input": "USDC"
}

Parameters

ParameterTypeRequiredDescription
inputstringNoSYNTHORA stablecoin-supply: circulating USD supply, price and peg deviation in basis points for the top stablecoins (USDT, USDC, DAI...), with a depeg alert flag above 50 bps. Optional symbol filter.

Example response

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

{
  "niche": "stablecoin_supply",
  "ok": true,
  "receipt": {
    "alg": "ed25519"
  },
  "result": {}
}

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

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://api.hergertsynthora.com/v1/stablecoin-supply' \
  -H 'content-type: application/json' \
  --data-raw '{"input":"USDC"}'

# 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://api.hergertsynthora.com/v1/stablecoin-supply' \
  -H 'content-type: application/json' \
  --data-raw '{"input":"USDC"}' \
  | 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.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
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.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.hergertsynthora.com%2Fv1%2Fstablecoin-supply&method=POST
const res = await pay("https://api.hergertsynthora.com/v1/stablecoin-supply", {
  method: "POST",
  headers: { "content-type": "application/json" },
  body: JSON.stringify({
    "input": "USDC"
  }),
});
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.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.post(
        "https://api.hergertsynthora.com/v1/stablecoin-supply",
        json={
            "input": "USDC",
        },
    )
    print(res.status_code, res.text)

Security scan

1 finding

  • Payment address changed recently in payment
    Payment address changed from 0xEf879BFD6C4AccB8F795136de90246e1EC245e06 to 0x6D9F318463168fF637b50E5b9a21392e97c7c167

Recent checks

WhenResultHTTPTimePrice
11 min agoPassed402217 ms$0.01
4 h agoPassed402326 ms$0.01
9 h agoPassed402197 ms$0.01
13 h agoPassed402294 ms$0.01
17 h agoPassed402258 ms$0.01
Show 10 older checks
21 h agoPassed402304 ms$0.01
25 h agoPassed402210 ms$0.01
29 h agoPassed402219 ms$0.01
33 h agoPassed402341 ms$0.01
37 h agoPassed402367 ms$0.01
41 h agoPassed402329 ms$0.01
45 h agoPassed402239 ms$0.01
2 days agoPassed402231 ms$0.01
2 days agoPassed4021.7 s$0.01
2 days agoPassed402216 ms$0.01

History

12 Oct 2026Payment address changed from 0xEf879BFD6C4AccB8F795136de90246e1EC245e06 to 0x6D9F318463168fF637b50E5b9a21392e97c7c167