---
title: "Use Cases"
description: "Where Citadel sits before a mortgage funds, or an insurer binds or pays."
---

# Use Cases

Where Citadel sits before a mortgage funds, or an insurer binds or pays.

Source URL: https://trymighty.ai/docs/use-cases

Start with the file the customer sent. Ask where that file becomes a funding, bind, or payout decision.

Citadel use case map: scan the customer file before funding, payout, storage, or automation acts on it.

For setting recipes, see [Choose Scan Settings](/docs/concepts/configs).

## Use case map

| Use case | What can go wrong | Where Citadel sits | Suggested settings |
| --- | --- | --- | --- |
| Mortgage income and assets | Altered paystubs, W-2s, bank statements, or tax returns clear review and come back as a buyback. | Before underwriting trusts the file, and before you fund. | [`content_type=document` or `pdf`](/docs/concepts/configs#content-types), `focus=steg`, `profile=strict` for high value. |
| Insurance underwriting | Generated or edited attachments used to qualify a policy. | Before the packet is treated as true and the policy binds. | [`data_sensitivity=tolerant`](/docs/concepts/configs#mode-profile-and-data-sensitivity), `focus=steg` for structured docs, `focus=all` for image or PDF evidence. |
| Claims intake | Altered photos, estimates, or invoices. Hidden instructions in the packet. | Before storage, extraction, routing, or adjuster automation. | [`data_sensitivity=tolerant`](/docs/concepts/configs#mode-profile-and-data-sensitivity), `profile=strict` for high value. Use `focus=steg` for structured documents and `focus=all` for known image or PDF evidence. |
| Damage photo review | Damage added, erased, or generated to match the loss. | Before claim, repair, or payment decisions. | [`content_type=image`, `focus=all`](/docs/concepts/configs#focus-modes-without-jargon), `mode=comprehensive` for deep review. |
| Invoice and estimate review | Line items and totals altered. Fabricated charges. | Before extraction, approval, or payment. | [`content_type=pdf` or `document`](/docs/concepts/configs#content-types), `data_sensitivity=tolerant`. |
| Text already read from a file | Hidden instructions become trusted fields. | Scan the original file, then the extracted text with the same `scan_group_id`. | [`focus=steg`, `data_sensitivity=tolerant`](/docs/concepts/configs#start-with-the-thing-you-are-about-to-trust). |
| User-generated uploads | Hidden instructions, sensitive data, unsupported file size. | Before permanent storage, indexing, or sharing. | [`content_type=auto`, `mode=secure`, `focus=steg`](/docs/concepts/configs#safe-default), async for large evidence. |
| Review assistant | A summary carries a tampered source forward as trusted. | Before showing generated summaries or recommendations. | [`scan_phase=output`, `data_sensitivity=tolerant`](/docs/concepts/configs#output-inspection). |
| Batch intake | Many records hide risky items and lose traceability. | Per item before batch automation writes state. | One `session_id` per batch, one `scan_group_id` per item. |
| Chat or agent tools | Hidden instructions in a prompt, tool result, or retrieved file. | Before the model call, and before tool output enters context. | [`mode=secure`, `focus=steg`](/docs/concepts/configs#start-with-the-thing-you-are-about-to-trust), `profile=ai_safety` for public output. |
| Audio intake | Transcripts can carry unsafe instructions or disputed statements. | Scan transcript text today. Audio scanning is closed beta. | [`content_type=text`](/docs/concepts/configs#content-types) for the transcript, same session as the source audio. |

## Why scan here

A bad file can become a trusted income figure, a bind decision, a payout, or an automated summary.

- Income docs: catch the alteration before you fund.
- Underwriting packets: catch the fake attachment before you bind.
- Claims photos and estimates: catch the edit before you pay.
- Extracted text: catch hidden instructions before they become a field.
- Model output: catch a summary that treats a tampered source as clean.

## Value by workflow

| Workflow | Value |
| --- | --- |
| Mortgage | Flag an altered paystub, W-2, or bank statement before funding. |
| Insurance underwriting | Flag a generated or edited attachment before bind. |
| Claims | Flag a doctored photo, estimate, or invoice before payout. |
| Extracted text | Keep hidden instructions out of workflow fields. |
| Review queues | Give reviewers IDs, risk fields, the original file, derived text, and scan history. |
| Agents | Keep untrusted tool output out of model context. |

## Build order

1. Start with the workflow that moves money: income docs before funding, or claim evidence before payout.
2. Add `POST /v1/scan` before that step.
3. Store IDs and action.
4. Route `ALLOW`, `WARN`, `BLOCK`, `indeterminate`, and `pending`.
5. Scan derived output with the same `scan_group_id`.
6. Add review metrics so you can tune tolerance later.

## AI-agent prompt

### Choose Citadel use cases

```text
Find the Citadel use cases in this product.

For each workflow, identify:
- The customer file or derived text.
- Whether the next step is funding, bind, payout, storage, or a model call.
- The right content_type, scan_phase, mode, focus, profile, and data_sensitivity.
- Where scan_group_id and session_id should be stored.
- How ALLOW, WARN, BLOCK, indeterminate, and pending are routed.

Prioritize:
- income and asset documents before funding
- new-business attachments before bind
- damage photos, estimates, and invoices before payout
- text already read from those files
- model summaries of those files
- agent tool output
- batch intake

Acceptance criteria:
- Every high-risk file has a server-side scan.
- Every derived output scan reuses the correct scan_group_id.
- Review wording says Citadel flags suspicious evidence, not that it proves fraud.
```