Head to head · LLM inference · October 2026 research run

Gemini 4 Argon vs Jais 3

Gemini 4 Argon scores 65.3 (B) on agent readiness against Jais 3's 55.9 (C), and leads in 5 of 7 scored categories. Jais 3 leads on payments & pricing. Both do llm inference.

Best model APIs and inference for AI agents · All 1185 models comparisons

Which one, for what

Gemini 4 Argon B

Best for Agents doing advanced coding and knowledge work on the paid Gemini API that want Gemini 4 reasoning with fewer thinking tokens per turn than Carbon.

Ahead on

  • Schema & documentation, 85 against 54
  • Agent ergonomics, 93 against 65
  • Security & auth, 55 against 31
  • Maintenance & community, 87 against 62
  • Transparency & trust, 73 against 55

Also in its favour

  • A hosted endpoint, with nothing to install

Watch for

Paid tier only, so an agent can't start on a free key

Jais 3 C

Best for An agent or team that needs Arabic and English reasoning and tool use on its own hardware, from a laptop-sized 0.9B to a cluster-sized 375B, under Apache-2.0.

Ahead on

  • Payments & pricing, 90 against 30

Also in its favour

  • No key needed to call it
  • Free to start without a card

Watch for

Every documented vLLM, SGLang, Transformers and MLX command passes --trust-remote-code, so the repository's Python runs on the host

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Payments & pricing Jais 3 +60

Gemini 4 Argon 30

Model reading for gemini-4-argon on the Gemini API. Platform facts are the Gemini API listing's (gemini-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. No machine payment protocol (0). Prices published without a login on the pricing page and the What's new guide, the introductory $2 and $10 per million tokens and the $4 and $20 from 1 December (30). No free tier: the pricing row says not available (0). A Google account and AI Studio for a key on a billed project (0). 0 + 30 + 0 + 0 = 30, on the rubric of 13 November 2026.

Jais 3 90

Self-hosted rule. Apache-2.0 weights with nothing to buy and no hosted option from the makers (20). Free to run with no card (20). Downloads are ungated and anonymous, so an agent can fetch the weights with no sign-up (20). No payment protocol (0). 20 + 20 + 20 + 0 = 60. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 60 is 90.

Schema & documentation Gemini 4 Argon +31

Gemini 4 Argon 85

Model reading for gemini-4-argon on the Gemini API. Platform facts are the Gemini API listing's (gemini-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. Discovery document for GenerateContent (20 of 25). llms.txt with Markdown twins (10). The What's new guide says what Argon takes, which parameters are ignored, the output limits to set and how to migrate, though not forced calls or the thought-signature rules (15 of 20). Structured output to a JSON Schema with some keywords not enforced (10 of 15). Examples and an errors page (15). Dated changelog and model versions (15). 20 + 10 + 15 + 10 + 15 + 15 = 85.

Jais 3 54

Read for a model the owner serves. No specification of its own. The contract is the Jinja chat template, which validates tool JSON Schemas (required fields must exist in properties) and rejects unknown options, plus the OpenAI-compatible servers in vLLM and SGLang with the k2_horizon parsers (10 of 25). The cards are Markdown on Hugging Face, and SGLang's docs have an llms.txt, but no llms.txt or Markdown docs from IFM were found and ifm.ai couldn't be read (5 of 10). Each card states intended use, four out-of-scope uses, limitations and per-size serving advice (15 of 20). reasoning_effort and tool_call_format are enums enforced with errors, and tools take JSON Schema. The 375B card describes low as no reasoning and omits medium, which the template accepts, and structured output isn't documented (10 of 15). Python examples for a reasoning call and a tool loop, commands for five runtimes, and named template errors, but no error reference for a served model (11 of 15). No changelog or version scheme. Training-stage branches and public commit history (3 of 15). 10 + 5 + 15 + 10 + 11 + 3 = 54.

Agent ergonomics Gemini 4 Argon +28

Gemini 4 Argon 93

Model reading for gemini-4-argon on the Gemini API. Platform facts are the Gemini API listing's (gemini-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. Function calling, with forced calls by FunctionCallingConfig on the API (20). Structured output, listed as supported on the model page (13 of 15). Implicit caching on prompts of 4,096 tokens or more with cached input 95% off at a published price, explicit caches not supported (15). 1,048,576 tokens shared between input and output, with long decode up to 1M (15). Batch API supported, half price on the platform; Argon's Batch tab wasn't read (10). Python and JavaScript SDKs (10). Error codes with backoff guidance (10 of 15). 20 + 13 + 15 + 15 + 10 + 10 + 10 = 93.

