By use case
For AI SOC agents
Agents act in seconds — and amplify every bad input they are handed. Intelligence they can verify, not just consume.
Agent-ready — machine-priced, machine-readable, machine-verifiable.
The problem
An agent cannot tell that APT41 and Wicked Panda are the same actor
A human analyst hits a naming collision and works around it. An agent does not — it confidently joins the wrong two things, or fails to join the right ones, and carries that error into whatever it does next. The same applies to a stale indicator, an unscored feed, or an answer with no source behind it.
Autonomy raises the cost of bad input. What an agent needs is not more data but data whose provenance and freshness it can check.
What answers it
The building blocks that solve it
RST Threat Library
Aliases resolved into stable, linked actor profiles — so the join an agent makes is the right one.
RST Report Hub
Every report as a STIX 2.1 graph with typed objects and relationships, not prose an agent has to parse.
RST CTI Assistant
Source-referenced answers over MCP, so an agent can follow the citation rather than trust the sentence.
Enrichment at investigation time
When the verdict isn’t in the feed yet
Half of what an agent meets during an incident has never been scored by anyone — a domain registered this morning, an IP nobody has reported. The agent still has to reason about it. The RST Enrichment API gives it observable facts to reason from, every one of them callable as a tool over MCP.
Registration reality
Registrar, creation and expiry dates, nameservers, contact structure.
A domain created three days ago and one registered in 2009 deserve opposite default assumptions — age alone is often the strongest single signal an agent has.
Certificate and its neighbours
Issuer, validity window and the full SAN list for an IP:port.
The SAN list is the pivot: one certificate routinely names every sibling host in the same operation, turning a single IP into the whole cluster.
The kit’s fingerprint
Favicon metadata and the image itself for any target.
Operators re-deploy kits without changing the icon. A favicon match across otherwise unrelated domains is one of the cheapest ways to find the rest of a campaign.
What the page actually serves
Raw body markup and the JavaScript extracted from it.
This is where a credential harvester gives itself away — the form target, the exfil endpoint, the obfuscated loader — none of which is visible from the URL.
Visual confirmation
A PNG of the live page, captured as first, full or last.
last follows the redirect chain to where a victim actually lands — the brand being impersonated is usually invisible at the first hop.
Is it really a C2?
Cobalt Strike beacon scan against a suspected IP:port or URL.
Turns “this IP looks suspicious” into a configuration pulled off the listener itself — evidence an agent can attach to a finding rather than a hunch it has to hedge.
All of it is one MCP surface. The same server also exposes ioc_lookup for a scored verdict, noise_lookup and noise_batch_lookup to discard known-good before spending a single enrichment call, report_get_stix for the reporting behind a finding, and threat_object_get for the actor or malware profile it belongs to. An agent chains them in one session — and every answer it produces can be traced back to the call that produced it.
Give your agents something they can check.
Our scoring is published and every answer carries its source. Start a trial and point your agents at it.