Jais 3 vs Vertex AI (Gemini Enterprise Agent Platform)

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.

Vertex AI (Gemini Enterprise Agent Platform) 97

Model reading. OAuth 2.0 with IAM roles and service accounts, which the docs recommend for production, with API keys for testing. No key in a query string found in the docs we read (30). The training restriction in the Service Specific Terms says Google won't use customer data to train or fine-tune any model without permission, GA and pre-GA alike (20). Default in-memory caching for 24 hours that can be disabled, flagged prompts logged up to 90 days unless an abuse-monitoring exception is granted or the customer has a Cloud Master Agreement, the Interactions API storing by default, and Claude Fable 5 and Mythos 5 requiring 30-day retention shared with Anthropic (12 of 15, a judgement call matching the Fable exception on the Anthropic and Bedrock listings). Cloud Audit Logs, with Data Access logs off until enabled, and optional request-response logging to BigQuery (15). google.com security.txt valid to 2030-04-01, the Google VRP, and Generative AI on the platform in ISO 27001, 27017 and 27018 and SOC 1, 2 and 3 scope per the 1 October services-in-scope check for vertex-ai-tuning, not re-read on 6 October (20).

Jais 3 48

Read with the local-software lines, since the owner serves the weights. Ungated weights on Hugging Face with stated runtimes (vLLM 0.30.0 or later, SGLang 0.5.20 or later, Transformers validated at 5.15.0, mlx-lm with shipped model code), but every launch command trusts remote code. The GGUF card still says to build llama.cpp from master or wait for a release, though llama.cpp's own tags carry K2 Horizon support from b11454 (6 October 2026) (16 of 20, held). No CI or test suite of the makers' was found, and the code repository is 'coming soon'. SGLang's cookbook reports a validation pass of the tool-call parser on all six checkpoints, and IFM's MLX cards describe conversion checks against the PyTorch code (3 of 25). No crash reports. On 4 November the six main repositories held seven discussions, six of them closed citation updates and one open MoVA-36B-A4B thread from 26 October with no reply yet. Two template fixes for OpenAI-style message history landed on 14 October, before the launch (15 of 25). No changelog or version tags, only public commit messages (2 of 15). Released as named final checkpoints with no preview label, though mlx-lm v0.32.2 still has no K2 Horizon model code of its own (12 of 15). 16 + 3 + 15 + 2 + 12 = 48.

Vertex AI (Gemini Enterprise Agent Platform) 99

Google Cloud status dashboard with per-product history (20). Its incident feed, read on 6 November, has no incident naming Vertex Gemini API, Gemini or the Agent Platform in the 90 days. The regional incidents of 20 August, 1 September and 20 October (europe-west2) and the Cloud Storage incident of 8 and 9 October didn't list it among affected products (30). Standard PayGo publishes usage tiers by 30-day spend with baseline throughput, 2,000,000 to 50,000,000 tokens a minute for Flash models and 500,000 to 10,000,000 for Pro, plus quota tables for other methods (15). A 429 page says to use the global endpoint and truncated exponential backoff, and a retry-strategy page (15). SLA of 99.5 per cent a month on generateContent and streamGenerateContent, 95 per cent for short-term availability models, and a latency SLO on Provisioned Throughput. The 429 page says pay-as-you-go 429s don't count toward the SLA error rate (10). Gemini 4 Argon reached GA on 13 October and Gemini 3.8 Flash moved to the 12-month tier, and the v1 API, 3.5 Flash-Lite and Claude Opus 5.5 are GA, but express mode was Preview at the 6 October check (9 of 10, up from 8). Up from 98 on 6 October.

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.

Vertex AI (Gemini Enterprise Agent Platform) 94

Model reading. Keyless discovery document for the Agent Platform API v1, revision 20260930, with 1,128 methods and 1,493 schemas (25). No llms.txt, but every docs page answers as Markdown at .md.txt, counted as for vertex-ai-tuning (10). Model cards give limits, capabilities and retirement dates, and the 3.8 Flash card says when to use 3.7 Flash instead, but the docs mix the Vertex AI and Agent Platform names, and the OpenAI page tells new users to call the Gemini Developer API instead (16 of 20). Structured output with response_schema and response_mime_type: application/json always follows the schema per the docs, and complex schemas fail with a 400 (15). Examples on every page and a 429 guide, but we found no full error code list for generateContent (13 of 15). Versioned v1 and v1beta1 APIs and release notes with entries on most working days, newest 5 November 2026 (15).

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.

Vertex AI (Gemini Enterprise Agent Platform) 90

Closed service under the Google Cloud terms, with the Gen AI SDKs under Apache-2.0 and a public discovery document (18, as for Bedrock's open service models). The zero data retention and abuse monitoring pages agree with the Cloud terms and give periods for each case, 24 hours in memory, up to 90 days for flagged prompts, 30 days for Advanced AI models, 3 days for Search grounding logs and 30 days for Maps grounding, and say which can't be switched off (27 of 30). A dated model versions table with release and retirement dates and a stated 12-month or 45-day policy, but on 6 November it still listed Gemini 2.5 Pro, Flash and Flash-Lite as available with a 20 October 2026 retirement date and left them out of the retired table (18 of 20, down from 20). The Cloud subprocessor list with locations, per the 1 October vertex-ai-tuning check, regional and multi-region endpoints, and per-model ML processing locations on the partner model cards (20).

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.

Vertex AI (Gemini Enterprise Agent Platform) 97

Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Function calling with FunctionCallingConfig mode ANY and allowedFunctionNames to force a named tool (20). Schema-guaranteed JSON output (15). Implicit and explicit context caching, cached input at 0.1x, $0.075 per million on 3.8 Flash through 31 December (15). 1,048,576-token context on 3.8 Flash, a unified 1,048,576-token input and output limit on Gemini 4 Argon, and 1,000,000 on Claude Opus 5.5 (15). Flex/Batch at half price on Gemini (10). Gen AI SDKs for Python and JavaScript among others, and the OpenAI libraries work with Google Cloud auth (10). 429 handling documented per quota framework, with standard Google status codes elsewhere (12 of 15).

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.

Vertex AI (Gemini Enterprise Agent Platform) 91

Model reading. Gemini Omni 1.2 Flash GA on 5 November, Grok 4.7 GA on 27 October, Gemini 4 Argon GA on 13 October and Claude Haiku 5.5 on 7 October 2026 (30). Stable models stay at least 12 months, and since 6 October Gemini 4 Argon and Gemini 3.8 Flash are in that tier, while 3.7 and 3.6 Flash remain short-term with at least 45 days' notice once a date is set (10 of 12, up from 8). Gemini 2.5 Pro, Flash and Flash-Lite were due to retire on 20 October, three models on one date after more than 12 months, with replacements named. We didn't check partner model retirements (6 of 8, down from 8). Dated release notes on most working days, newest 5 November, and Cloud Customer Care (15). python-genai replies not sampled this run (5 of 10). Current SDKs, google-genai 3.0.0 on 6 November and @google/genai 3.0.0, and google-cloud-aiplatform 2.7.0 on 28 October 2026 (15). Supported runtimes stated, Python 3.10 or later and Node 20 or later, per the 6 October check (10). Unchanged at 91.