bitcoin fees derived
api.hergertsynthora.comMarket dataderived
POST https://api.hergertsynthora.com/v1/bitcoin-fees
failabsent from every registry#3 by calls of 9 on this host
0.01 USDC
per call, as the listing declares it on eip155:
Compare with anotherEvery figure as JSONCite this page
the price, as of 2026-10-06 06:18 UTC · method
- Validation state
- fail
- Uptime, 7 / 30 / 90 days
- 83% / 95% / 95%
- Calls, trailing 30 days
- 4
- Unique payers, trailing 30 days
- 3
- Last called
- 2026-09-28 04:57 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.01 USDC
- Networks
- 1
How has the volume on this endpoint moved?
The sweep of 2026-10-06 found bitcoin fees answering HTTP 410 instead of a payment challenge.
At api.hergertsynthora.com, bitcoin fees takes POST requests, is listed in neither registry at the last pull, and falls under market data by TOLL's rules.
bitcoin fees is priced at 0.01 USDC on Base.
The request to bitcoin fees is a json body with the field protocol.
The declared response carries ok, niche, result and receipt.
bitcoin fees drew 4 calls from 3 unique payers in the trailing 30 days.
The last call to bitcoin fees came 9 days before the snapshot, 2026-09-28.
bitcoin fees shares api.hergertsynthora.com with 8 other listed endpoints and is tied 3rd by calls with 1 other.
bitcoin fees takes 18% of the calls counted across api.hergertsynthora.com.
Among comparable prices in market data, bitcoin fees sits above 32% of them.
Closest in price to bitcoin fees within market data: address current balance at api.nansen.ai and token safety at api.deepnets.ai.
The wallet paid by bitcoin fees is the payee of 31 endpoints across 2 hosts.
Across market data, 9,879 endpoints carry counters and bitcoin fees out-counts 81% of them.
Seller tags: bitcoin, fees, mempool and realtime.
bitcoin fees was missing from the Coinbase registry at the pull of 2026-10-06, confirmed at the pull of 2026-10-07; that is registry presence, not liveness.
The price of bitcoin fees is declared by 4,398 other listings in market data 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-10-06 06:18 UTC · method
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.01 USDC | exact | 0xEf879B…245e06 |
the checks, as of 2026-10-06 16:41 UTC · methodendpoint answered HTTP 410
returns_402· an unauthenticated request gets HTTP 402
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-06 16:41 UTC | fail | 1 | daily-2026-10-06 |
| 2026-10-05 13:03 UTC | pass | 0 | daily-2026-10-05 |
| 2026-10-04 15:26 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-03 08:29 UTC | pass | 0 | daily-2026-10-03 |
| 2026-10-02 17:34 UTC | pass | 0 | daily-2026-10-02 |
| 2026-10-01 10:11 UTC | pass | 0 | daily-2026-10-01 |
| 2026-09-30 09:37 UTC | pass | 0 | daily-2026-09-30 |
| 2026-09-29 21:44 UTC | pass | 0 | daily-2026-09-29 |
| 2026-09-23 08:35 UTC | pass | 0 | daily-2026-09-23 |
| 2026-09-22 08:48 UTC | pass | 0 | daily-2026-09-22 |
| 2026-09-21 09:08 UTC | pass | 0 | daily-2026-09-21 |
| 2026-09-19 07:05 UTC | pass | 0 | daily-2026-09-19 |
| 2026-09-17 06:57 UTC | pass | 0 | daily-2026-09-17 |
| 2026-09-16 06:53 UTC | pass | 0 | daily-2026-09-16 |
| 2026-09-15 07:09 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 06:35 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 06:24 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 13:58 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 14:55 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-09-28 04:57 UTC · method
The input and output block
{
"input": {
"body": {
"protocol": "aave"
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"schema": {
"type": "object",
"required": [
"ok",
"niche"
],
"properties": {
"ok": {
"type": "boolean"
},
"error": {
"type": "string"
},
"niche": {
"type": "string"
},
"result": {
"type": "object",
"properties": {
"red": {
"type": "string"
},
"fees": {
"type": "object"
},
"error": {
"type": "string"
},
"source": {
"type": "string"
},
"unidad": {
"type": "string"
},
"as_of_utc": {
"type": "string"
},
"block_height": {
"type": "number"
}
}
},
"receipt": {
"type": "object"
}
}
},
"example": {
"ok": true,
"niche": "bitcoin_fees",
"result": {},
"receipt": {
"alg": "ed25519"
}
}
}
}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, "bitcoin fees on api.hergertsynthora.com". https://tollindex.com/e/api-hergertsynthora-com-v1-bitcoin-fees-ff2773. Accessed [access date].
BibTeX
@misc{toll-e-api-hergertsynthora-com-v1-bitcoin-fees-ff2773-2026-10-07,
author = {TOLL},
title = {bitcoin fees on api.hergertsynthora.com},
howpublished = {\url{https://tollindex.com/e/api-hergertsynthora-com-v1-bitcoin-fees-ff2773}},
year = {2026},
month = {10},
note = {Frozen at its last observation, 2026-10-07 05:57 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.