One Operator-Controlled Operating Record across clinical, financial, workforce, market, and compliance. A typed API that returns not just the value, but which source the operator declared authoritative for it and the lineage behind it. Agent-native discovery built in — not bolted on.
One Operator-Controlled Operating Record, agent-native discovery, and audit-grade PHI handling — built for developers, integrators, and AI agents that need the operating record for senior housing & care.
Answer first
Most AI tools in senior housing & care fail the same way: they hallucinate because the underlying data is fragmented across an EHR, an ERP, a CRM, a scheduler, and a BI tool. SeniorCRE eliminates that — every system normalizes into the same six entities (Resident, Care Plan, Ledger, Shift, Property/Unit, Entity), so an agent calling the API gets a canonical answer, not a reconciled guess.
SeniorCRE is not valuable because it has AI. SeniorCRE is valuable because AI makes trusted operating data exponentially more important.
C2
Canonical data layer
Six canonical entities anchor the model; every field carries its declared source.
tRPC
Typed API contract
Domain routers per functional area, typed end to end from schema to client.
Aurora
Managed infrastructure
Aurora PostgreSQL 17 and ECS Fargate, with separate staging and production estates.
61 / 64
Internal test suite, synthetic environment
Vanta automated framework, verified April 30, 2026.
For operators & owners
Behind every technical capability sits a business outcome — governed definitions, declared source authority, reconciliation of differences, and preserved lineage.
Technical capability
Business outcome
Unified operator-controlled operating record
Single operating record
Six canonical entities (Resident, Care Plan, Ledger, Shift, Property/Unit, Entity) — no more reconciling spreadsheets across clinical, financial, and property systems.
Typed request-time APIs
Faster decisions
Occupancy, ledger, and census can be read at request time in controlled SeniorCRE environments; freshness follows the source release cadence.
Agent-native discovery
Clinician hours returned
Agents and copilots can support documentation, scheduling, and compliance tasks against the Operator-Controlled Operating Record, subject to human approval.
Structured benchmarks
Audit-grade investor reporting
Institutional-grade data exports LPs, lenders, and surveyors actually trust — normalized to integer cents.
Agent discovery
AI crawlers and autonomous agents find SeniorCRE through industry-standard discovery endpoints. Point your agent at any of these and it gets a structured map of the platform.
seniorcre.com/llms.txtNatural-language platform description optimized for LLM comprehension. Full capability index, key pages, and content taxonomy.
.well-known/agents.jsonStructured capability manifest with data domains, integration protocols, compliance status, and contact endpoints.
seniorcre.com/robots.txtGPTBot, ClaudeBot, PerplexityBot, and all major AI crawlers explicitly allowed. Full access to public marketing content.
Data domains
Agents in senior housing & care need structured, compliant, real-time data. SeniorCRE is designed to be that layer, staying canonical regardless of which upstream system generated the row.
EHR, eMAR, ADL, care plans, vitals, wound care, behavior tracking
Scheduling, labor costs, retention analytics, float-pool management
NOI, RevPAR, occupancy, operating margins — normalized to integer cents
Submarket supply/demand, comps, demographics, competitive analysis
State licensing, survey deficiencies, corrective actions — all 50 states
Properties, portfolios, deal pipeline, transactions, valuation tools
Proprietary operational benchmarks, staffing ratios, care quality scores
Integration protocols
REST API for traditional integrations. MCP for AI agents. SCRE-DEX for industry data exchange. Each maps onto the same operating record.
Proof model
No marketing capability claims dressed as production. Tier assignment is auditable and surfaced on the technical documentation page.
Evidence class
Exists in a controlled SeniorCRE environment. This does not mean operator production or measured outcome.
Evidence class
Exercised end to end with synthetic or de-identified data.
Evidence class
Requires named operator data, instrumentation, a defined baseline, and passed acceptance gates. None claimed today.
Evidence class
Requires a named operator result with the source, window, method, and lineage stated. None published today.
Evidence class
Specified or intended, but not built. Timing depends on deployment, safety, and acceptance gates.
The moat
The SeniorCRE moat is operator-controlled authority across the entire stack. The per-community instance preserves definitions, source authority, reconciliation, and lineage. Horizontal platforms cannot reach in and replicate that authority.
New agents face a chicken-and-egg problem — they need data to be useful, but need users to get data. The Operator-Controlled Operating Record is designed to remove that step: an agent reads only what authority rules permit, with lineage to the upstream system that produced it.
HIPAA, state licensing, and survey data require specialized handling. PHI is served via signed URLs, with sealed sessions, tenant isolation, and server-side access helpers.
The protocol for exchanging operational definitions and benchmarks is published, not proprietary. Agents that need operational benchmarks, staffing ratios, or care quality scores can read the schema before they connect.
Domain-specific schemas for medication administration, ADL assessments, regulatory surveys, and NOI calculations — modelled for senior housing & care rather than mapped onto a generic entity.
Architecture
┌─────────────────────────────────────────────────────┐ │ AI Agent Ecosystem │ │ │ │ ┌──────────┐ ┌──────────┐ ┌──────────────────┐ │ │ │ Claude │ │ GPT │ │ Custom Agents │ │ │ │ Agents │ │ Agents │ │ (Investor Tools) │ │ │ └────┬─────┘ └────┬─────┘ └────────┬─────────┘ │ │ │ │ │ │ │ └─────────────┼─────────────────┘ │ │ │ │ │ ┌──────▼────────┐ │ │ │ MCP / REST │ │ │ │ Interface │ │ │ └──────┬────────┘ │ │ │ │ │ ┌──────────────────▼────────────────────────────┐ │ │ │ SeniorCRE — operator authority plane │ │ │ │ │ │ │ │ ┌─────────┐ ┌──────────┐ ┌───────────────┐ │ │ │ │ │Clinical │ │Financial │ │ SCRE-DEX │ │ │ │ │ │ Data │ │ Metrics │ │ Benchmarks │ │ │ │ │ └─────────┘ └──────────┘ └───────────────┘ │ │ │ │ ┌─────────┐ ┌──────────┐ ┌───────────────┐ │ │ │ │ │ CRM / │ │Compliance│ │ Market Intel │ │ │ │ │ │ Census │ │ & Survey │ │ & Analytics │ │ │ │ │ └─────────┘ └──────────┘ └───────────────┘ │ │ │ └───────────────────────────────────────────────┘ │ └──────────────────────────────────────────────────────┘
Security & compliance
Commercial terms are provided under NDA in a written scope. SeniorCRE does not claim SOC 2 certification or a SOC 2 report; reports are published only when issued. Native mobile and on-platform payments are not in current scope.
Frequently asked
Next step
Whether you're shipping an AI agent, integrating operational data, or developing tools for the industry — SeniorCRE is the data layer. Request API access and we'll map your use case onto the operating record.