# Mighty - Check Customer Files Before People or AI Act
# Full public reference for LLM indexing and citation
# Last updated: 2026-04-23

Mighty builds an input trust layer for document-heavy workflows. Mighty checks
customer-submitted files, images, PDFs, OCR output, and extracted text before
reviewers, AI tools, OCR, or automation rely on the material.

## Executive Summary

Production workflows increasingly rely on submitted PDFs, images, invoices,
repair estimates, forms, receipts, and text extracted by OCR or document
processing systems. Those materials can influence summaries, review queues,
payment review, claim decisions, or AI-assisted automation.

Mighty is designed to sit before that workflow action. It checks submitted
material and extracted content for suspicious signals such as hidden
instructions, suspicious text layers, unsafe automation instructions, and input
trust issues. The goal is to return a practical workflow decision: allow,
review, or block.

## What Mighty Does Not Claim

Mighty does not claim to replace OCR, claims systems, SIU platforms, or human
reviewers. Mighty does not claim to catch every fraud category or validate the
factual truth of every claim or invoice. The tighter positioning is narrower:
check risky submitted inputs before downstream systems rely on them.

## Sourced Insurance Market Numbers

The public site uses only sourced market numbers:

- The National Association of Insurance Commissioners cites the Coalition
  Against Insurance Fraud estimate that fraud costs businesses and consumers
  $308.6 billion per year across insurance lines.
- NAIC cites a $45 billion property and casualty fraud estimate.
- NAIC cites the FBI estimate that insurance fraud costs the average family
  $400 to $700 per year in premiums.

Source: https://content.naic.org/insurance-topics/insurance-fraud

These numbers size the market problem. They are not claims that Mighty detects
all insurance fraud represented in those estimates.

## Primary Insurance Workflows

### Claims Intake

Use Mighty before submitted claim files reach adjuster review, claim
summaries, OCR, IDP, touchless claims workflows, or AI assistants.

### Repair Estimates, Damage Photos, And Vendor Invoices

Use Mighty before repair estimates, invoices, damage photos, mitigation
documents, or third-party supporting material enters the claim file.

### OCR / IDP Output

Use Mighty after OCR or IDP extraction and before extracted text is passed to an
AI agent, summarizer, rules engine, or workflow tool.

### Adjacent Workflow Expansion

The same input trust pattern can apply to logistics documents, construction
change orders and site photos, financial services onboarding, and enterprise
AI/OCR pipelines. The first wedge remains P&C insurance claims and intake.

## Integration and deployment

Endpoint: `POST /v1/scan`

Supported request styles:

- JSON text scan
- Multipart file upload
- Image scan
- PDF and document scan
- OCR or extracted text inspection

Common response fields:

- `action`: recommended workflow action such as allow, review, or block
- `risk_score`: numeric risk score
- `threats`: detected categories or signals
- `extracted_text`: extracted text when available
- `scan_id`: identifier for correlating results and logs
- `content_type_detected`: detected input type
- `processing_ms`: processing time when available

Sensitive-workflow deployment options:

- Hosted API for fast testing
- Hashed-input mode for teams that do not want raw submitted content stored
- Private-cloud, bring-your-own-cloud, or on-prem discussions for stricter
  deployment requirements

## Example Text Scan

```bash
curl -X POST https://gateway.trymighty.ai/v1/scan \
  -H "X-API-Key: $MIGHTY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "content_type": "text",
    "content": "Text or OCR output to inspect",
    "scan_phase": "input",
    "mode": "secure"
  }'
```

## Example File Scan

```bash
curl -X POST https://gateway.trymighty.ai/v1/scan \
  -H "X-API-Key: $MIGHTY_API_KEY" \
  -F "file=@claim-packet.pdf" \
  -F "scan_phase=input" \
  -F "mode=secure"
```

## Company

- Legal name: Nine Suns Inc
- Brand: Mighty
- Product: Mighty API
- Website: https://trymighty.ai
- Email: hi@trymighty.ai
- Twitter/X: @TryMighty
- LinkedIn: https://www.linkedin.com/company/trymighty

## Pages

- [Home](https://trymighty.ai): Product overview and insurance workflow positioning
- [Use Cases](https://trymighty.ai/use-cases): P&C use cases and adjacent workflow patterns
- [Docs](https://trymighty.ai/docs): Public API examples and response fields
- [Product](https://trymighty.ai/product): Mighty product overview
- [Pricing](https://trymighty.ai/pricing): Plans and usage information
- [Why Mighty](https://trymighty.ai/why-mighty): Technical context and FAQ
- [Security](https://trymighty.ai/security): Data handling and security practices