# ViceWire Documentation

## Docs

- [Overview](https://vicewire.ai/docs/Core-Concepts-Overview.md): The main concepts behind ViceWire's event model, novelty tracking, relevance signals, geography, business-surface mapping, and claim-status interpretation.
- [Why ViceWire](https://vicewire.ai/docs/Why-ViceWire.md): Why a bespoke company-specific event structure instead of generic headline feeds, sentiment, or manual tagging.
- [Business Impact Mapping](https://vicewire.ai/docs/business-impact-mapping.md): How ViceWire maps each event to the part of a security that is most directly implicated.
- [Directional Layers](https://vicewire.ai/docs/directional-layers.md): How ViceWire attaches directional interpretation and FinBERT scoring to each event object.
- [Documentation Scope](https://vicewire.ai/docs/documentation-scope.md): What the public ViceWire docs cover, what remains gated, and how to use the docs in evaluation.
- [Entity Relevance Signals](https://vicewire.ai/docs/entity-relevance-signals.md): How ViceWire records whether the company is central to the article or only mentioned in passing.
- [Event Model Overview](https://vicewire.ai/docs/event-model.md): How ViceWire turns one article into one or more company-specific structured event objects.
- [Example: Legal Event](https://vicewire.ai/docs/example-legal-event.md)
- [Example: One Article, Three Event Families](https://vicewire.ai/docs/example-product-partner-compeition-event.md)
- [Example Overview](https://vicewire.ai/docs/example-workflows.md): Worked example payloads showing how ViceWire structures real articles into event-level output.
- [Facts vs Rumors](https://vicewire.ai/docs/facts-vs-rumors.md): How ViceWire distinguishes officially confirmed claims from sourced reporting and rumor-level speculation.
- [Geography Data](https://vicewire.ai/docs/geography-data.md): How ViceWire captures geography when place is materially relevant to the event described in the article.
- [How To Evaluate](https://vicewire.ai/docs/how-to-evaluate.md): How to assess ViceWire today using the public docs, worked examples, and whether trial access is the right next step.
- [Novelty Tracking](https://vicewire.ai/docs/novelty-tracking.md): How ViceWire incorporates novelty tracking into its workflow.
- [Overview](https://vicewire.ai/docs/overview.md): ViceWire is an alt-data vendor that turns publicly available web and mainstream media into per-ticker, machine-readable features for investment and trading workflows. It extracts company-specific events, maps them to the relevant business surface, tracks novelty, scores tone and directional implicat…
- [Pipeline & Workflow](https://vicewire.ai/docs/pipeline-and-workflow.md): How ViceWire moves from a raw article to a structured event payload.
- [QA, Evaluations & Limitations](https://vicewire.ai/docs/qa-evaluations-and-limitations.md): How ViceWire evaluates output quality, where review occurs, and the main limitations of the current system.
- [Trial Access](https://vicewire.ai/docs/trial-access.md): How to evaluate ViceWire beyond the public documentation.

## OpenAPI Specs

- [openapi](https://vicewire.ai/docs/api-reference/openapi.json)