xbrl fee war derived
api.cryptoetfsentinel.comMarket dataderived
GET https://api.cryptoetfsentinel.com/v1/xbrl/fee-war
passlisted in Coinbase#7 by calls of 22 on this host
0.1 USDC
per call, as the listing declares it on eip155:
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 100% / 100% / 100%
- Calls, trailing 30 days
- 2
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-09-06 08:43 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.1 USDC
- Networks
- 2
How big is this endpoint among the ones like it?
No trace is drawn of this endpoint’s own volume. Its counters have changed 2 times across 33 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.
Among the 22 endpoints on api.cryptoetfsentinel.com, xbrl fee war is tied 7th by calls with 15 others.
Requests carry the query parameter crypto.
xbrl fee war returns json; the example shows data and meta.
One payer accounts for all 2 calls to xbrl fee war over 30 days.
Its last counted call came 11 days before the snapshot.
A call to xbrl fee war costs 0.1 USDC on Base, as declared.
It accounts for 4% of the calls counted across the host.
For xbrl fee war the listing declares 2 accepts on Base and Solana, to 2 different wallets.
xbrl fee war is a GET endpoint at api.cryptoetfsentinel.com, listed in the Coinbase registry and filed by TOLL under market data.
xbrl fee war answered the sweep of 2026-09-16 with a valid 402, as at every sweep since 2026-09-11.
Closest in price to xbrl fee war within market data: forecast btc at kronossignals.com and analyze at svm402.com.
Among comparable prices in market data, xbrl fee war sits above 87% of them.
The wallet paid by xbrl fee war is the payee of 22 endpoints on one host.
The price of xbrl fee war is declared by 274 other listings in market data too.
the payment options, as of 2026-09-16 21:17 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.1 USDC | exact | 0x169Bf4…1683d1 |
| Coinbase | solana: | USDC | 0.1 USDC | exact | Ezzbt3d3…KdpMxk |
the checks, as of 2026-09-16 06:19 UTC · method · pinnableendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-09-16 06:19 UTC | pass | 0 | daily-2026-09-16 |
| 2026-09-15 06:35 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 06:04 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 05:56 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 08:13 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 12:30 UTC | pass | 0 | daily-2026-09-11 |
Presence in a registry, not liveness of the service (method). Newest first.
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-09-06 08:43 UTC · method · live
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"crypto": "bitcoin"
}
},
"output": {
"type": "json",
"example": {
"data": [
{
"cik": "0001980994",
"name": "iShares Bitcoin Trust",
"ticker": "IBIT",
"fee_bps": 25,
"fee_pct": "0.25%"
}
],
"meta": {
"total": 1
}
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-09-16 21:17 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "xbrl fee war on api.cryptoetfsentinel.com", snapshot of 2026-09-16 21:17 UTC. https://tollindex.com/e/api-cryptoetfsentinel-com-v1-xbrl-fee-war-cf4101/at/2026-09-16T21-17Z. Accessed [access date].
BibTeX
@misc{toll-e-api-cryptoetfsentinel-com-v1-xbrl-fee-war-cf4101-2026-09-16T21-17Z,
author = {TOLL},
title = {xbrl fee war on api.cryptoetfsentinel.com},
howpublished = {\url{https://tollindex.com/e/api-cryptoetfsentinel-com-v1-xbrl-fee-war-cf4101/at/2026-09-16T21-17Z}},
year = {2026},
month = {9},
note = {Pinned view of the snapshot of 2026-09-16 21:17 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.