Sume SDK: try/catch misses a 402, generated calls return { error }

With @sume-com/sdk, a generated operation such as generateVideoV1 or listFormats returns an object with data, error and response; it does not throw on an HTTP error status, so a try/catch around it will not catch a 402 insufficient_credits or a 429 rate_limited. Check error after every call. The package README shows the pattern: destructure { data: submitted, error }, then if (error) throw ... (TypeScript SDK).

The helpers behave differently on purpose. waitForJob throws SumeJobRequestError when a status read fails and SumeJobTimeoutError when the deadline passes, but it resolves, not throws, for a failed or canceled job, since that is a result you asked for.

What does a safe call look like?

Check error first, read response.status for the HTTP code, and take the code and request id from the error envelope.

import { createSumeClient, generateVideoV1, waitForJob } from "@sume-com/sdk";

const client = createSumeClient({ apiKey: process.env.SUME_API_KEY! });

async function main() {
  const { data, error, response } = await generateVideoV1({
    client,
    headers: { "idempotency-key": "mug-clip-v1" },
    body: { prompt: "Slow push-in on a ceramic mug", mode: "async" },
  });
  if (error || !data) {
    const e = (error as { error?: { code?: string; request_id?: string } })?.error;
    throw new Error(`submit ${response?.status} ${e?.code} ${e?.request_id}`);
  }
  const job = await waitForJob(data.data.request_id, { client });
  console.log(job.status);
}

main().catch((err) => {
  console.error(err);
  process.exitCode = 1;
});

Which outcomes throw and which return?

What does the client retry for you?

The client created with createSumeClient retries 408, 429 and 5xx responses and transport failures, twice by default, with exponential backoff and jitter, and honors retry-after. It only replays a POST when you supplied an Idempotency-Key, since replaying a create without one could start and bill a second job. That is one more reason to always pass the header on creates.

What should you do about it?

• Wrap generated calls in one helper that throws on error, so a missed check cannot become a silent undefined.
• Branch on the error code and retryable, not on the message text.
• Log the request_id from the envelope on every failure.