Publish a status page update straight from the incident report

import { SIEClient } from '@superlinked/sie-sdk';

const client = new SIEClient('https://api.superlinked.com', {
  apiKey: 'sk-sie-…',
});

const result = await client.chatCompletions({
  model: 'Qwen/Qwen3.8-27B-FP8',
  messages: [
    { role: 'system', content: "Write a public status page update from the internal incident report below.\n\nReturn exactly these four lines and nothing else:\nStatus: Resolved\nImpact: <what users experienced, one sentence of 25 words or fewer>\nWindow: <YYYY-MM-DD HH:MM> to <YYYY-MM-DD HH:MM> UTC\nCause: <the cause in plain language, one sentence of 25 words or fewer>\n\nRules:\n- Copy the start and end times from the report. If it lists several windows, use the first start and the last end.\n- Do not mention hostnames, ticket numbers or staff names." },
    { role: 'user', content: "Title: 2025-03-31 sessionstore unavailability\n\nTask: T390513\nStart: 2025-03-31 02:58\nEnd: 2025-03-31 03:36\nImpact: Edits were failing for the duration of the outage.\n\nStarting at approximately 02:58 the sessionstore service in both datacenters became unavailable after a enough nodes had crashed due to disk exhaustion, that clients were no longer able to make quorum." },
  ],
  max_completion_tokens: 256,
});
console.log(result.choices[0]?.message.content);

curl https://api.superlinked.com/v1/chat/completions \
  -H "Authorization: Bearer sk-sie-…" \
  -H "Content-Type: application/json" \
  -d "{\"model\":\"Qwen/Qwen3.8-27B-FP8\",\"messages\":[{\"role\":\"system\",\"content\":\"Write a public status page update from the internal incident report below.\\n\\nReturn exactly these four lines and nothing else:\\nStatus: Resolved\\nImpact: <what users experienced, one sentence of 25 words or fewer>\\nWindow: <YYYY-MM-DD HH:MM> to <YYYY-MM-DD HH:MM> UTC\\nCause: <the cause in plain language, one sentence of 25 words or fewer>\\n\\nRules:\\n- Copy the start and end times from the report. If it lists several windows, use the first start and the last end.\\n- Do not mention hostnames, ticket numbers or staff names.\"},{\"role\":\"user\",\"content\":\"Title: 2025-03-31 sessionstore unavailability\\n\\nTask: T390513\\nStart: 2025-03-31 02:58\\nEnd: 2025-03-31 03:36\\nImpact: Edits were failing for the duration of the outage.\\n\\nStarting at approximately 02:58 the sessionstore service in both datacenters became unavailable after a enough nodes had crashed due to disk exhaustion, that clients were no longer able to make quorum.\"}],\"max_completion_tokens\":256}"