Get a CMA
https://api.ruuster.com/v1/cma/{cmaId}Read a CMA your brokerage ran, for 90 days after it was created. The same object Run a CMA returned, with the market as it was that day.
- Authentication:
x-api-keyandx-emailheaders of an owner or admin - Rate limit: 120 requests per minute per key
Returns a stored analysis exactly as Run a CMA produced it; nothing is recomputed, so the comps and market figures are as of the day it ran. CMAs are kept for 90 days. A cmaId from another brokerage, or an expired one, returns 404 not_found. Reading a stored CMA doesn't count toward the daily CMA allowance.
In Claude (claude.ai and Claude desktop) and other assistants that show MCP Apps, the cma_create and cma_get tools' answers come with a visual CMA: the subject's photo gallery, the value conclusion, each sold comp with its photo and adjustments, the active, pending and expired competition with thumbnails, the market and the net sheet, under your logo and in your colors and fonts from the brand kit, with the credited agent's photo and contact details. Through MCP those answers also carry brand (the brand kit, for a seller-facing write-up or listing presentation), and the tools take includePhotos (0 to 8), which hands the assistant that many of the subject's photos to look at, for example to judge condition and updates before re-running with overrides. None of this is part of the HTTP API.
Path parameters
| Name | Type | Description |
|---|---|---|
cmaId |
string |
Response
data is the CMA object described on Run a CMA, with cmaId and createdAt. meta.ms is how long the original run took.