Developers & AI agents

Start in 60 seconds

curl "https://covelightcare.com/api/v1/facilities?county=Los%20Angeles&needs=dementia,wheelchair&limit=2"

const res = await fetch("https://covelightcare.com/api/v1/facilities?county=Los%20Angeles&needs=dementia,wheelchair&limit=2");
const body = await res.json();
if (!res.ok) throw new Error(`${res.status}: ${body.error}`);
console.log(`${body.data.total} homes; next page: offset=${body.data.offset + body.data.limit}`);
for (const f of body.data.facilities) console.log(f.license_number, f.name.value, f.clearances.dementia.value);

import requests

res = requests.get("https://covelightcare.com/api/v1/facilities", params={"county": "Los Angeles", "needs": "dementia,wheelchair", "limit": "2"}, timeout=30)
body = res.json()
if not res.ok:
    raise SystemExit(f"{res.status_code}: {body['error']}")
print(body["data"]["total"], "homes; next page: offset =", body["data"]["offset"] + body["data"]["limit"])
for f in body["data"]["facilities"]:
    print(f["license_number"], f["name"]["value"], f["clearances"]["dementia"]["value"])

curl "https://covelightcare.com/api/v1/facilities/191200037"

const res = await fetch("https://covelightcare.com/api/v1/facilities/191200037");
const body = await res.json();
if (!res.ok) throw new Error(`${res.status}: ${body.error}`);
const home = body.data;
console.log(home.name.value, home.license_status.value, "as of", home.license_status.confirmed_on);
for (const [need, fact] of Object.entries(home.clearances)) console.log(need, fact.value);

import requests

res = requests.get("https://covelightcare.com/api/v1/facilities/191200037", timeout=30)
body = res.json()
if not res.ok:
    raise SystemExit(f"{res.status_code}: {body['error']}")
home = body["data"]
print(home["name"]["value"], home["license_status"]["value"], "as of", home["license_status"]["confirmed_on"])
for need, fact in home["clearances"].items():
    print(need, fact["value"])

curl "https://covelightcare.com/api/v1/facilities/191200037/reports"

const res = await fetch("https://covelightcare.com/api/v1/facilities/191200037/reports");
const body = await res.json();
if (!res.ok) throw new Error(`${res.status}: ${body.error}`);
console.log("Read them at", body.data.state_record_url);
for (const r of body.data.reports) console.log(r.date, r.title);

import requests

res = requests.get("https://covelightcare.com/api/v1/facilities/191200037/reports", timeout=30)
body = res.json()
if not res.ok:
    raise SystemExit(f"{res.status_code}: {body['error']}")
print("Read them at", body["data"]["state_record_url"])
for r in body["data"]["reports"]:
    print(r["date"], r["title"])

curl "https://covelightcare.com/api/v1/guides"

const res = await fetch("https://covelightcare.com/api/v1/guides");
const body = await res.json();
if (!res.ok) throw new Error(`${res.status}: ${body.error}`);
for (const g of body.data.guides) console.log(g.title, g.url);

import requests

res = requests.get("https://covelightcare.com/api/v1/guides", timeout=30)
body = res.json()
if not res.ok:
    raise SystemExit(f"{res.status_code}: {body['error']}")
for g in body["data"]["guides"]:
    print(g["title"], g["url"])

curl -X POST "https://covelightcare.com/api/v1/check" \
  -H "Content-Type: application/json" \
  -H "X-Client-Name: your-product" \
  -d '{"homes":["191200037","Sunrise","Zzqx Nothing"]}'

const res = await fetch("https://covelightcare.com/api/v1/check", {
  method: "POST",
  headers: { "Content-Type": "application/json", "X-Client-Name": "your-product" },
  body: JSON.stringify({"homes":["191200037","Sunrise","Zzqx Nothing"]}),
});
const body = await res.json();
if (!res.ok) throw new Error(`${res.status}: ${body.error}`);
for (const r of body.data.results) {
  console.log(r.input, r.status, r.home?.name ?? r.candidates.map((c) => c.name).join(" / "));
}

import requests

res = requests.post("https://covelightcare.com/api/v1/check", json={"homes": ["191200037", "Sunrise", "Zzqx Nothing"]}, headers={"X-Client-Name": "your-product"}, timeout=30)
body = res.json()
if not res.ok:
    raise SystemExit(f"{res.status_code}: {body['error']}")
for r in body["data"]["results"]:
    print(r["input"], r["status"], r["home"]["name"] if r["home"] else [c["name"] for c in r["candidates"]])

