passabsent from every registry#6 by calls of 5 on this host
0.03 USDC
per call, as the listing declares it on eip155:
Compare with anotherEvery figure as JSONCite this page
the price, as of 2026-09-17 21:21 UTC · method
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- — / — / 100%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-08-18 21:31 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.03 USDC
- Networks
- 1
How big is this endpoint among the ones like it?
No trace is drawn of this endpoint’s own volume. Its counters have changed 1 time across 37 observations, and 3 changes are the fewest this site will draw a trace through, because two points and a guess are not a series. Every observation is in the JSON.
TOLL files asset risk under the "other" category: a POST endpoint on api.hergertsynthora.com, listed in neither registry at the last pull.
asset risk is priced at 0.03 USDC on Base.
Its declared inputs are a json body with the field input.
asset risk returns json; the example shows ok, niche, result and receipt.
The daily sweep got a valid payment challenge from asset risk on 2026-09-17, as at every sweep since 2026-09-11.
Of api.hergertsynthora.com's 5 listings, asset risk ranks 6th by calls.
5% of the host's counted calls go to it.
asset risk drew a single call from a single payer in the trailing 30 days.
The last call to asset risk came 75 days before the snapshot, 2026-08-18.
Closest in price to asset risk within the "other" category: shop buy at x402.clashofcoins.com and horror story at horrorstoryapi.vercel.app.
asset risk is priced above 88% of comparable listings in the "other" category.
The wallet paid by asset risk is the payee of 53 endpoints across 10 hosts.
asset risk was missing from the Coinbase registry at the pull of 2026-09-18, confirmed at the pull of 2026-09-18; that is registry presence, not liveness.
The price of asset risk is declared by 40 other listings in the "other" category too.
Where the sentences above compare this endpoint with others, the comparison is against the index as it stands now, live; the figures above are final.
the payment options, as of 2026-09-17 21:21 UTC · method
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.03 USDC | exact | 0x10800a…427dE0 |
the checks, as of 2026-09-17 06:55 UTC · methodendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-09-17 06:55 UTC | pass | 0 | daily-2026-09-17 |
| 2026-09-16 06:51 UTC | pass | 0 | daily-2026-09-16 |
| 2026-09-15 07:08 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 06:34 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 06:23 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 13:56 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 14:53 UTC | pass | 0 | daily-2026-09-11 |
Presence in a registry, not liveness of the service (method). Newest first.
- absence from Coinbase confirmed, rule v1
- absent from Coinbase at this pull
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-08-18 21:31 UTC · method
The input and output block
{
"input": {
"body": {
"input": "gibraltar"
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"ok": true,
"niche": "asset_risk",
"result": {},
"receipt": {}
}
}
}Cite this page
This endpoint is delisted: the page is frozen at its last observation and its live URL is the stable one. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "asset risk on api.hergertsynthora.com". https://tollindex.com/e/api-hergertsynthora-com-v1-asset-risk-fcb23b. Accessed [access date].
BibTeX
@misc{toll-e-api-hergertsynthora-com-v1-asset-risk-fcb23b-2026-11-01,
author = {TOLL},
title = {asset risk on api.hergertsynthora.com},
howpublished = {\url{https://tollindex.com/e/api-hergertsynthora-com-v1-asset-risk-fcb23b}},
year = {2026},
month = {11},
note = {Frozen at its last observation, 2026-11-01 13:19 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.