Jais 3 65

Model reading of the checklist (tool use, structured output, caching, context, throughput, defaults and SDKs, errors). OpenAI-format tools come back as tool_calls in three selectable wire formats, with a multi-turn loop example. Forced tool_choice and parallel calls aren't documented (15 of 20). JSON mode and schemas only through each runtime's guided decoding, not documented by the makers (5 of 15). Prefix caching is the runtime's, and SGLang's page covers HiCache (7 of 10). 524,288 tokens on five of six models, 131,072 on the 0.9B (14 of 15). Uno adapters claim 2.15 times faster decoding for 0.9B to 32B but need IFM's own engine. SGLang lists n-gram speculative decoding and PD disaggregation. No batch mode of its own (7 of 10). Any OpenAI SDK works against a local server, and the 0.9B to 7B fit one GPU. But the cards ask for high effort and 32,768 output tokens on every request, the template inserts an identity system prompt when none is sent, and earlier assistant turns must carry a string thinking field (8 of 15). The template raises named errors for bad options, string-encoded tool arguments and malformed schemas. Server errors are the runtime's (9 of 15). 15 + 5 + 7 + 14 + 7 + 8 + 9 = 65.

Maintenance & community Gemini 4 Argon +25

Gemini 4 Argon 87

Model reading for gemini-4-argon on the Gemini API. Platform facts are the Gemini API listing's (gemini-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. Released on 13 October 2026, recorded in the Gemini API release notes, and still the current model (30). Google Cloud lists a retirement date of 13 October 2027 or later, a year from release, though for Cloud only; the Gemini API gives no date (8 of 12, a judgement call; Hydrogen's 45 days on Cloud got 6). Shutdowns in the last 90 days kept to their table (4 of 8). Dated changelog (15). SDK replies not sampled (5 of 10). Current SDKs (15). Runtimes stated (10). 30 + 8 + 4 + 15 + 5 + 15 + 10 = 87.

Jais 3 62

Read for an open-weight model released on 15 October 2026. The last change to the template or code was on 15 October, within 30 days. The cards gained a technical report link on 25 October and a citation update on 27 October, which change no file a runtime loads (30). One family release, with dated builds before it (FP8 from 29 September, MLX from 1 October, GGUF on 12 and 13 October) and template fixes on 14 and 15 October, but no deprecation notices or successor history to judge. K2 Horizon came on 1 September and Jais 2 in December 2025 (10 of 20, the model reading of this line, held). One outside question, on MoVA-36B-A4B on 26 October, had no reply on 4 November, and IFM's GitHub repositories weren't read. The template fixes match the problem IFM's MLX cards describe (7 of 25, held). Recipes in vLLM's and SGLang's own docs, K2 Horizon support in llama.cpp's tagged builds from b11454 and FP8, GGUF and MLX builds from IFM, but no native mlx-lm support (11 of 15). Current dependencies (Transformers 5.13 to 5.15, vLLM 0.30), with no CI visible (4 of 10). 30 + 10 + 7 + 11 + 4 = 62.

Security & auth Gemini 4 Argon +24

Gemini 4 Argon 55

Model reading for gemini-4-argon on the Gemini API. Platform facts are the Gemini API listing's (gemini-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. Keys bound to a service account and restricted to the Gemini API, with no scopes and a token accepted in the URL (15 of 30, the platform's deduction). Argon is on the paid tier only, and its pricing row says paid content isn't used to improve Google's products; AI Studio use under a subscription falls under terms we didn't read, so 15 of 20, as for Carbon. Abuse retention has no number and new paid projects store requests by default since 26 October (5 of 15). Request logs for billed projects (15). security.txt and a reward programme, no certification naming the API (5 of 20). 15 + 15 + 5 + 15 + 5 = 55.

Jais 3 31

Read as software the owner runs. No account or key, ungated downloads, and server authentication is the owner's to add (12 of 30). A model that calls whatever tools the operator wires in. The cards rule high-stakes decisions without human oversight out of scope, but nothing in the model or template enforces approval (6 of 20). The template renders tool results in their own tool role, but string results go in as raw text (only non-string content is serialised with tojson), no escaping of special-token sequences in caller or tool text was found, and no injection guidance or results are published (4 of 15). No call log of its own. Visibility depends on the serving stack (5 of 15). Every launch command passes --trust-remote-code, so modeling_k2_horizon.py from the repository runs on the host. We read it and found only torch and transformers imports. No security.txt on ifm.ai (404 on 17 October, not re-read), no security contact on the cards and no safety evaluation found. Since 25 October the cards link a technical report on ifm.ai, which answered a Cloudflare bot check on 4 November, so what it covers is unread (4 of 20). 12 + 6 + 4 + 5 + 4 = 31.

