The platform
The platform our companies run on.
Most home health and hospice companies run on the same vendor software. We built our own platform, with its own API, and our apps run on it. We haven’t found another home health, hospice and palliative care company that does. It isn’t for sale.
/api/v1/health…Calling the API from your browser…
- Apps built on it
- 4
- API operations
- 38
- Sites on the Navigator engine
- 2
- Records in the API
- 7
Six parts, one back end.
Each part is used by more than one app. That’s the point: we build a part once, and every company gets it.
Accounts and sign-in
Live inside our companiesOne sign-in for our own people, with two-step, sessions anyone can end, and an activity log owners can read and download.
POST /sign-inPlatform API
Live38 operations on seven records: businesses, people, objectives, key results, check-ins, promises and cadences. JSON in and out, our own keys, an OpenAPI 3.1 document generated from the code.
GET /api/v1/objectivesNavigator engine
LiveOne engine behind every question box we run. A site is a document: its pages, its voice, its rules. Answers come only from that site’s own pages.
POST /navigator/<site>/askOKR records
LiveObjectives roll up through a parent, key results carry where they started, where they stand and where they should land, and check-ins move them.
GET /api/v1/boardAgents
Internal buildAgents watch the numbers and draft the next step. A person approves it before anything changes, and every decision lands in the activity log.
Approve or declineNarration
LiveEvery field note and every Lab answer can be read aloud in a consistent voice, disclosed as AI narration.
POST /navigator/<site>/speak
What’s built on it.
Four apps today, each marked as live or still an internal build.
- Live
hvhh.ai
HealthView’s site. Its Care, Careers and Ask Rounds navigators answer families, applicants and readers in English or Spanish from the Navigator engine.
Runs on: Navigator engineVisit hvhh.ai ↗ - Live
Navigator by CultureAI
The question box on every site we run, answering from that site’s own pages. Built once, switched on with a config, and on the Lab every answer cites its passages and reads aloud.
Runs on: Navigator engineNarrationPlatform APITry it → - Internal build
The OKR app
The 1:1 coach, objectives and promises kept, inside Teams or Slack where leaders already work. Running in our companies first.
Runs on: Accounts and sign-inOKR recordsAgentsPlatform APISee how it works → - Live
The Culture Lab
Field notes in text and audio, a public Ledger of scored predictions, and Ask the Lab over every note.
Runs on: Navigator engineNarrationRead the Lab →
One question, end to end.
What happens when someone types a question into a site we run, and what is never kept along the way.
- A visitor asksIn their own words, in the question box on hvhh.ai or The Culture Lab.
- The engine reads the siteIt loads that site’s document: the pages it may answer from and the rules it keeps.
- Claude answers from those pagesOnly from that site’s own pages, so the answer can point to where it came from.
- The answer comes back citedOn the Lab, every claim links to the passage it came from.
- It can be heardNarration reads the answer aloud, disclosed as an AI voice.
Real code, not a mock-up.
The first call is public, so you can run it now. The other two use the CultureAI Kit, our SDK and command line, with a key only our companies hold.
# Anyone can run this one. It needs no key.
curl https://cultureai.com/api/v1/health
{ "ok": true, "build": "B239", "db": "ready",
"time": "2026-10-18T19:30:00.000Z" }
// Inside our companies: the CultureAI Kit import CultureAI from '@cultureai/kit'; const cai = new CultureAI(); // reads CULTUREAI_API_KEY const answer = await cai.navigator('lab').ask('What is the yield?'); console.log(answer.text, answer.sources);
# The same kit, from a terminal cultureai ask lab "what is the yield" cultureai board healthview cultureai smoke # checks every part, end to end
Built in, not bolted on.
The parts of the platform you can’t see, and why they’re there.
Keys shown once
A key is shown one time when it’s made. We keep only its SHA-256 fingerprint, so a stolen database can’t sign anyone in.
A request id on every answer
Every response carries an x-request-id, and every call is in the request log, so any answer can be traced.
Safe to retry
Send an Idempotency-Key and the same request within 24 hours returns the first result instead of making a second record.
Test and live, kept apart
Test keys reach a sandbox only. Live keys reach our companies.
Questions aren’t stored
The Navigator engine writes nothing down: not the question, not the visitor’s address.
No patient data
Patient information never goes in, and won’t until every vendor in the chain has signed a business associate agreement.
One app, up close: the OKR app.
The manager is the sensor, the 1:1 the instrument, the OKR the measure, and an agent the response. It runs inside Teams or Slack, where leaders already work. These screens are illustrations of the internal build.
Signals in
CultureAI core · operational · internal build
Movement out
Sensor
The manager
senses the team
Instrument
The 1:1
captures the signal
Measure
OKRs
score what matters
Intervention
AI agents
deployed on stuck key results
Agents report back to the manager. The loop closes weekly.
CultureAI CoachActive now
Prep my 1:1 with Jordan at 28:52 AM ✓✓
Coach brief
Jordan · RN Case Manager
Pulse dipped 6 pts after the schedule change. Recognition is 14 days overdue.
Suggested commitments · tap to keep
The 1:1 Culture Coach
Every leader runs AI-guided one-on-ones. Tag the coach in a Teams or Slack chat, get the brief, and every commitment is captured before it evaporates.
ObjectivesQ3 · Ops Leadership · posted Mondays
Referral response < 2 hrsIntake SLA 91% · after-hours 96%
Pulse up 4 pts since the rotation fix
OKRs & Cadences
Objectives, key results, and operating rhythm as a tab in the team channel, tracked from the field to the boardroom on a cadence that never slips.
Promises3 open · 2 due this week · tap a filter
- Adjust weekend rotationJordan · Due Friday
- Shadow visit scheduledMaria · Due Thursday
- Values award nominationPriya · Submitted
No promises in this view.
This week5 promises kept · streak: 6 weeks
Promises Kept
Every commitment made in a 1:1 is posted back to the channel and tracked to completion, so follow-through stops depending on memory.
What comes next.
Labeled for what it is. Nothing here is live yet.
- Next
Version pinning
Each key locked to the API version it was made on, so nothing built on it breaks when the API changes.
- Next
Events and webhooks
Signed events when a record changes, with retries and a delivery log.
- Next
A status page and an API changelog
Public uptime, and a dated list of every change to the API.
- Later
Beyond our own companies
Sign-in and the API for people outside the Culture companies. A future sprint, and not for sale.
Not for sale. Installed.
There is one way to run on CultureAI: be a company we build or back.
