# Synthetic sample APIs (fictional insurer — generic naming)

Promoted from the June knowledge-base program; content-verified against the current series on 9 July 2026. All data is synthetic by construction and **generically named** (naming decision 10 July 2026: no invented brand or system names — "the insurer", "partner portal", "vehicle registry"). This satisfies the plan's fictional-content guardrail (§8.2) without colliding with any real-world names, so the files are safe for screen sharing and as LLM input.

| File | What it is | Primary use |
|---|---|---|
| claims-api.yaml | OpenAPI 3 contract, motor claims (the worked motor-claims running example) | W2 spec reading & gap-hunting, W4 LLM demos |
| vehicle-registry-api.yaml | OpenAPI with **deliberately** mismatched naming & date formats vs claims-api | W2 data-mapping exercise |
| vehicle-registry-legacy.wsdl | Valid WSDL for the same registry | W1/W2 "what SOAP looks like" show-and-tell |
| claim-status-event.md | Event contract (pub/sub example) | W2 async requirements |
| bordereaux-file-spec.md | Batch file specification | W2 file-integration requirements |

Notes: in-file references to "D1/D3" sessions are from the old program — read them as W2/W4. The planned Track B demo API (MTPL domain, plan §8.2) follows the same generic-synthetic naming and can borrow shapes from these specs.