Developers — Kareplex API
Use Kareplex as a backend. The API exposes your facilities (auto-enriched from CMS Care Compare), outcomes, regulatory watch, market intelligence, and the cross-layer Weekly Briefing as JSON.
Authentication
Every data endpoint requires a Bearer API key. Mint one (server-side):
pnpm api:key --tenant <your-org-id> --name "frontend prod"Then send it on each request:
curl -H "Authorization: Bearer kx_live_…" \
https://kareplex.com/api/v1/briefingEndpoints
OpenAPI spec ↓| GET /api/v1 | Discovery — lists endpoints (no auth). |
| GET /api/v1/facilities | Your facilities, CMS-enriched with risk scoring. |
| GET /api/v1/facilities/{ccn} | One facility's CMS Care Compare profile + enrichment. |
| GET /api/v1/portfolio | Portfolio-wide risk rollup. |
| GET /api/v1/outcomes | Outcome records (deficiencies, complaints, financials). |
| GET /api/v1/reg-watch | Regulatory change events in your facility-type scope. |
| GET /api/v1/briefing | Cross-layer collisions — the Weekly Briefing. |
| GET /api/v1/market | Market / competitive intelligence. |
Responses are JSON with CORS enabled. Errors use { "error": { "status", "message" } }. All reads are tenant-scoped to the key.