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 09:02 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.01 USDC
- Networks
- 1
How has the volume on this endpoint moved?
Among the 94 endpoints on globalrules-api.onrender.com, JP calling code is tied 3rd by calls with 47 others.
JP calling code declares an input block that names no parameters.
The output example is a json object with vat, country and updated.
JP calling code drew 4 calls from 2 unique payers in the trailing 30 days.
The last call to JP calling code came 5 days before the snapshot, 2026-10-08.
On Base, JP calling code asks 0.01 USDC per call.
It accounts for 2% of the calls counted across the host.
JP calling code, a GET endpoint on globalrules-api.onrender.com, appears in the Coinbase registry; TOLL's taxonomy puts it in identity.
JP calling code answered the sweep of 2026-10-23 with a valid 402, as at every sweep since 2026-09-11.
Closest in price to JP calling code within identity: icypeas result at vaaya.ai and perp screener at api.nansen.ai.
Among comparable prices in identity, JP calling code sits above 34% of them.
Within identity, 72% of endpoints with counters have fewer calls.
The wallet paid by JP calling code is the payee of 94 endpoints on one host.
The seller's own tags are country-data, vat, crypto-compliance and stablecoin.
JP calling code dropped out of the registry at the pull of 2026-09-27 and was listed again on 2026-09-28.
The price of JP calling code 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-23 06:33 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-23 06:33 UTC | pass | 0 | daily-2026-10-23 |
| 2026-10-22 04:48 UTC | pass | 0 | daily-2026-10-22 |
| 2026-10-21 08:31 UTC | pass | 0 | daily-2026-10-21 |
| 2026-10-20 08:42 UTC | pass | 0 | daily-2026-10-20 |
| 2026-10-19 06:16 UTC | pass | 0 | daily-2026-10-19 |
| 2026-10-18 08:28 UTC | pass | 0 | daily-2026-10-18 |
| 2026-10-17 18:29 UTC | pass | 0 | daily-2026-10-17 |
| 2026-10-16 04:43 UTC | pass | 0 | daily-2026-10-16 |
| 2026-10-15 06:17 UTC | pass | 0 | daily-2026-10-15 |
| 2026-10-14 04:40 UTC | pass | 0 | daily-2026-10-14 |
| 2026-10-13 09:07 UTC | pass | 0 | daily-2026-10-13 |
| 2026-10-12 06:32 UTC | pass | 0 | daily-2026-10-12 |
| 2026-10-11 04:53 UTC | pass | 0 | daily-2026-10-11 |
| 2026-10-10 13:04 UTC | pass | 0 | daily-2026-10-10 |
| 2026-10-09 05:02 UTC | pass | 0 | daily-2026-10-09 |
| 2026-10-08 06:39 UTC | pass | 0 | daily-2026-10-08 |
| 2026-10-07 05:49 UTC | pass | 0 | daily-2026-10-07 |
| 2026-10-06 06:45 UTC | pass | 0 | daily-2026-10-06 |
| 2026-10-05 06:24 UTC | pass | 0 | daily-2026-10-05 |
| 2026-10-04 09:11 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-03 04:25 UTC | pass | 0 | daily-2026-10-03 |
| 2026-10-02 13:36 UTC | pass | 0 | daily-2026-10-02 |
| 2026-10-01 06:47 UTC | pass | 0 | daily-2026-10-01 |
| 2026-09-30 06:04 UTC | pass | 0 | daily-2026-09-30 |
| 2026-09-29 18:25 UTC | pass | 0 | daily-2026-09-29 |
| 2026-09-28 16:53 UTC | pass | 0 | daily-2026-09-28 |
| 2026-09-25 19:59 UTC | pass | 0 | daily-2026-09-25 |
| 2026-09-23 05:40 UTC | pass | 0 | daily-2026-09-23 |
| 2026-09-22 05:50 UTC | pass | 0 | daily-2026-09-22 |
| 2026-09-21 06:13 UTC | pass | 0 | daily-2026-09-21 |
| 2026-09-20 18:52 UTC | pass | 0 | daily-2026-09-20 |
| 2026-09-19 04:14 UTC | pass | 0 | daily-2026-09-19 |
| 2026-09-18 09:59 UTC | pass | 0 | daily-2026-09-18 |
| 2026-09-17 04:12 UTC | pass | 0 | daily-2026-09-17 |
| 2026-09-16 04:13 UTC | pass | 0 | daily-2026-09-16 |
| 2026-09-15 04:11 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 04:09 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 04:09 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 06:24 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 09:52 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 09:02 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, "JP calling code on globalrules-api.onrender.com", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/globalrules-api-onrender-com-api-v1-country-jp-calling-code-22de53/at/2026-10-13T14-08Z. Accessed [access date].
BibTeX
@misc{toll-e-globalrules-api-onrender-com-api-v1-country-jp-calling-code-22de53-2026-10-13T14-08Z,
author = {TOLL},
title = {JP calling code on globalrules-api.onrender.com},
howpublished = {\url{https://tollindex.com/e/globalrules-api-onrender-com-api-v1-country-jp-calling-code-22de53/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.