API documentation

Support

How to reach us and what you can expect, on one page. This page repeats only the commitments that are already published elsewhere in this documentation. It adds none.

How to reach us

In the dashboard, use Report an issue in the sidebar. The note reaches the team with the page attached, and every report is stored on our side before it is delivered, so none is lost.
For everything else write to contact@stonewake.ai, in English or in German.
Your workspace has a named contact from onboarding. Account changes such as a password reset, a new user or the removal of a leaver go through that person.
A suspected vulnerability, or anything that looks like an incident affecting your workspace, goes to the same address with "Security" in the subject. The Security disclosure page has the scope and the safe harbour.

Monthly feedback

A workspace can ask every named user five questions once a month, in the dashboard, in about three minutes. What did you use Stonewake for? How many minutes did it save on a typical task? Which leads did you take forward, and which early warnings reached you first? What is missing or wrong? Would you keep it?
The form is off until an administrator switches it on under Settings and names its recipients. A recipient must be a named user of the same workspace who has signed in; any other address is refused.
From the 15th of each month a quiet note at the top of the page asks once. Not now puts it away until next month, and the form stays reachable from the sidebar. An answer can be changed up to five times until the month ends.
Every answer goes by email to the named recipients, in the workspace's alert language, through the alert mail service in Paris that delivers alerts, and Stonewake receives the same answers for the monthly report, so nobody forwards anything by hand. The API and the MCP server do not serve the answers.

What you can expect

We will get back to you on an issue report the same day, as stated under Enterprise onboarding.
A security report is acknowledged within three business days, followed by a first assessment with an indicative fix path, as stated under Security disclosure.
Never put live keys, credentials or workspace data into a message to us. The host, the path, the time of the request and the error code from the response are enough for us to find it. The codes are listed under Errors and rate limits.

What we do not publish

There is no published service level agreement. What applies to your institution is what your contract says, and this page does not stand in for it.
There is no public status page today.
There is no telephone hotline.

See also the Changelog and the Security overview.