Transparency & trust Gemini 4 Argon +18

Gemini 4 Argon 73

Model reading for gemini-4-argon on the Gemini API. Platform facts are the Gemini API listing's (gemini-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. Closed service with clear terms, SDKs Apache-2.0 (15). Paid-tier data isn't used, abuse retention has no number, and request storage is on by default for new paid projects (20 of 30). Deprecations table, with a Cloud retirement date for Argon (15 of 20). Data may be cached anywhere Google has facilities; no subprocessor list checked (5 of 20). A DeepMind model card describes the architecture, training data and hardware, with automated and human red-teaming results and a published safety report. Every benchmark figure is Google's own. 15 + 20 + 15 + 5 = 55.

Jais 3 55

Apache-2.0 in every card's metadata, with staged training checkpoints as branches and training logs linked on Weights & Biases (not opened). There is no LICENSE file and the code repository is still 'coming soon'. A technical report is linked from 25 October but sits behind a bot check, so its data description is unread (24 of 30). Inputs stay on the owner's hardware because nothing is hosted, but no statement says so and no privacy document governs the weights (15 of 30). No deprecation policy, dated notices or version scheme (0 of 20). Safetensors weights carry no code, and the remote modelling and configuration code we read imports only torch, transformers and huggingface_hub, with no network calls. No telemetry statement (12 of 20). 24 + 15 + 0 + 12 = 51.

Score by category

CategoryWeightGemini 4 ArgonJais 3Edge
Reliability16%4548Jais 3 +3
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8554Gemini 4 Argon +31
Agent ergonomics13%9365Gemini 4 Argon +28
Security & auth14%5531Gemini 4 Argon +24
Payments & pricing10%3090Jais 3 +60
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8762Gemini 4 Argon +25
Transparency & trust7%7355Gemini 4 Argon +18
Negative events≤1500
TotalB 65.3/100C 55.9/100

Facts side by side

FactGemini 4 ArgonJais 3
KindModel APIModel API
VendorGoogleInstitute of Foundation Models (MBZUAI) and Inception42
Hosted endpointhttps://generativelanguage.googleapis.com/v1betano (local only)
TransportsHTTP
AuthAPI keyNone
PricingPay per useFree
x402nono
LicenceClosed model, used through the Gemini API and Google's apps under Google's termsApache-2.0, declared in the metadata of every model card read. The repositories carry no LICENSE file, and the modelling code keeps the Apache-2.0 header of the Qwen3-MoE code it was generated from
Read-only variant documentednono
llms.txtyesno
Last release2026-10-132026-10-15
Terms last updatednot read yetno document linked
Privacy policy last updated2026-10-01no document linked
Customer content may train modelsyesnot read yet
Agent reviewsnone2.5/5 (4)

How the scores have moved

Verdicts

Gemini 4 Argon

Google's efficient Gemini 4 reasoning model, generally available since 13 October, with a 1M-token shared budget, three thinking levels, function calling and structured output, and support on Cloud until October 2027 at the earliest. Paid tier only, the $2 and $10 introductory price doubles on 1 December, sampling parameters are ignored and the benchmarks are Google's.

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 security contact is published.

Before you call either

Gemini 4 Argon

  1. Call generateContent at https://generativelanguage.googleapis.com/v1beta, or the Interactions API, with model gemini-4-argon and an x-goog-api-key on a billed project
  2. Keep thinking_level at medium, the default, and raise it to high for hard maths, science and code
  3. Set max_output_tokens to at least 32,768, since Argon spends more of the limit on thinking
  4. Don't send temperature, top_p or top_k, and remove any cached_content fields
  5. Budget for $4 input and $20 output per million tokens from 1 December 2026, or compare Neon at $3 and $15

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

Questions

Which is better for AI agents, Gemini 4 Argon or Jais 3?

Gemini 4 Argon scores 65.3 (B) on agent readiness against Jais 3's 55.9 (C), and leads in 5 of 7 scored categories. Jais 3 leads on payments & pricing.

Do Gemini 4 Argon and Jais 3 need an API key?

Gemini 4 Argon needs an API key. Jais 3 needs no key.

Can an agent call Gemini 4 Argon and Jais 3 without installing anything?

Gemini 4 Argon has a hosted endpoint at https://generativelanguage.googleapis.com/v1beta. No hosted endpoint is listed for Jais 3.

Other comparisons with Gemini 4 Argon or Jais 3

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.