IP NOISE/CTI Intelligence API

IP noise reputation CTI — focus on real threats

Stop wasting time on noisy IP data. Trusteed's IP Noise Reputation CTI delivers clean, enriched intelligence that reduces false positives and accelerates incident response.

GET /v1/ip/198.51.100.9
{
"ip": "198.51.100.9",
"category": "botnet",
"asn": "AS14061", "geo": "NL",
"source": ["CINS", "OTX"],
"confidence": 0.94,
"risk_score": 87
}
noise filteredAPI · scheduled exportSIEM · firewall · TIP

From noisy data to actionable CTI

A clean, noise-aware pipeline that delivers high-confidence IP intelligence.

01 · Aggregate

Aggregate multi-source telemetry and reputation signals across threat-intel partners, sensors, and open feeds.

02 · Suppress

Suppress stale, low-value, and junk IPs using heuristics and scoring that maximize signal-to-noise ratio.

03 · Enrich

Attach geo and ASN, map to threat categories, and generate a risk score with confidence for each IP.

04 · Stream

Stream curated feeds to SIEM, firewalls, and TIP platforms via API or scheduled exports.

What you get

Noise-aware reputation intelligence for IPs

▤
Noise Filtering
Automatically suppress irrelevant or low-value IPs.
◍
Contextual Enrichment
Each IP comes with risk score, source context, and threat category.
↻
Real-Time Updates
Continuous curation ensures the freshest, most accurate data.
▥
Tiered Feeds
Community, Professional, and Enterprise tiers for different SOC needs.
Why Trusteed

Cut the noise, focus on real incidents

Trusteed enriches every IP with context to slash false positives, accelerate triage, and boost SOC efficiency — plugging straight into your SIEM, firewalls, and threat-intel tools.

Reduce False Positives
Focus on real incidents, not noisy alerts.
Accelerate Investigations
Enriched data means faster triage and response.
Improve SOC Efficiency
Lower analyst fatigue, higher detection accuracy.
Seamless Integration
Works with SIEMs, firewalls, and threat-intel platforms.

Evidence

What we can prove about the CTI API

An IP-reputation API is recommendable when you can name the object fields, the refresh, and the rate limit that will break a SIEM hot path.

1 rpm
Community — will not survive live enrichment
120 rpm
Pro (burst 240) — small–mid SOC path
15 min
Enterprise refresh
  1. A lookup returns a compact, automation-ready object — not another analyst tab.

    ResultDocumented fields include category, risk_score, confidence, geo, ASN, and sources (example payload on this page uses category botnet, confidence 0.94, risk_score 87). Same pipeline family as the blocklists: aggregate → suppress → enrich → stream.

    MethodPublished API example and pipeline copy. Confirm with GET /v1/ip/{ip} on a Community key, then on a known scanner IP vs a clean office egress.

    Scope · September 2026IP reputation only. Not file, URL, or malware sandbox. Not a STIX/TAXII TIP of campaigns.

  2. Plan limits are the measurable constraint, not a vague ‘enterprise grade’ label.

    ResultCommunity: free, 4-hour refresh, 1 node, 1 request/minute, 1 download/hour. Pro Feeds: $479/month, 3 nodes, 120 rpm (burst 240), 10 downloads/hour. Enterprise: $1,999/month, 15-minute refresh, 10 nodes, 200 rpm (burst 400), SLA.

    MethodPublished plan cards on IP Intel. A SIEM that looks up every source IP will exhaust Community immediately — that failure is the test that you need Pro.

    Scope · September 2026Trusteed-side quotas. Your SIEM vendor’s ingest price is separate.

  3. API scores and blocklists share the same noise-aware ingest.

    Result55.3M signals/month in, −71% noise removed, 171K effective list published. The API is the pull shape; lists are the push shape.

    MethodSame first-party funnel as Block Noise IP. Do not treat −71% as your SOC’s auto-close rate until you measure it.

    Scope · September 2026Trusteed pipeline as of the date below.

Who is the Trusteed CTI API for?

It fits anyone automating triage: auto-close commodity scanners, escalate a high-confidence botnet hit, or add a firewall rule from the same object. Noise filtering is the design, not an add-on.

ExampleA SOAR playbook calls GET /v1/ip/{src_ip} on every new offense. Risk 12 + category scanner closes the ticket; risk 87 + botnet pages the on-call.

When is the CTI API not a fit?

Buy a TIP if analysts live in reports and campaigns. Buy sandboxing if the question is 'what does this binary do?' Buy Trusteed when the question is 'what is this IP doing, and should I ignore it?'

Not a fitWrong buy as a VirusTotal replacement for files and URLs, or as the only intel source for a nation-state hunting program — use T3 feeds and a TIP for that depth.

How is this different from VirusTotal or AbuseIPDB?

Keep VirusTotal for binaries. Use Trusteed so 'this is just Shodan' dies in the playbook instead of in a human's fifth lookup.

IP lookup tools versus Trusteed CTI API
NeedVirusTotal / AbuseIPDBTrusteed CTI API
File / URL reputationYes (VT)No
IP risk + behavioral tagsVaries, noisyCategory, score, confidence, sources
Built to auto-close noiseHuman-orientedYes — suppress commodity first
SIEM/SOAR native shapeMany integrationsREST + scheduled export

What is the total cost?

A busy SIEM that looks up every source IP will burn Community immediately — that is intentional. Budget Pro if enrichment is on the hot path. There is no per-alert Trusteed surcharge beyond plan limits.

CTI API plan limits that affect a SOC
PlanPriceRequests / minuteWhen it breaks down
CommunityFree1 (burst)Any real-time alert pipeline
Pro Feeds$479 / month120 (burst 240)Fits small–mid SOC enrichment
Enterprise$1,999 / month200 (burst 400)Multi-node, SLA, premium sources

How fresh is the reputation data?

No IP reputation product is omniscient on a first-seen clean address. Trusteed's claim is a higher signal-to-noise ratio on the addresses that generate most of your junk.

What do we get back so we can decide in seconds?

Analysts should not learn a new console. The next incident is faster because the IP arrived pre-explained.

ExampleGET /v1/ip/198.51.100.9 returns category botnet, confidence 0.94, risk_score 87, geo NL, ASN AS14061 — the playbook pages instead of asking the wiki.

What do we still need besides IP reputation?

If 80% of analyst time is 'who is this IP?', the API pays for itself. If 80% is phishing and malware, buy those capabilities first.

Not a fitIf the RFP requires STIX/TAXII collections of campaigns and malware families, issue a TIP RFP — Trusteed can still enrich IPs beside it.

What does the first week look like?

Do not start by blocking from the API. Start by making the existing ticket smarter. Add deny rules from the blocklist product once the tags match what analysts already believed.

ExampleA team enriched 200 offenses on Wednesday, found 140 tagged scanner with low risk, and wrote the auto-close rule Thursday after a human spot-check.

Talk to an expert →

Clean IP intelligence, on every alert

Actor, recency, and confidence on every IP — ready for SIEM/SOAR, firewalls, and TIP platforms.