Snapshots

What ERM3 returns when you ask it to render.

Every decomposition the API computes can come back as JSON or as a printable institutional artifact. The two examples below were generated end-to-end from single API calls — no manual chart-building, no post-processing.

API output — institutional artifacts

From one API call to a research-desk one-pager.

Same decomposition engine, two output formats — JSON for code, printable PDF for memos. Single-name due diligence (NVDA) and fund fit (AGTHX) below, both generated from one call each.

Build from the API

NVDA

Single-stock due diligence snapshot

RiskModels API output: cumulative returns, ERM3 factor bridge, peer residual analytics, and hedgeable risk layers.

AGTHX

Mutual fund fit snapshot

Funds pipeline output: 5-year NAV attribution, top holdings risk contribution, active risk mix, and summary profile.

Run it on your book

Same engine, your positions.

Both snapshots above are rendered from the same call developers use programmatically. Hit the API from code, the CLI, or an agent — the JSON powers your pipeline and the same call can render a one-pager for your IC.

Get API Key View API Docs Read the research