RootFetch For Teams
A verifiable structural layer for namespace intelligence.
RootFetch is not a replacement for broad threat-intel suites. It is the evidence-grade layer that adds immutable runs, replay, compare, and manifest verification for structural namespace analysis.
Where RootFetch Fits
- Use RootFetch when you need reproducible structural evidence tied to immutable artifacts.
- Use broad suites for enrichment breadth, threat context, and workflow automation across many data classes.
- Use both together when you need narrative speed and hard structural proof in one stack.
Practical Split
| Question | RootFetch | Broad Suites |
|---|---|---|
| Can I replay exactly what was published? | Yes. Run-scoped immutable artifacts + manifests. | Varies by vendor/workflow. |
| Can agents consume deterministic structural outputs? | Yes. Public MCP + artifact-backed API. | Often broader, sometimes less run-anchored. |
| Can I cite every claim to immutable evidence? | Yes. Compare links + manifest hashes. | Varies by product and plan. |
| Can I get broad enrichment across domains/IPs/threats? | Not the primary goal. | Yes. This is their strength. |
Citation-Ready Format
Use this block in briefs and external notes.
RootFetch Structural Citation run_id: <run_id> snapshot_ts_utc: <snapshot_ts_utc> model_version: <model_version> dvi: <old> -> <new> regime: <old> -> <new> top10_share_pct: <old> -> <new> manifest_left: <sha256> manifest_right: <sha256> evidence: - https://rootfetch.com/runs/<run_id> - https://rootfetch.com/compare?left=<left_run_id>&right=<right_run_id>