> ## Documentation Index
> Fetch the complete documentation index at: https://docs.factagora.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> How DeepStamp protects your content with invisible, structure-based watermarking

<Note>
  **DeepStamp is the product name; the API paths still say `fingerprint`.** Endpoints are `/api/v1/fingerprint/embed` and `/api/v1/fingerprint/detect`, and responses return `fingerprint_id`. There is no `/api/v1/deepstamp/*` endpoint.
</Note>

## What is DeepStamp?

DeepStamp is Factagora's content provenance API. It solves a fundamental problem: **how do you prove that a piece of content originated from you, even after it's been rewritten, paraphrased, or translated?**

Traditional text-matching tools fail when content is rephrased. DeepStamp works differently, it analyzes the *causal structure* of your content (who did what, when, and why) and embeds an invisible watermark based on that structure. Even if every word is changed, the underlying structure remains detectable.

## How it works

<Steps>
  <Step title="Embed">
    You send your content to `/fingerprint/embed`. The API extracts a **Temporal Knowledge Graph (TKG)**: entities, timelines, causal relations, and argument chains, then embeds an invisible zero-width Unicode watermark seeded by that structure. You get back the watermarked content to distribute.
  </Step>

  <Step title="Detect">
    When you encounter suspicious content, send it to `/fingerprint/detect`. The API runs two independent checks:

    1. **Watermark check**: extracts hidden bits and correlates against stored fingerprints (near-certain match)
    2. **TKG matching**: compares the causal structure using fuzzy word-level matching (catches paraphrases)
  </Step>

  <Step title="Audit">
    Each match comes with a full breakdown: which entities, time anchors, and causal patterns were shared. This is your evidence trail, auditable and explainable.
  </Step>
</Steps>

## Key capabilities

<CardGroup cols={2}>
  <Card title="Paraphrase-resistant" icon="arrows-rotate">
    Word-level fuzzy matching means "EU enacts AI Act" matches "European Union passed AI Act regulation", no exact string match required.
  </Card>

  <Card title="Dual-layer detection" icon="layer-group">
    Watermark correlation (cryptographic) + TKG Jaccard (semantic) run independently. Both firing simultaneously makes coincidental overlap statistically implausible.
  </Card>

  <Card title="Content-type aware" icon="sliders">
    Scoring weights are automatically tuned: legal documents emphasize causal structure (0.6), news emphasizes entities (0.5), reports balance all three signals.
  </Card>

  <Card title="Auditable evidence" icon="file-lines">
    Every match includes the exact overlap lists, shared entities, timelines, and causal triples, so you can explain *why* two articles matched.
  </Card>
</CardGroup>

## What's in a TKG snapshot?

The Temporal Knowledge Graph extracted from your content contains four layers:

| Layer            | Example                                  | Purpose                                 |
| ---------------- | ---------------------------------------- | --------------------------------------- |
| **Entities**     | `Bank of Korea`, `Interest rate`         | Who and what are involved               |
| **Timeseries**   | `2024-03-15`                             | When events occurred                    |
| **Relations**    | `Bank of Korea → raises → Interest rate` | What happened (cause and effect)        |
| **Argument map** | Premise → Evidence → Conclusion chains   | Why it happened (macro-level reasoning) |

The argument map is what makes DeepStamp uniquely robust. Two articles about the same event will share entities and dates, but the argument structure, *why* the rate was raised, *what evidence* supports the claim, is the hardest to change in a paraphrase.

## Use cases

* **News agencies**: Detect when your articles are republished without attribution
* **Legal teams**: Prove content provenance in licensing disputes
* **Research organizations**: Track how your findings are cited and reused
* **Content platforms**: Automatically flag potential content reuse at scale

## Next steps

<CardGroup cols={2}>
  <Card title="Embed & Detect walkthrough" icon="play" href="/guides/factagora/fingerprint/embed-and-detect">
    Step-by-step guide with code examples.
  </Card>

  <Card title="Best practices" icon="lightbulb" href="/api-reference/best-practices/fingerprint">
    Production tips for scoring, filtering, and auditing.
  </Card>
</CardGroup>