Skip to main content

1. Embed a watermark

Send your content to /fingerprint/embed to extract the TKG and embed the watermark.

Response

Distribute watermarked_content, not the original. The watermarked version looks identical to the original but contains invisible zero-width characters that enable watermark-based detection.
Store fingerprint_id alongside your internal article ID. You’ll need it for re-scoring and reporting.

2. Detect content reuse

When you encounter content that looks like it might originate from your article, even if it’s been rewritten, send it to /fingerprint/detect.

Response

Notice that the query text is completely rewritten, “ECB hiked rates 25bp” vs “European Central Bank raised interest rates by 25 basis points”, yet the API matched it with 87% confidence by comparing the underlying causal structure.

3. Detect with watermark (highest confidence)

If the watermarked version of your content was copied with the invisible characters intact, the watermark layer fires for near-certain provenance:
When watermark_match: true, the match is cryptographically verified, the exact watermarked content (or a portion of it) was used.

4. Tune detection with custom weights

Different content types benefit from different scoring emphasis. Override the defaults when needed:
The weights used are always echoed back in meta.weights so you can verify what was applied.

5. Re-score an existing fingerprint

To periodically check if new content matches a fingerprint you already embedded, pass the fingerprint_id directly:
This reuses the stored TKG snapshot without re-extracting, making it faster and ideal for scheduled monitoring.

Summary