Analyze a policy and prepare claim evidence API
Extract policy clauses, run a preliminary text-match screen, and build a general evidence checklist. This is not legal advice or confirmation of coverage.
The Analyze a policy and prepare claim evidence operation is part of the Insurance Claims Assist API on BRAINIAC.software. Extract policy clauses, run a preliminary text-match screen, and build a general evidence checklist. This is not legal advice or confirmation of coverage. It is exposed as POST /api/v1/claims/analyze and priced at $0.10 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: Policy documents and incident facts supplied by the caller. Limitations: Results are preliminary assistance, not legal advice or confirmation of coverage. Correspondence is a draft and is never sent automatically. 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 Draft insurer correspondence. Open the group documentation for the full request schema, field notes, and response examples before integrating.
/api/v1/claims/analyzeExample request
curl -i -X POST "https://www.brainiac.software/api/v1/claims/analyze" \
-H 'content-type: application/json' \
-H 'Idempotency-Key: <fresh-64-character-random-hex-key>' \
--data-binary @- <<'JSON'
{
"filename": "policy.pdf",
"fileBase64": "JVBERi0xLjcKJYGBgYEKCjYgMCBvYmoKPDwKL0ZpbHRlciAvRmxhdGVEZWNvZGUKL0xlbmd0aCAyNTUKPj4Kc3RyZWFtCnicbZDNSgQxEITveYqcBTE/neoERNDZDB68CHkBkXVR9KCIz2+lB3ZFJZCkJ11V3/S7uxku+Lk+Du7idv/6tf98fnw419Cq1KC1+Zj8eHKx+nHnorVGL9VrCH68uUspWhGx04AFJQWeK28NWVsKEFZZC3Yo6CpXfry4cUZZxqpA0USxouTrFIqagVK8YDGraCZgb+J50hSIdUaVWVsQITYvvjDW9jor+nUlxFEXeFvpzi8qTOgnrM4HmfQb0sSc3DTOKv9bzvjNck6BHYtBR+AIF9E3DX0bUW0WP2PnEDOFRWcDIy0cnMPKJb//D00zd4P9M5ejbR/u3n0DxS9nngplbmRzdHJlYW0KZW5kb2JqCgo3IDAgb2JqCjw8Ci9GaWx0ZXIgL0ZsYXRlRGVjb2RlCi9UeXBlIC9PYmpTdG0KL04gNQovRmlyc3QgMjYKL0xlbmd0aCAzNjgKPj4Kc3RyZWFtCnic1VJNS8NAEL3vr5ijHux+NMkmUgptkyiIWFpBUTykyVIiZVeSjdR/70zSWnoQzxIeuzPzZvdt5kkQoCAIYAw6hgDCsYIQtNQwmTD++PVhgC+LrWkZv6urFl6RI2AFb4wvXGc9SDadshN3Ufhi57ZsaAJJ5CNj2biqK00DkzzLcyG0ECIKEJEQKsV1gUgQCmOsqRj3CB0cgDk9FmI8w1o+INJDD9V7bnjoz3BFbkScdOAG8RD/3Et3ZcMZ6i89yZTxe1elhTdwkV4roSIphZRaBjJ5ucTf0ZjCu//7uF5/7eyvLzybM42XhtwY8kA/Zb4yreuaEsdOvNxhhTa3ZvdpfF0WV1okMerUcYIeOxiDPz9s3k3ZUynM9v5m7UnDkKDcvanqYu726D6BX5iEIxVDHMgRnoROnFnrPHmzd6X1qImi6ODUM+Eki/F1t/F9SEnJ+LxoTS/4pBal2NJVtd0Cf6rtzLb1MUEnfgOKSscqCmVuZHN0cmVhbQplbmRvYmoKCjggMCBvYmoKPDwKL1NpemUgOQovUm9vdCAyIDAgUgovSW5mbyAzIDAgUgovRmlsdGVyIC9GbGF0ZURlY29kZQovVHlwZSAvWFJlZgovTGVuZ3RoIDQyCi9XIFsgMSAyIDIgXQovSW5kZXggWyAwIDkgXQo+PgpzdHJlYW0KeJxjYGD4/5+JgZ2BAUQwgggmEMEMIlgYGQQYGBgZI4AEsx4DAwBc+QLTCmVuZHN0cmVhbQplbmRvYmoKCnN0YXJ0eHJlZgo4MTQKJSVFT0Y=",
"incidentDate": "2026-10-20",
"incidentType": "property damage",
"description": "Water damage in the insured building",
"knownDocuments": []
}
JSONAn 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 operations
- Draft insurer correspondence — $0.02 USDC