IOC enrichment with ICS campaign context
IOC enrichment with ICS campaign context. Pass ?value=1.2.3.4&type=ip or type=domain. Queries AlienVault OTX, AbuseIPDB, and DeepSeek CTI for OT campaign association. Returns verdict on whether the IOC is linked to ICS-targeting campaigns.
by ot-intel-api.onrender.com · discovered, not yet claimed by its owner · updated 2026-10-08
Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.
What it does
IOC enrichment with ICS campaign context. Pass ?value=1.2.3.4&type=ip or type=domain. Queries AlienVault OTX, AbuseIPDB, and DeepSeek CTI for OT campaign association. Returns verdict on whether the IOC is linked to ICS-targeting campaigns.
Tags: bazaar
Call contract
- Method
- GET
- Input
- query parameters
- Output
- json
- Last paid call
- 2026-10-08
{
"type": "ip",
"value": "185.220.101.45"
}{
"abuse_confidence_score": 87,
"country_code": "DE",
"data_sources": [
"AlienVault-OTX",
"AbuseIPDB",
"DeepSeek-CTI-Analysis"
],
"freshness": "2025-05-22T10:00:00.000Z",
"ics_association": {
"associated_with_ics_campaign": true,
"campaign_context": "IP observed in VOLTZITE reconnaissance activity against US electric utilities.",
"confidence": "high",
"ics_tags_found": [
"ics",
"scada",
"modbus"
],
"known_threat_actor": "VOLTZITE"
},
"ioc": {
"type": "ip",
"value": "185.220.101.45"
},
"isp": "Tor Project",
"pulse_count": 50,
"reputation": -2,
"tor_node": true,
"total_abuse_reports": 142
}Use with an agent
- Discover. Agents find this listing with
GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP toolsearch_resources, or/discovery/resources. - Inspect. Fetch
/resources/41183.jsonfor the price and payment options. - Pay. Call
GET https://ot-intel-api.onrender.com/ot/ioc. The provider answers402with its payment requirements. An x402 client signs one of the options below and retries withPAYMENT-SIGNATURE. - Execute. The provider returns
200with the data. Agent Bazaar is not in the request path and never sees your payment.
For humans
You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.
Pricing & payment
- Price
- $0.01 / request
- Protocol
- x402 v2
- Auth
- No account or API key. Pay per request.
- Networks
- Base
- Demand
- 2 calls · 2 unique payers in 30d (public x402 Bazaar data)
x402 payment requirements
| Scheme | Network | Asset | Amount | Pay to | Timeout |
|---|---|---|---|---|---|
| exact | Base eip155:8453 | USDC | $0.01 | 0x1888192FAc6a69e4cd7d078eC4bCf6F24f7C767B | 300s |
accepts[] (raw JSON)
[
{
"scheme": "exact",
"network": "eip155:8453",
"payTo": "0x1888192FAc6a69e4cd7d078eC4bCf6F24f7C767B",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "10000",
"amountUsd": 0.01,
"maxTimeoutSeconds": 300
}
]Schemas
Output schema (JSON Schema)
{
"properties": {
"example": {
"type": "object"
},
"type": {
"type": "string"
}
},
"required": [
"type"
],
"type": "object"
}Example shape — generated from the schema, not a captured live response
{
"example": {},
"type": "string"
}Examples
curl "https://ot-intel-api.onrender.com/ot/ioc"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paidconst res = await fetch("https://ot-intel-api.onrender.com/ot/ioc");
if (res.status === 402) {
const { accepts } = await res.json();
// pay one of accepts[] via an x402 client, then retry with the payment header
}import httpx
res = httpx.get("https://ot-intel-api.onrender.com/ot/ioc")
if res.status_code == 402:
accepts = res.json()["accepts"]
# pay one of accepts[] via an x402 client, then retry with the payment headerDetails
- Provider
- ot-intel-api.onrender.com
- Endpoint
- https://ot-intel-api.onrender.com/ot/ioc
- Machine-readable
/resources/41183.json