# BRAINIAC Insurance Claim Analyzer

> BRAINIAC Insurance Claim Analyzer is a paid API for AI agents from www.brainiac.software, paid per call via x402, $0.1/call, status unknown (last checked 2026-11-15).

Analyzes an insurance policy document against a described incident to screen coverage, extract relevant clauses, and produce an evidence checklist and timeline for a claim.

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/claims/analyze?utm_source=zero.xyz
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/brainiac-insurance-claim-analyzer-384d5c93
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_yHfg5zQjvM0-IdQocMeD_

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability brainiac-insurance-claim-analyzer-384d5c93 -d '<json body>'
```

Example prompt: Can you analyze my homeowner's insurance policy (attached as PDF) against a property damage incident that happened on 2024-11-15 and tell me which clauses apply, what my coverage status looks like, what evidence I should gather, and when my notice deadline is?

## When to prefer this

Choose this endpoint when you need to cross-reference a specific insurance policy document against a concrete incident to understand coverage applicability, extract actionable clauses, and prepare a claim — especially when timing (notice deadlines) and evidence checklists matter. Prefer this over generic document Q&A tools when the output must be structured (clauses, timelines, screening status) and claim-specific rather than free-form.

## Known failure modes

- Scanned or image-only PDFs may result in incomplete text extraction, noted in limitations array
- Missing or malformed incidentDate (must be a valid calendar date) causes validation failure
- fileBase64 payload exceeding ~20 MB limit will be rejected
- Ambiguous or very short incident descriptions may yield low confidence scores and sparse clause matches
- Policy documents in non-standard formats may parse incorrectly, reducing clause extraction accuracy

## How this service works

Pay-per-call APIs for AI agents: OFAC sanctions screening, compliance checks, token security, and Base chain data via x402. No account. Fixed USDC price. MCP-ready.

## Output

Returns a JSON object containing: parsed policy clauses with headings, categories, page numbers, and confidence scores; a coverage status (e.g. WARN/OK); an evidence preparation checklist tied to the incident type; a claim timeline with the incident date, notice due date, and any inferred statutory deadlines; and a preliminary screening status with disclaimers. Also includes a source hash of the analyzed document and any extraction limitations noted.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "filename": {
   "type": "string",
   "default": "policy.pdf",
   "maxLength": 240,
   "minLength": 1
  },
  "fileBase64": {
   "type": "string",
   "maxLength": 20971520,
   "minLength": 1
  },
  "description": {
   "type": "string",
   "maxLength": 12000,
   "minLength": 1
  },
  "incidentDate": {
   "type": "string",
   "format": "date",
   "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$"
  },
  "incidentType": {
   "type": "string",
   "maxLength": 100,
   "minLength": 1
  },
  "knownDocuments": {
   "type": "array",
   "items": {
    "type": "string",
    "maxLength": 240
   },
   "default": [],
   "maxItems": 100
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "policy": {
   "status": "WARN",
   "clauses": [
    {
     "id": "clause-1",
     "page": 1,
     "excerpt": "Example clause excerpt",
     "heading": "Coverage",
     "category": "coverage",
     "confidence": 0.61
    }
   ],
   "parsedAt": "2026-10-29T12:00:00.000Z",
   "confidence": 0.61,
   "sourceHash": "0123456789abcdef0123456789abcdef0123456789abcdef0123456789abcdef",
   "limitations": [
    "Text extraction may omit scanned or image-only policy content."
   ],
   "noticePeriodDays": null
  },
  "evidence": {
   "checklist": [],
   "disclaimer": "General claim preparation suggestion.",
   "incidentType": "property damage"
  },
  "timeline": {
   "incidentDate": "2026-10-20",
   "noticeDueDate": null,
   "noticePeriodDays": null,
   "statutoryDeadlinesInferred": false
  },
  "screening": {
   "status": "WARN",
   "checklist": [],
   "disclaimer": "Preliminary text match only.",
   "screeningOnly": true,
   "noticePeriodDays": null
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-insurance-claim-analyzer-384d5c93/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from www.brainiac.software](https://www.zero.xyz/host/www.brainiac.software/llms.txt)
