The sknr developer reference documents nine REST endpoints, all POST under https://api.sknr.wholetech.eu/api/v1/vendor. Image routes accept multipart and the rest accept JSON. The endpoints are grouped in three capability packs: A shade and skin, B medication and routine, C clinical screening. Every request sends x-api-key plus Authorization set to the literal string api-key; a Bearer token overrides the key and is the most common cause of an unexpected 401.
Responses return signals, not diagnoses: ranked predictions, adaptive questions, and a severity index on sknr's own 0 to 10 scale that is not PASI, SALT, SPI or IGA. Every 2xx carries a disclaimer to pass to the end user unaltered; Pack C adds a limitations string. Nine MCP tools wrap the same routes: the REST endpoints are live, the MCP server is not published yet.
The page also covers upload limits, enumerations and error codes, and states plainly that no accuracy, sensitivity or specificity figures are published for these models and that sknr output may not be built into a product placed on the market as an MDR Class IIa or higher medical device.