Detect coverage gaps API

Compare caller-supplied contract requirements to supplied limits, deductibles, and exclusions. Preliminary gap signals only—not coverage confirmation.

The Detect coverage gaps operation is part of the Insurance Underwriting & Policy Intelligence API on BRAINIAC.software. Compare caller-supplied contract requirements to supplied limits, deductibles, and exclusions. Preliminary gap signals only—not coverage confirmation. It is exposed as POST /api/v1/insurance-intelligence/coverage-gap-detect and priced at $0.05 USDC on Base. Payment uses the x402 exact scheme: an unpaid call returns HTTP 402 with payment requirements; after paying the exact USDC amount, retry the same request with a payment-signature header and Idempotency-Key. No account and no API key are required. Data sources for this product: Caller-uploaded insurance policies, schedules, loss runs, requirements, and evidence records processed locally Limitations: No insurer or broker system is contacted and no API key is required. PDF text extraction is local and heuristic. Scanned/image-only PDFs are not OCR-read. Results are preliminary document analysis for underwriting workflow support—not confirmation of insurance coverage or legal advice. Missing values are not invented. Program and renewal comparisons use only supplied sides/labels. Coverage gap findings compare supplied requirements to supplied policy extracts only. Outputs are compliance prechecks, drafts, or data lookups for human review. They are not official determinations, legal advice, identity confirmation, or certified filings. Related operations in this group include Normalize insurance policies, Compare policy limits, Compare policy exclusions, Extract deductible structures. Open the group documentation for the full request schema, field notes, and response examples before integrating.

POST$0.05 USDC
/api/v1/insurance-intelligence/coverage-gap-detect

Example request

curl -i -X POST "https://www.brainiac.software/api/v1/insurance-intelligence/coverage-gap-detect" \
  -H 'content-type: application/json' \
  -H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
  --data-binary @- <<'JSON'
{
  "asOf": "2026-11-04T21:00:00.000Z",
  "limits": [
    {
      "coverage": "Each Occurrence",
      "limitAmount": 1000000,
      "side": "current",
      "source": "Caller-supplied"
    }
  ],
  "deductibles": [
    {
      "coverage": "Each Occurrence",
      "amount": 5000,
      "source": "Caller-supplied"
    }
  ],
  "requirements": [
    {
      "id": "R1",
      "coverage": "Each Occurrence",
      "minLimitAmount": 2000000,
      "maxDeductibleAmount": 10000,
      "requiredEndorsement": "Additional Insured",
      "forbiddenExclusion": "Contractual Liability",
      "source": "Caller-supplied contract"
    }
  ]
}
JSON

An unpaid probe returns HTTP 402 with x402 payment requirements. After paying the exact USDC amount on Base, retry the identical request with a payment-signature header.

FAQ

  • Do I need an API key? No. Pay the listed USDC amount with x402.
  • What network? Base (eip155:8453), USDC.
  • Is this an official determination? No. Results are for human review against the cited sources.

Related APIs

Insurance Underwriting & Policy Intelligence APIFull docsHow it works