How Vein Explorer works
Vein Explorer helps you turn a theme into a concrete map: what the product depends on, where risk concentrates, and which public tickers are exposed — fast enough to use in real research loops.
What is Vein Explorer?
Vein Explorer is an interactive supply-chain and trade explorer. Enter any product, component, or service and Vein builds a dependency tree with criticality, chokepoint flags, and tradeable tickers — then compounds results into Vein Graph for second‑order exposure.
Problems it solves
- Hidden single points of failure in complex products
- Unclear upstream exposure for investors and analysts
- Slow manual decomposition for procurement and operations teams
- Difficulty monitoring portfolio overlap with supply-chain risk
- Scattered research that is hard to share across a team
How a trace works
1. Start with a query
Start on Explore with a product or theme (e.g. "lithium", "data center", "HBM memory"). If you want a guided starting point, use sector templates or the Sector Explorer.
2. Review the root breakdown
You’ll see the first decomposition: children, criticality, and early tickers. Use the list + graph views to spot obvious clusters and missing layers.
3. Expand nodes
Expand the most critical branches until you reach tradable layers (public companies, commodities, ETFs). Use chokepoint + rank panels to focus where disruption matters.
4. Act on insights
From any node, screen equities (cap tier + sector), add symbols to your watchlist, and run Exposure for second‑order beneficiaries. Share links or export results when you have a narrative.
Use cases
Investor / analyst
Find market exposure behind a theme or product
- Start with Explore (or Sector Explorer if you want curated anchors)
- Expand the highest‑criticality branches until you see tradable nodes
- Use the node Equity screener to filter to small/micro caps or a target sector
- Open Exposure to find second‑order beneficiaries via Vein Graph
- Add candidates to your watchlist and set alerts for chokepoint keywords
Operator / procurement
Map supplier and material dependencies
- Trace your SKU, subsystem, or supplier category
- Expand until you can name the constrained inputs and chokepoints
- Use evidence badges to separate “AI‑asserted” from corroborated relationships
- Export JSON/CSV for internal briefs and keep a share link as the living source
Team lead
Collaborate on supply-chain research
- Create a workspace and centralize traces for your theme coverage
- Comment on nodes where assumptions or supplier names need review
- Compare traces side by side to reconcile different decompositions
- Standardize alerts and share “starter traces” with your team
Developer
Automate traces in your pipeline
- Create an API key on the API page
- POST /v1/public/traces with your query
- Expand nodes programmatically
- Store results and periodically re-run to catch supply-chain drift