Choose Scan Settings

Mighty inspects anything before your product trusts it: user input, generated output, uploads, OCR text, image evidence, PDF evidence, office documents, and agent tool output.

Start with the thing your product is about to trust. Then choose the settings that match that story.

For definitions of focus, AI edits, steganography, prompt injection, and related terms, see the glossary.

Start With The Thing You Are About To Trust

Use this table first. It shows the setting combinations that should be copied into real integrations.

Safe Default

If you are unsure, start here:

{
  "content_type": "auto",
  "scan_phase": "input",
  "mode": "secure",
  "focus": "steg",
  "profile": "balanced",
  "data_sensitivity": "standard"
}

This says: "A user or upstream system submitted something, Mighty should inspect it with the normal production path, and normal product policy should decide what happens next."

Change the defaults only when the workflow needs it:

• Use data_sensitivity=tolerant when the text normally contains names, addresses, claim IDs, policy numbers, invoice lines, or contact details.
• Use profile=ai_safety and data_sensitivity=strict for public AI output.
• Use focus=ai, focus=edits, or focus=all only for supported image/PDF evidence paths.
• Use mode=comprehensive and async=true for high-value image/PDF review where waiting is acceptable.

Input Inspection

Input inspection means the material came from a user, customer, claimant, vendor, partner, upload, browser, or upstream system.

Examples:

For browser or API uploads, see Scan File Uploads. For visual evidence, see Damage Photo AI Fraud Review.

Output Inspection

Output inspection means your system generated the material: a model answer, OCR text, extraction result, AI summary, agent tool result, generated recommendation, or public response.

Scan output before users, models, tools, or workflow automation act on it.

{
  "content": "Generated answer shown to a user",
  "content_type": "text",
  "scan_phase": "output",
  "mode": "secure",
  "focus": "steg",
  "profile": "ai_safety",
  "data_sensitivity": "strict"
}

Use the scan_group_id from the related input scan. That keeps the prompt, upload, OCR output, model answer, and review record connected.

For generated responses, see Scan Model Output. For multi-step evidence chains, see Sessions And Scan Groups.

Focus Modes Without Jargon

focus answers: what kind of risk or evidence should Mighty prioritize?

Default value: steg. Focused image paths bill 4 SCU per image. focus=all bills 10 SCU per image unit. Deprecated aliases still exist: standard maps to steg, and both maps to all.

Office and structured documents currently support steg only. For content_type=document, focus=ai, focus=edits, focus=all, and deprecated focus=both return 400 with code=unsupported_focus_for_content_type.

For the technical compatibility table, see POST /v1/scan focus compatibility.

When focus=ai Is Useful

Ask: "Is this visual evidence likely generated, AI-edited, reposted, or missing useful provenance?"

Use focus=ai when authenticity is the main question and you already know the material is image/PDF evidence.

curl -X POST https://gateway.trymighty.ai/v1/scan \
  -H "Authorization: Bearer $MIGHTY_API_KEY" \
  -F "file=@./receipt-photo.jpg" \
  -F "content_type=image" \
  -F "scan_phase=input" \
  -F "mode=secure" \
  -F "focus=ai" \
  -F "profile=strict"

This is review evidence, not proof of fraud. Use focus=all instead when the same image/PDF may also contain hidden instructions or unsafe text.

When focus=edits Is Useful

Ask: "What changed, and where does the submitted image look manipulated?"

The best path is to send a source image with reference_file.

curl -X POST https://gateway.trymighty.ai/v1/scan \
  -H "Authorization: Bearer $MIGHTY_API_KEY" \
  -F "file=@./submitted-damage-photo.jpg" \
  -F "reference_file=@./original-damage-photo.jpg" \
  -F "content_type=image" \
  -F "scan_phase=input" \
  -F "mode=secure" \
  -F "focus=edits" \
  -F "profile=strict"

Without a reference image, Mighty can only return conservative hints. Use focus=all when you also need hidden-content or AI-authenticity review.

Mode, Profile, And Data Sensitivity

These settings are separate from focus.

Mode is not tolerance. mode changes how deep the inspection goes. profile, data_sensitivity, and your routing policy decide how strict the product is after Mighty returns a result. See Modes And Tolerance.

Content Types

content_type answers: what kind of thing is this?

If a PDF contains images, still send it as pdf. If an OCR system extracted text from a PDF, scan that extracted text as content_type=text and reuse the same scan_group_id.

IDs And Review

Store these fields so your reviewers and logs can explain what happened:

Route results in product language:

Common Wrong Choices

• Using focus=all for normal text, OCR text, or model output. Use focus=steg.
• Using focus=ai as a fraud verdict. Mighty flags review evidence; your business process decides fraud.
• Using focus=edits without explaining reference vs no-reference review. Use reference_file when you have the source image.
• Using focus=ai, focus=edits, or focus=all on content_type=document. Structured documents support focus=steg only.
• Using mode=fast because a workflow should be tolerant. Use data_sensitivity=tolerant for expected PII.
• Scanning only OCR text when the original file is available. Scan the file first, then scan extracted text with the same scan_group_id.