# BRAINIAC Insurance Claim Dispute Letter Drafter

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

Generates a formatted insurance claim dispute or initial claim letter from structured claim data, including coverage validity scores and matched exclusions.

## Facts

- Endpoint: POST https://www.brainiac.software/api/v1/claims/dispute-draft?utm_source=zero.xyz
- Price: $0.04/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/brainiac-insurance-claim-dispute-letter-drafter-1958dda9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ALESzMYAy2kIaYQrLLlcZ

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-dispute-letter-drafter-1958dda9 -d '<json body>'
```

Example prompt: Draft an insurance dispute letter for North Pier Contracting disputing claim CLM-100 on policy GL-2041. The incident was a river flood on 2026-03-02 for $12,500. The facts are: river flood water entered the warehouse after a storm and a forklift struck a rack. The coverage review shows a validity score of 75 and 35% denial risk, with one matched exclusion — flood, surface water, or overflow of any body of water. Purpose is dispute.

## When to prefer this

Use this endpoint when an AI agent needs to produce a professional, formatted insurance claim or dispute letter from structured claim data — especially when matched policy exclusions, claim validity scores, and denial risk percentages are already available from a prior coverage analysis step. Prefer this over generic LLM text generation when you need a structured, compliance-aware letter that explicitly incorporates coverage review metadata and is explicitly marked as a human-review draft before sending.

## Known failure modes

- Missing required fields (facts, claimant, insurer, etc.) result in validation errors
- purpose enum value not 'claim' or 'dispute' causes rejection
- incident_date not matching YYYY-MM-DD pattern returns format error
- matched_exclusions array items missing required 'clause' or 'basis' fields cause schema errors
- amount exceeding maximum value limit causes rejection
- Payment failure via x402 results in 402 response with no letter generated

## 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 fully formatted, human-review-ready dispute or claim letter addressed to the insurer's claims department, including all claim details, the narrative facts, coverage validity and denial risk context, matched exclusions, and a request for written justification. Also returns a completeness_score (0–100) indicating how complete the generated letter is based on supplied inputs.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "facts": {
   "type": "string",
   "maxLength": 4000,
   "minLength": 1
  },
  "amount": {
   "type": "number",
   "maximum": 1000000000000,
   "minimum": 0
  },
  "insurer": {
   "type": "string",
   "maxLength": 160,
   "minLength": 2
  },
  "purpose": {
   "enum": [
    "claim",
    "dispute"
   ],
   "type": "string"
  },
  "claimant": {
   "type": "string",
   "maxLength": 160,
   "minLength": 2
  },
  "claim_number": {
   "type": "string",
   "maxLength": 80,
   "minLength": 1
  },
  "incident_date": {
   "type": "string",
   "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
  },
  "policy_number": {
   "type": "string",
   "maxLength": 80,
   "minLength": 1
  },
  "matched_exclusions": {
   "type": "array",
   "items": {
    "type": "object",
    "required": [
     "clause",
     "basis"
    ],
    "properties": {
     "basis": {
      "type": "string",
      "maxLength": 240,
      "minLength": 3
     },
     "clause": {
      "type": "string",
      "maxLength": 400,
      "minLength": 3
     }
    },
    "additionalProperties": false
   },
   "maxItems": 40
  },
  "claim_validity_score": {
   "type": "number",
   "maximum": 100,
   "minimum": 0
  },
  "risk_of_denial_percentage": {
   "type": "number",
   "maximum": 100,
   "minimum": 0
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "draft_text": "North Pier Contracting\nHarbor Mutual\nClaims Department\n\nRe: Dispute — claim CLM-100, policy GL-2041\n\nDear Claims Department,\n\nI am North Pier Contracting. This letter disputes the application of a coverage exclusion to the loss described below. Please review the facts against the policy and confirm the claim decision in writing.\n\nPolicy number: GL-2041\nClaim number: CLM-100\nDate of loss: 2026-03-02\nAmount claimed: $12,500.00\n\nFacts:\nRiver flood water entered the warehouse after the storm. A forklift also struck a rack.\n\nCoverage review supplied with this letter:\nValidity score: 75 of 100\nDenial risk: 35 percent\nExclusions matched by that review:\n- flood, surface water, or overflow of any body of water\n\nPlease cite the policy language you rely on if any part of this claim is denied, and list any documents you still need. This draft was prepared from the fields above for human review before it is sent.\n\nSincerely,\nNorth Pier Contracting",
  "completeness_score": 100
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/brainiac-insurance-claim-dispute-letter-drafter-1958dda9/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)
