Written as we built Kept, in the order things happened, so it reflects what a first-time builder actually goes through. Times are from our notes on Oct 24, 2026.
What worked
- Signing in with Google was quick, and the contact-details step verified our email with a 6-character code that arrived within a minute.
- The console's landing page shows a copy-paste OpenAI-SDK snippet with the base URL and the
NEBIUS_API_KEYvariable. For anyone who has used the OpenAI SDK, the mental model is instant. - The "zero data retention" option is offered during profile setup, before you've sent a single prompt. For a personal assistant that reads someone's inbox, that is exactly when the question should be asked. We switched it on, and it became part of our privacy story.
What needs work
- A card is required before hackathon credits can be used. The FAQ says promo credits come through a form and the Builders Program, but the console shows a mandatory "Billing details" screen (address + card) before anything else. Builders who expect "free credits" are surprised here. A line on the Devpost resources page ("you'll need to add a card; it's a $0 authorization") would remove the surprise.
- The promo-code form is easy to miss. The "Fill out this form" link opens nebius.com/promo-code, where the first thing that renders is a newsletter sign-up; the real promo form loads later inside an embedded frame further down. On our first visit we gave up thinking the page was broken. Once found, it worked: "Form submitted. The promo code will be emailed to you." It would help if the console simply had a "Redeem a code" box next to the trial balance.
- Two different "verify your email" flows (Builders Program and Token Factory) arrive with the same subject line. Different subjects would help.
- The billing form clears street, city and postal code when you change the country, and only then shows the State field. Filling the country first avoids it, but nothing tells you that.
What worked
/v1/modelslists the Nemotron family with stable IDs (nvidia/NVIDIA-Nemotron-3-Nano-30B-A3B,nvidia/nemotron-3-super-120b-a12b,nvidia/Nemotron-3-Ultra-550b-a55b), so Kept discovers the models at start-up instead of hard-coding them. Note the inconsistent casing between the three IDs; we match case-insensitively.response_format: json_objectis honoured by all three sizes.- Latency was good: Nano answers in under a second with reasoning off, Super in 2-8 s, Ultra in roughly 5-15 s for a real decision.
- Super and Ultra return their reasoning in a separate
reasoning_contentfield. We store Ultra's reasoning next to its decision so the owner can see why it proposed moving a deadline.
What needs work
- Hidden reasoning can eat the whole answer. Our first live run of Nano with
max_tokens=200came back withfinish_reason: length, emptycontentand emptyreasoning_content, while usage showed all 200 tokens spent. Nothing in the response says the tokens went to reasoning. Passingchat_template_kwargs: {"enable_thinking": false}fixed it: 34 tokens, 0.8 s. A line in the quickstart ("Nemotron 3 reasons by default; budget for it or switch it off") would have saved us an hour. The/no_thinksystem prompt andreasoning_effort: lowdid not help.
An outage the status page didn't show. On Oct 24 from about 12:45 to 12:58 UTC, chat completions
for all three Nemotron sizes returned 503 Service Temporarily Unavailable (an nginx page) on and off,
while /v1/models answered 200 and status.nebius.com showed Token Factory as operational. Our trial
balance was fine. Kept handled it the way we'd hoped: each job failed on its own, nothing was invented,
and the dashboard kept showing the last good morning. A status entry would have saved us from wondering
whether our account was the problem.
Nano (reasoning off) was good enough wherever the job is narrow and code checks the answer: sorting mail into a handful of labels, and spotting the promise in a reply the owner is about to send. Pulling promises out of a whole email thread was another matter: in live runs the quality wasn't there, so we moved extraction to Super. Nano also shouldn't be trusted with dates: "by Friday" came back as a Tuesday once. Now code works out every date from the words.
Super writes emails that sound like a person, and we use it for every draft and for the
morning brief. Two quirks came up in live runs: now and then the JSON came back as a Python-style
dict (single quotes, True), and sometimes it greeted the sender instead of the recipient. Both
are caught in code now.
Ultra was worth its price only for the rare decisions where a wrong call costs money or
trust: what a signed contract covers, which deadline can move, whether an offer is a good idea at
all. Its reasoning_content is the most useful thing it returns. We show it to the owner next to
each proposal ("How Nemotron Ultra weighed it"). It still needs a short leash:
- it once invented an email address for the person it wanted to write to;
- asked to find patterns in a history of promises, it picked five convenient examples and reported "5 of 5 late". We now make it describe the pattern and let code count every match;
- in our first two evaluation runs (about 15 Ultra calls) one reply was invalid JSON and a decision was lost; Kept now retries once.
Super VL (nvidia/Nemotron-3.5-Super-VL) reads a client's kitchen photo well: the cabinet style,
the damage, what the picture can't show, and rough sizes that are good enough for a preliminary
estimate. Two things we'd flag: with reasoning on, it spent a 1,500-token budget thinking and
returned nothing (same lesson as Nano: enable_thinking: false gave a clean JSON answer in about
8 seconds), and we couldn't find its price on the model catalog page, so our cost display assumes
Super's price for it.
Cost and speed. A full morning for a one-person business is 46-59 calls and costs $0.065-0.11 (median $0.077 over dozens of graded runs). With the independent parts running side by side it takes one to two and a half minutes, which is fine for a job that runs before the owner wakes up. Over two days we made a few thousand calls across 51 graded mornings and hundreds of graded client emails; apart from the short 503 window above, Token Factory never failed us.
Yes. Having three sizes of one model family behind one OpenAI-compatible endpoint meant routing by job was a one-line change, and the whole product costs a few cents a day to run. What we'd ask for: say in the quickstart that Nemotron 3 reasons by default, and put a "redeem a code" box in the console.