passlisted in Coinbasecounted above 0% of Market data
0.137 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
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-09-26 06:02 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.137 USDC
- Networks
- 2
How has the volume on this endpoint moved?
intel, a GET endpoint on mobilitychain.kr, appears in the Coinbase registry; TOLL's taxonomy puts it in market data.
On Base, intel asks 0.137 USDC per call.
Requests carry the query parameters depth and limit.
intel accepts payment on Base and Polygon, 2 options in all, all to one wallet.
intel declares json output without an example.
The daily sweep got a valid payment challenge from intel on 2026-10-30, as at every sweep since 2026-09-11.
intel is the only listed endpoint on mobilitychain.kr.
In the trailing 30 days: one call, one payer.
intel was last called 17 days before the snapshot.
Closest in price to intel within market data: send token at keyring-agent.blockchhub.link and distribution balance exchanges relative at x402.glassnode.com.
intel is near the top of prices in market data; 97% of comparable listings are cheaper.
The payee wallet of intel appears on no other listing.
Seller tags: korea, mobility, supply-chain and ev; seller label: "data".
the payment options, as of 2026-10-13 14:08 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.137 USDC | exact | 0x6cA33C…8d8B69 |
| Coinbase | eip155: | USDC | 0.137 USDC | exact | 0x6cA33C…8d8B69 |
the checks, as of 2026-10-30 09:23 UTC · method · pinnableendpoint answered HTTP 402
bazaar.info.output.example· advisory, does not affect the verdict · an output example is provided (advisory)
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-30 09:23 UTC | pass | 1 | daily-2026-10-30 |
| 2026-10-29 09:04 UTC | pass | 1 | daily-2026-10-29 |
| 2026-10-28 09:26 UTC | pass | 1 | daily-2026-10-28 |
| 2026-10-27 09:09 UTC | pass | 1 | daily-2026-10-27 |
| 2026-10-26 15:38 UTC | pass | 1 | daily-2026-10-26 |
| 2026-10-23 09:22 UTC | pass | 1 | daily-2026-10-23 |
| 2026-10-21 11:52 UTC | pass | 1 | daily-2026-10-21 |
| 2026-10-20 11:29 UTC | pass | 1 | daily-2026-10-20 |
| 2026-10-19 09:09 UTC | pass | 1 | daily-2026-10-19 |
| 2026-10-18 11:00 UTC | pass | 1 | daily-2026-10-18 |
| 2026-10-17 21:25 UTC | pass | 1 | daily-2026-10-17 |
| 2026-10-16 07:11 UTC | pass | 1 | daily-2026-10-16 |
| 2026-10-15 08:59 UTC | pass | 1 | daily-2026-10-15 |
| 2026-10-14 07:00 UTC | pass | 1 | daily-2026-10-14 |
| 2026-10-13 11:46 UTC | pass | 1 | daily-2026-10-13 |
| 2026-10-12 09:07 UTC | pass | 1 | daily-2026-10-12 |
| 2026-10-11 07:50 UTC | pass | 1 | daily-2026-10-11 |
| 2026-10-10 15:57 UTC | pass | 1 | daily-2026-10-10 |
| 2026-10-09 08:41 UTC | pass | 1 | daily-2026-10-09 |
| 2026-10-08 10:10 UTC | pass | 1 | daily-2026-10-08 |
| 2026-10-07 09:33 UTC | pass | 1 | daily-2026-10-07 |
| 2026-10-06 10:19 UTC | pass | 1 | daily-2026-10-06 |
| 2026-10-05 09:14 UTC | pass | 1 | daily-2026-10-05 |
| 2026-10-04 11:31 UTC | pass | 1 | daily-2026-10-04 |
| 2026-10-03 06:11 UTC | pass | 1 | daily-2026-10-03 |
| 2026-10-02 15:23 UTC | pass | 1 | daily-2026-10-02 |
| 2026-10-01 08:14 UTC | pass | 1 | daily-2026-10-01 |
| 2026-09-30 07:35 UTC | pass | 1 | daily-2026-09-30 |
| 2026-09-29 19:49 UTC | pass | 1 | daily-2026-09-29 |
| 2026-09-28 09:12 UTC | pass | 1 | daily-2026-09-28 |
| 2026-09-25 21:20 UTC | pass | 1 | daily-2026-09-25 |
| 2026-09-23 06:53 UTC | pass | 1 | daily-2026-09-23 |
| 2026-09-22 07:05 UTC | pass | 1 | daily-2026-09-22 |
| 2026-09-21 07:28 UTC | pass | 1 | daily-2026-09-21 |
| 2026-09-19 05:29 UTC | pass | 1 | daily-2026-09-19 |
| 2026-09-18 13:56 UTC | pass | 1 | daily-2026-09-18 |
| 2026-09-17 05:23 UTC | pass | 1 | daily-2026-09-17 |
| 2026-09-16 05:22 UTC | pass | 1 | daily-2026-09-16 |
| 2026-09-15 05:39 UTC | pass | 1 | daily-2026-09-15 |
| 2026-09-14 05:12 UTC | pass | 1 | daily-2026-09-14 |
| 2026-09-13 05:08 UTC | pass | 1 | daily-2026-09-13 |
| 2026-09-12 07:24 UTC | pass | 1 | daily-2026-09-12 |
| 2026-09-11 11:08 UTC | pass | 1 | 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-26 06:02 UTC · method · live
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"depth": "brief",
"limit": "10"
}
},
"output": {
"type": "json"
}
}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, "intel on mobilitychain.kr", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/mobilitychain-kr-api-intel-80076a/at/2026-10-13T14-08Z. Accessed [access date].
BibTeX
@misc{toll-e-mobilitychain-kr-api-intel-80076a-2026-10-13T14-08Z,
author = {TOLL},
title = {intel on mobilitychain.kr},
howpublished = {\url{https://tollindex.com/e/mobilitychain-kr-api-intel-80076a/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.