Jais 3 vs Router.com (Ramp Router)

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.

Router.com (Ramp Router)

Detailed Markdown docs with typed error codes, per-model capability data and routing an agent can set per request. No OpenAPI document, status page, changelog or published rate limits were found. Signup needs a US business email in a browser, and Ramp records prompts and outputs for a year by default unless switched off.

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

Router.com (Ramp Router)

1. Switch off content recording in Settings before sending private data. It is on by default and keeps prompts and outputs for a year
2. Read model ids from GET /v1/models at runtime. Ids are account-specific, an unknown one is a 404, and Gemini ids need your own Google key
3. Use POST /v1/responses with a models list for fallbacks. Router stops falling back once a stream has started
4. Set fallback_timeout and provider_timeout, or allow_flex_tier: false, when latency matters. Flex routing is on by default
5. Treat both 401 invalid_api_key and 401 api_key_deactivated as a possibly locked key, and stop retrying on 402