Service status and data vintages
https://platform.casafari.com/v1/claro/healthNeeds no key on Claro's own host. On the platform this is GET https://platform.casafari.com/v1/claro/health; GET /v1/health is Claro's own path, which the platform adds /claro to. The platform forwards the call to Claro unchanged: Claro's Claro-Version header and its error bodies ({"error":{"code","message"}}, with rate_limited and quota_reached on a 429) pass through.
Over MCP: no tool does this. MCP and REST compared.
Description
No key needed. The version, the vintages of the location data (Targomo datasets, Overture Maps places release), when the sync last updated a property, and how many properties are active. Cached for 60 seconds. 503 with ok false when the database cannot be read.
Example request
Placeholders only: replace the token and the values with your own.
curl "https://platform.casafari.com/v1/claro/health"Responses
200 Status
No body.
Example from the API description
{
"ok": true,
"version": "1.0.0",
"data": {
"Portal": [
{
"dataset": "Footfall estimates",
"vintage": "2024"
},
{
"dataset": "MB Research sociodemographics",
"vintage": "2024"
}
],
"overture_release": "2026-09-23.1",
"last_sync_at": "2026-10-15T03:12:00Z",
"active_listings": 41250
},
"checked_at": "2026-10-15T09:00:00.000Z"
}503 Database unreadable; ok is false and the data fields are null
No body.