passabsent from every registry#2 by calls of 4 on this host
0.005 USDC
per call, as the listing declares it on eip155:
Compare with anotherEvery figure as JSONCite this page
the price, as of 2026-09-22 04:53 UTC · method
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- — / 100% / 100%
- Calls, trailing 30 days
- 5
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-08-23 05:09 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.005 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 2 times across 53 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.
open-pay.jp serves jpyc transfers, a GET endpoint that TOLL places in identity, listed in neither registry at the last pull.
Per call, jpyc transfers declares 0.005 USDC on Base.
Its declared inputs are the query parameters chain and limit.
jpyc transfers returns json; the example shows mode, chain, items, token, notice, chainId and 2 others.
jpyc transfers answered the sweep of 2026-09-22 with a valid 402, as at every sweep since 2026-09-11.
open-pay.jp lists 4 endpoints; jpyc transfers is tied 2nd by calls with 1 other.
jpyc transfers takes 25% of the calls counted across open-pay.jp.
Over 30 days: 5 calls, one payer.
jpyc transfers was last called 51 days before the snapshot.
Closest in price to jpyc transfers within identity: my usage at agent402.tools and screen at sanctions.cyberwarex.com.
Among comparable prices in identity, jpyc transfers sits above 21% of them.
Across identity, 2,150 endpoints carry counters and jpyc transfers out-counts 82% of them.
12 listed endpoints across 2 hosts pay to the same wallet.
The seller's tags on jpyc transfers are jpyc, token-transfers, wallet-activity and payment-reconciliation.
jpyc transfers was missing from the Coinbase registry at the pull of 2026-09-22, confirmed at the pull of 2026-09-22; that is registry presence, not liveness.
The price of jpyc transfers is declared by 228 other listings in identity 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-22 04:53 UTC · method
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.005 USDC | exact | 0x52d490…a3cA81 |
the checks, as of 2026-09-22 07:08 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-22 07:08 UTC | pass | 0 | daily-2026-09-22 |
| 2026-09-21 07:30 UTC | pass | 0 | daily-2026-09-21 |
| 2026-09-19 05:32 UTC | pass | 0 | daily-2026-09-19 |
| 2026-09-18 13:59 UTC | pass | 0 | daily-2026-09-18 |
| 2026-09-17 05:25 UTC | pass | 0 | daily-2026-09-17 |
| 2026-09-16 05:25 UTC | pass | 0 | daily-2026-09-16 |
| 2026-09-15 05:42 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 05:15 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 05:11 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 07:27 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 11:12 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-23 05:09 UTC · method
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"chain": "polygon",
"limit": "20"
}
},
"output": {
"type": "json",
"example": {
"mode": "snapshot",
"chain": "polygon",
"items": [
{
"to": "0xB808AF91bDc577BFb3f9c91470f3286dd076e5C1",
"from": "0x13FE0A65D0aA7641B44D1AF17ECE4b41cEbB1880",
"value": "600000000000000000000000",
"txHash": "0xcae3af66168483e5905709cfc8f7cc0162f5234b9c456905df8ab4917b6f8c39",
"logIndex": 286,
"blockNumber": "92387695",
"valueFormatted": "600000"
}
],
"token": {
"symbol": "JPYC",
"decimals": 18
},
"notice": "onchain-facts-only",
"chainId": 137,
"hasMore": false,
"toBlock": "92387745",
"contract": "0xE7C3D8C9a439feDe00D2600032D5dB0Be71C3c29",
"termsUrl": "https://open-pay.jp/en/terms",
"fromBlock": "92385945",
"truncated": false,
"nextCursor": "92387695:286",
"generatedAt": "2026-08-21T04:30:45.340Z",
"schemaVersion": "2.2"
}
}
}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, "jpyc transfers on open-pay.jp". https://tollindex.com/e/open-pay-jp-api-paid-usdc-jpyc-transfers-838233. Accessed [access date].
BibTeX
@misc{toll-e-open-pay-jp-api-paid-usdc-jpyc-transfers-838233-2026-10-13,
author = {TOLL},
title = {jpyc transfers on open-pay.jp},
howpublished = {\url{https://tollindex.com/e/open-pay-jp-api-paid-usdc-jpyc-transfers-838233}},
year = {2026},
month = {10},
note = {Frozen at its last observation, 2026-10-13 14:08 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.