passlisted in Coinbase#1 by calls of 11 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
- 3
- Unique payers, trailing 30 days
- 3
- Last called
- 2026-09-12 17:10 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.01 USDC
- Networks
- 1
How has the volume on this endpoint moved?
ot-intel-api.onrender.com lists 11 endpoints; ot ioc is tied 1st by calls with 1 other.
The listing describes the request as the query parameters type and value.
ot ioc returns json; the example shows ioc, isp, tor_node, freshness, reputation, pulse_count and 2 others.
The registry's counters give ot ioc 3 calls and 3 unique payers over 30 days, every call from a different payer.
The last call to ot ioc came 3 days before the snapshot, 2026-09-12.
ot ioc is priced at 0.01 USDC on Base.
20% of the host's counted calls go to it.
TOLL files ot ioc under the "other" category: a GET endpoint on ot-intel-api.onrender.com, listed in the Coinbase registry.
ot ioc answered the sweep of 2026-09-15 with a valid 402, as at every sweep since 2026-09-11.
Closest in price to ot ioc within the "other" category: authorize at api.safe4.ai and business time at chrono.schemasure.com.
ot ioc is priced above 64% of comparable listings in the "other" category.
ot ioc out-counts 77% of the 2,777 endpoints in the "other" category that carry counters.
The wallet paid by ot ioc is the payee of 11 endpoints on one host.
The price of ot ioc is declared by 428 other listings in the "other" category too.
the payment options, as of 2026-09-15 16:57 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.01 USDC | exact | 0x188819…7C767B |
the checks, as of 2026-09-15 06:52 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-15 06:52 UTC | pass | 0 | daily-2026-09-15 |
| 2026-09-14 06:20 UTC | pass | 0 | daily-2026-09-14 |
| 2026-09-13 06:10 UTC | pass | 0 | daily-2026-09-13 |
| 2026-09-12 08:28 UTC | pass | 0 | daily-2026-09-12 |
| 2026-09-11 14:36 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-12 17:10 UTC · method · live
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"type": "ip",
"value": "185.220.101.45"
}
},
"output": {
"type": "json",
"example": {
"ioc": {
"type": "ip",
"value": "185.220.101.45"
},
"isp": "Tor Project",
"tor_node": true,
"freshness": "2025-05-22T10:00:00.000Z",
"reputation": -2,
"pulse_count": 50,
"country_code": "DE",
"data_sources": [
"AlienVault-OTX",
"AbuseIPDB",
"DeepSeek-CTI-Analysis"
],
"ics_association": {
"confidence": "high",
"ics_tags_found": [
"ics",
"scada",
"modbus"
],
"campaign_context": "IP observed in VOLTZITE reconnaissance activity against US electric utilities.",
"known_threat_actor": "VOLTZITE",
"associated_with_ics_campaign": true
},
"total_abuse_reports": 142,
"abuse_confidence_score": 87
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-09-15 16:57 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "ot ioc on ot-intel-api.onrender.com", snapshot of 2026-09-15 16:57 UTC. https://tollindex.com/e/ot-intel-api-onrender-com-ot-ioc-e7e748/at/2026-09-15T16-57Z. Accessed [access date].
BibTeX
@misc{toll-e-ot-intel-api-onrender-com-ot-ioc-e7e748-2026-09-15T16-57Z,
author = {TOLL},
title = {ot ioc on ot-intel-api.onrender.com},
howpublished = {\url{https://tollindex.com/e/ot-intel-api-onrender-com-ot-ioc-e7e748/at/2026-09-15T16-57Z}},
year = {2026},
month = {9},
note = {Pinned view of the snapshot of 2026-09-15 16:57 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.