Jais 3 vs Nemotron 3.5 Super VL

Jais 3

Jais 3 runs on the owner's hardware through OpenAI-compatible servers in vLLM and SGLang, with tool calls, three reasoning levels and a 512K context, from a 2.2 GB 0.9B model to a 758 GB 375B one. The weights download without sign-up under Apache-2.0, but every launch command trusts remote code, and no technical report or security contact is published.

Nemotron 3.5 Super VL

NVIDIA's free endpoint takes OpenAI-format requests with typed tool calls, JSON Schema output and an OpenAPI 3.1 file, and the weights run anywhere under a permissive licence. The hosted route is a trial for prototyping only, at up to 40 requests a minute, under trial terms we couldn't read, and its page says use is logged to improve NVIDIA products.

Jais 3

1. Start vLLM or SGLang with --reasoning-parser k2_horizon, and add --tool-call-parser k2_horizon (vLLM also --enable-auto-tool-choice) for tools, or tool calls come back as raw text
2. Pass reasoning_effort (high, medium or low) and tool_call_format inside chat_template_kwargs. Other values return a template error
3. Send each earlier assistant turn back with reasoning_content as a string, even an empty one. A missing or null thinking field makes the template raise an error
4. Send your own system message, or set default_system_prompt to an empty string. Without one the template inserts an identity prompt naming IFM, Inception42 and Cerebras
5. Budget at least 32,768 output tokens at high effort, which the cards recommend for every request

Nemotron 3.5 Super VL

1. Set chat_template_kwargs to {"enable_thinking": false} for short tasks. Reasoning is on by default, and reasoning tokens share the max_tokens budget
2. Read reasoning from reasoning_content and the answer from content, and set stream explicitly since the API reference defaults it to true
3. Don't send confidential or personal data to the hosted trial. The model page asks callers not to and says use is logged
4. Back off and retry on throttling. Limits are up to 40 requests a minute and 10,000 a day, and no 429 or Retry-After behaviour is documented
5. For production, use a partner endpoint or serve the weights. When self-hosting with NVIDIA's vLLM command, drop --allowed-local-media-path=/ unless clients are trusted