Budgets per IP: 120 requests a minute on /api/v1/*, 30 on POST /api/v1/check. Details: rate limits.

Connect an AI assistant (MCP)

https://covelightcare.com/mcp

claude mcp add --transport http covelight https://covelightcare.com/mcp

{
  "mcpServers": {
    "covelight": {
      "type": "http",
      "url": "https://covelightcare.com/mcp"
    }
  }
}

{
  "mcpServers": {
    "covelight": {
      "url": "https://covelightcare.com/mcp"
    }
  }
}

code --add-mcp "{\"name\":\"covelight\",\"type\":\"http\",\"url\":\"https://covelightcare.com/mcp\"}"

{
  "servers": {
    "covelight": {
      "type": "http",
      "url": "https://covelightcare.com/mcp"
    }
  }
}

{
  "mcpServers": {
    "covelight": {
      "type": "http",
      "url": "https://covelightcare.com/mcp"
    }
  }
}

Where it can’t connect yet

• Not in any directory yet. Covelight Care — California care homes is not listed in Claude’s connector directory or ChatGPT’s plugin directory, so neither host suggests it on its own. You add it by its URL, and Claude labels it “Custom”.
• ChatGPT’s Free plan and mobile apps. Developer mode is web-only, on the plans named above.
• Clients that speak only a revision newer than these. The server speaks 2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05, 2024-10-07 — MCP’s 2026-07-28 revision and the 2025 initialize handshake, on the same URL. A request that declares a newer version gets a 400 that names the revision to use instead (example).
• Clients that need a GET event stream or the old SSE transport. The server is stateless and POST-only; GET answers 405.
• Hosts that only start local (stdio) servers and cannot reach a remote URL.

The data dictionary

The fields a caller must read correctly. The REST API wraps each fact as { value, source_class, confirmed_on, next_due, ref }; the MCP tools return flat records with an as_of date on each group.

Yes, no, and “not on file”

Dates and provenance

Check the dates rather than polling: a response is only as current as its retrieved_on and confirmed_on say.

License status, including closed licenses

Price kinds (MCP)

find_homes’ max_monthly_budget_usd, in the tool’s own words: “Monthly ceiling in whole dollars, 1000 to 30000. Reads each home’s starting figure — its own listed rate, else Covelight’s estimate or the area’s typical rate; a home with no figure on file stays in. Example: 6000.” price is null when no figure is on file, and always on a closed license.

Medi-Cal Assisted Living Waiver

Neutral order: there is no ranking parameter

What is never in this data

• Availability. No field says whether a home has an open bed, under any name. What every MCP list result says instead: “No website — including this one — knows which homes have an open bed today. Openings change daily and live only inside each home. That is what the phone call is for.”
• Scores, ratings and tiers. None exists to return.
• Business fields. The record’s columns are named one by one, and every payload is scanned for business and availability keys before it is sent.
• Personal data. No family, lead or contact data is reachable. A home’s phone is the number on the state roster.

Markdown pages

GET https://covelightcare.com/facility/regency-park-oak-knoll-191200037.md

HTTP 200
content-type: text/markdown; charset=utf-8
cache-control: s-maxage=86400, stale-while-revalidate=31449600
link: <https://covelightcare.com/facility/regency-park-oak-knoll-191200037>; rel="canonical"
x-robots-tag: noindex

# Regency Park Oak Knoll

License #191200037 · Pasadena, Los Angeles County · Licensed for 206 — Large care community · a licensed care home (RCFE)

Regency Park Oak Knoll is a large care community in Pasadena — a licensed residential care facility for the elderly (RCFE), the licence category behind “assisted living” and “board and care.” It is licensed for 206 residents since 1987. Hospice care and bedridden care are not on file.

- Care approvals on file: Wheelchair · Dementia — State licensing record · September 13, 2026
- Starting rate: $5,950 a month — Listed by the home on Seniorly · September 9, 2026

Full page: <https://covelightcare.com/facility/regency-park-oak-knoll-191200037>

A citation does not make a home unsafe, and an empty file does not make a home good.

## Quick answers about Regency Park Oak Knoll
…

The family hand-off

1. The assistant calls start_family_request with 1–5 license numbers the family chose, and optionally care needs, timing, an area and a note. It sends no personal details. The tool screens every free-text field for them (names, phone numbers, emails, addresses) and refuses the call when the screen finds one (example), but a screen cannot catch every name: send none.
2. The tool writes nothing about the family. It returns a signed link, dated to lapse in 7 days, relay_sentence (one sentence to pass on), a longer family_message, each home’s roster phone and questions to ask, and consent.agent_can_consent: false.
3. The family opens the link. Covelight Care opens its free plan-calls-and-visits page with those homes already chosen, and a folded note saying an assistant chose them and that opening the link told no home about them. After 7 days the link still opens the homes, without that note, and a request the family later sends is no longer attributed to the assistant.
4. What happens next depends on one switch Covelight Care holds.

The link (hand-off signatures are cut on this page) carries only license numbers, the care needs, a timing choice, an expiry and the MCP client’s own name from its initialize call. Nothing typed in assistant_name or family_note goes into it. A tampered link opens nothing. Both captured calls, in full: the tool reference.

Terms and attribution

Discovery files

The server-card and catalog formats are an experimental MCP extension. The card, the catalog and server.json each answer with an ETag, allow any origin, and may be cached for an hour.

Support

Changelog

The MCP server is at version 1.1.2. Changes are additive; a rename or removal is announced here first, with at least 90 days’ notice (compatibility policy).

• 2026-09-28 · MCP server 1.1.2get_state_documents and get_home list one document for every report the state lists. A complaint whose investigation filed several reports under one control number now shows each report; about 1,800 across California were folded into one of their siblings before. A transcription is matched to its listed report by the state's own document id before date and form, so a report the state's list dates differently from its print no longer appears twice. No field changed.
• 2026-09-28 · REST APIA one-time correction to a report's ref on /api/v1/facilities/{license}/reports: it is now doc: followed by the state's own document id, one per document and stable from one harvest to the next. It used to be the row's key: a complaint's control number, which every report of that complaint shares, or for other reports a key of ours that moved between harvests although it was documented as stable. A ref stored before 2026-09-28 will not match. A complaint's control number now comes from the new field control_number, which is null on reports the state lists without one. The list now includes every report the state lists, so a home's total can rise.
• 2026-09-23 · MCP server 1.1.1start_family_request refuses more names. A name with an apostrophe after its first letter (O’Brien, D’Angelo), typed with a straight or curly apostrophe, is now caught wherever a plain name already was: after “named” or “called”, a title such as Mrs., or a family word. An introduction of a relative’s, friend’s, neighbor’s, patient’s, client’s or resident’s name (“grandma’s name is …”, “my mother-in-law’s name is …”) is caught too, not only a parent’s. The screen still cannot catch every name, so the rule is unchanged: send no personal details.
• 2026-09-23 · REST APIservice_designations on /api/v1/facilities and /api/v1/facilities/{license} leaves out a state service code that grants a clearance under a correction review: every code while the dementia clearance is held, and "985 - RCFE / HOSPICE" while the hospice clearance is held. The facility page already left out every code under a dementia hold; it now also leaves out the hospice code under a hospice hold.
• 2026-09-23 · REST APIA clearance under a correction review now reads "not_on_file" on /api/v1/facilities and /api/v1/facilities/{license}, as it already did on the facility page and in the MCP tools, and it no longer matches a needs filter. Both are CDN-cached for five minutes (was an hour), so a review reaches them within minutes.
• 2026-09-23 · MCP server 1.1.0explain is now explain_care_topic. The old name still answers until 2026-12-22, then it is removed. New: search and fetch, the tool pair ChatGPT connectors and deep research call; fetch returns a home’s page as Markdown with its canonical URL. /mcp speaks MCP 2026-07-28 (server/discover, no session) beside the 2025 initialize handshake. Every tool description says when to use it and what it is not for, and every argument names its allowed values with an example. Budget: 60 requests a minute per caller; inside Anthropic’s and OpenAI’s published egress ranges the caller is the session or the ChatGPT user, under a shared per-host ceiling. Over budget, the answer is 429 with Retry-After and a JSON-RPC error. Two names for every home. name is now the name the home goes by: the licensed name without a trailing legal form such as LLC, Inc., Corp. or Ltd. The exception is a fixed list of 22 names that two licences in one city would otherwise share; those keep the form wherever they appear. The new field licensed_name holds the name on the license, verbatim as filed. It appears on home records, summaries, check_homes candidates and get_state_documents. Links are unchanged.
• 2026-09-23 · REST APIlicensed_name on /api/v1/facilities records and POST /api/v1/check results: the name on the license, verbatim. It is an additive field; name on /api/v1/facilities keeps the record's own string.
• 2026-09-23 · SiteThis developer portal: a quickstart in curl, JavaScript and Python, per-host MCP setup, a reference generated from openapi.json and the MCP tool registry with real responses, and a data dictionary. Discovery files: the MCP server card at /mcp/server-card and /.well-known/mcp/server-card.json, and /.well-known/ai-catalog.json.
• 2026-09-23 · MCP server 1.0.0First release of the remote MCP server at /mcp: find_homes, check_homes (up to 100 homes a call), get_home, get_state_documents, compare_homes, homes_near_hospital, explain and start_family_request. POST /api/v1/check, the REST twin of check_homes. Markdown versions of pages ({page}.md, or Accept: text/markdown).
• 2026-08-10 · REST API v1The v1 read API: GET /api/v1, /api/v1/facilities, /api/v1/facilities/{license}, /api/v1/facilities/{license}/reports and /api/v1/guides, with the OpenAPI 3.1 contract at /openapi.json.