passlisted in Coinbase#3 by calls of 94 on this host
0.01 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
- 4
- Unique payers, trailing 30 days
- 2
- Last called
- 2026-10-08 08:43 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.01 USDC
- Networks
- 1
How has the volume on this endpoint moved?
Of globalrules-api.onrender.com's 94 listings, GB banking hours ranks tied 3rd by calls with 47 others.
Its declared input names no parameters.
A response from GB banking hours, as declared, includes vat, country and updated.
The registry's counters give GB banking hours 4 calls and 2 unique payers over 30 days.
GB banking hours was last called 5 days before the snapshot.
It is priced at 0.01 USDC on Base.
GB banking hours takes 2% of the calls counted across globalrules-api.onrender.com.
globalrules-api.onrender.com serves GB banking hours, a GET endpoint that TOLL places in identity, listed in the Coinbase registry.
GB banking hours answered the sweep of 2026-10-27 with a valid 402, as at every sweep since 2026-09-11.
Closest in price to GB banking hours within identity: screening match at api.relaystation.ai and icypeas result at vaaya.ai.
GB banking hours is priced above 34% of comparable listings in identity.
Within identity, 72% of endpoints with counters have fewer calls.
The wallet paid by GB banking hours is the payee of 94 endpoints on one host.
The seller's tags on GB banking hours are country-data, vat, crypto-compliance and stablecoin.
GB banking hours dropped out of the registry at the pull of 2026-09-27 and was listed again on 2026-09-28.
The price of GB banking hours is declared by 707 other listings in identity too.
the payment options, as of 2026-10-13 14:08 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.01 USDC | exact | 0x22c24D…83F8e2 |
the checks, as of 2026-10-27 09:45 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-10-27 09:45 UTC | pass | 0 | daily-2026-10-27 |
| 2026-10-26 16:09 UTC | pass | 0 | daily-2026-10-26 |
| 2026-10-23 10:03 UTC | pass | 0 | daily-2026-10-23 |
| 2026-10-21 12:30 UTC | pass | 0 | daily-2026-10-21 |
| 2026-10-20 12:11 UTC | pass | 0 | daily-2026-10-20 |
| 2026-10-19 09:49 UTC | pass | 0 | daily-2026-10-19 |
| 2026-10-18 11:37 UTC | pass | 0 | daily-2026-10-18 |
| 2026-10-16 07:46 UTC | pass | 0 | daily-2026-10-16 |
| 2026-10-15 09:37 UTC | pass | 0 | daily-2026-10-15 |
| 2026-10-14 07:35 UTC | pass | 0 | daily-2026-10-14 |
| 2026-10-13 12:22 UTC | pass | 0 | daily-2026-10-13 |
| 2026-10-12 09:47 UTC | pass | 0 | daily-2026-10-12 |
| 2026-10-11 08:25 UTC | pass | 0 | daily-2026-10-11 |
| 2026-10-10 16:34 UTC | pass | 0 | daily-2026-10-10 |
| 2026-10-09 09:32 UTC | pass | 0 | daily-2026-10-09 |
| 2026-10-08 10:56 UTC | pass | 0 | daily-2026-10-08 |
| 2026-10-07 10:23 UTC | pass | 0 | daily-2026-10-07 |
| 2026-10-06 11:06 UTC | pass | 0 | daily-2026-10-06 |
| 2026-10-05 09:52 UTC | pass | 0 | daily-2026-10-05 |
| 2026-10-04 12:02 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-03 06:34 UTC | pass | 0 | daily-2026-10-03 |
| 2026-10-02 15:46 UTC | pass | 0 | daily-2026-10-02 |
| 2026-10-01 08:34 UTC | pass | 0 | daily-2026-10-01 |
| 2026-09-30 07:57 UTC | pass | 0 | daily-2026-09-30 |
| 2026-09-29 20:09 UTC | pass | 0 | daily-2026-09-29 |
| 2026-09-28 17:13 UTC | pass | 0 | daily-2026-09-28 |
| 2026-09-23 07:10 UTC | pass | 0 | daily-2026-09-23 |
| 2026-09-22 07:23 UTC | pass | 0 | daily-2026-09-22 |
| 2026-09-21 07:45 UTC | pass | 0 | daily-2026-09-21 |
| 2026-09-19 05:46 UTC | pass | 0 | daily-2026-09-19 |
| 2026-09-18 14:19 UTC | pass | 0 | daily-2026-09-18 |
| 2026-09-17 05:38 UTC | pass | 0 | daily-2026-09-17 |
| 2026-09-16 05:38 UTC | pass | 0 | daily-2026-09-16 |
| 2026-09-15 05:55 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 05:27 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 05:22 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 07:38 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 11:27 UTC | pass | 0 | daily-2026-09-11 |
Presence in a registry, not liveness of the service (method). Newest first.
- back in Coinbase
- 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-10-08 08:43 UTC · method · live
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"queryParams": {}
},
"output": {
"type": "json",
"example": {
"vat": {
"name": "Consumption Tax",
"reduced": 8,
"standard": 10
},
"country": "JP",
"updated": "2026-10-05"
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-10-13 14:08 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "GB banking hours on globalrules-api.onrender.com", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/globalrules-api-onrender-com-api-v1-country-gb-banking-hours-960760/at/2026-10-13T14-08Z. Accessed [access date].
BibTeX
@misc{toll-e-globalrules-api-onrender-com-api-v1-country-gb-banking-hours-960760-2026-10-13T14-08Z,
author = {TOLL},
title = {GB banking hours on globalrules-api.onrender.com},
howpublished = {\url{https://tollindex.com/e/globalrules-api-onrender-com-api-v1-country-gb-banking-hours-960760/at/2026-10-13T14-08Z}},
year = {2026},
month = {10},
note = {Pinned view of the snapshot of 2026-10-13 14:08 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.