Head to head · LLM inference · October 2026 research run

GPT-6.2 Astra vs Nemotron 3.5 Super VL

GPT-6.2 Astra scores 85.8 (AA) on agent readiness against Nemotron 3.5 Super VL's 61.6 (C), and leads in 6 of 7 scored categories. Nemotron 3.5 Super VL leads on payments & pricing. Both do llm inference.

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

Which one, for what

GPT-6.2 Astra AA

Best for Long, demanding reasoning, coding and computer-use work through the Responses API.

Ahead on

  • Reliability, 75 against 58
  • Schema & documentation, 100 against 74
  • Agent ergonomics, 98 against 65
  • Security & auth, 100 against 54
  • Maintenance & community, 87 against 71
  • Transparency & trust, 90 against 58

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

Tool calling works only through the Responses API, not Chat Completions

Nemotron 3.5 Super VL C

Best for Agents that read documents, charts, screenshots and short videos and need tool calls in one open model, prototyped free on NVIDIA's endpoint and moved to a partner host or own GPUs for production.

Ahead on

  • Payments & pricing, 53 against 45

Also in its favour

  • Free to start without a card

Watch for

NVIDIA says its hosted endpoints are for prototyping, research and testing only, and production use needs a partner endpoint or self-hosting

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.

Security & auth GPT-6.2 Astra +46

GPT-6.2 Astra 100

Model reading for gpt-6-2-astra on the OpenAI API. Platform facts are the OpenAI API listing's (openai-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. Model reading. Project keys with All, Restricted (per-endpoint None, Read or Write) and Read Only permissions, service accounts, and mutual TLS with X.509 workload identity GA since 26 August, per the 1 October check. The changelog adds project key expiry dates on 10 September, key-creation controls on 15 September and, on 21 October, organisation and project settings that limit which service tiers a project may use (30). API data not used for training unless the customer opts in, since 1 March 2023 (20). Abuse-monitoring logs kept up to 30 days, and Zero Data Retention or Modified Abuse Monitoring by approval. The data-controls guide re-read on 1 November lists Chat Completions, Responses, Decisions and ten other endpoints as ZDR-eligible; /v1/agents, Conversations, Files and vector stores aren't (15). Usage and Costs filter by API key since 4 August, with Admin APIs to match, and audit logs for enterprise (15). SOC 2 Type 2, ISO 27001, 27017, 27018, 27701 and 42001 per the 1 October check, not re-read on 1 November, a Bugcrowd bug bounty and a coordinated disclosure policy, both linked from a signed security.txt. That security.txt had no Expires field on 27 October, which RFC 9116 requires, so the disclosure policy carries this line. It wasn't re-read on 1 November (20). For GPT-6.2 Astra the GPT-6.2 guide, read 18 November, says ZDR is available to approved organisations on eligible endpoints, with US and EU data residency.

Nemotron 3.5 Super VL 54

Model reading. nvapi- bearer keys sent in a header. NVIDIA's NGC docs say personal keys are limited to the services and role chosen at creation and take an expiry, and service keys can be scoped to actions (25 of 30). Inference only, with no write operation, but no zero-retention option for the hosted trial was found, and the model page asks callers not to send confidential or personal data (8 of 20). The model reads web pages, PDFs and images an agent passes it, and NVIDIA publishes safety, bias and privacy subcards, but no prompt-injection guidance or results were found (5 of 15). No per-call log for API callers was found, only rate limits shown in the account (3 of 15). NVIDIA PSIRT runs coordinated disclosure and publishes security bulletins, linked from the card, the reading nvidia-nemo-retriever and nemo-guardrails give the same programme (13). www.nvidia.com/.well-known/security.txt answered 403 per the 2 November check and build.nvidia.com has none, and no certification or bug bounty for the API catalogue was found (13 of 20). 25+8+5+3+13 = 54.

Agent ergonomics GPT-6.2 Astra +33

GPT-6.2 Astra 98

Model reading for gpt-6-2-astra on the OpenAI API. Platform facts are the OpenAI API listing's (openai-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Tool use with parallel calls and forced tool choice, 18 of 20 because GPT-6 Astra, GPT-6.1 Sol and GPT-6.1 Terra call tools only through the Responses API (18). Strict structured outputs (15). Automatic prompt caching with cached input at 0.1x on Astra and Luna ($0.01 per million on Luna) and 0.05x on GPT-6.1 Sol ($0.10) and GPT-6.1 Terra ($0.05), and a 12-hour cache lifetime in the Responses API since 20 October (15). 1.05M context on Astra, GPT-6.1 Sol, GPT-6.1 Terra and Luna (15). Batch at half price (10). Official SDKs in Python, JavaScript and more (10). Documented error codes with retry guidance (15). For GPT-6.2 Astra, read 18 November: tool calling only through the Responses API, the same 18 of 20; 1.05M context and 128K output; cached input $0.40, 0.05x input; Batch half price. Tool search and Skills are supported in Responses, recorded in details without points, as for the Claude API.

Nemotron 3.5 Super VL 65

Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). OpenAI-format tools, tool_choice auto, none, required or a named function, and parallel calls on by default (20 of 20). response_format with json_schema and strict in the OpenAPI file. Not tested by us (12 of 15). The card describes prefix caching for self-hosted serving, but no caching on the hosted endpoint is documented (2 of 10). 1M tokens in the weights, but the hosted page lists 262K, and completions are capped at 131,072 tokens (12 of 15). No batch mode (0 of 10). Any OpenAI SDK works with the base URL, and NVIDIA maintains langchain-nvidia-ai-endpoints. Only messages is required, but reasoning defaults to on at high effort and the reference defaults stream to true (10 of 15). Errors carry a message, type and request id, with no 429 or rate-limit body documented (9 of 15). 65.

Transparency & trust GPT-6.2 Astra +32

GPT-6.2 Astra 90

Model reading for gpt-6-2-astra on the OpenAI API. Platform facts are the OpenAI API listing's (openai-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). The data-controls guide, re-read on 1 November, gives retention periods per endpoint, the training default and the ZDR route. The DPA, effective 1 January 2026, commits to return or deletion of customer data on termination, 30 days to object to a new subprocessor, and SCCs with the UK Addendum for transfers, and nothing in it conflicts with the guide, per the 4 October check, not re-read on 1 November (30). Deprecations page with announcement and shutdown dates, and GET /v1/models returns each model's shutdown_date (20). The subprocessor list, updated 9 July 2026, names its third-party subprocessors and OpenAI affiliates with the processing countries for each and a form to get notice of new ones, and data residency regions are listed, per the 4 October check, not re-read on 1 November (20).

Nemotron 3.5 Super VL 58

Weights under OpenMDW-1.1, a short permissive licence from the Linux Foundation with no field-of-use limits, but not an OSI licence. Datasets and training recipes are released. The hosted trial is under terms we couldn't read, and the OpenAPI file names a different model licence and the AI Enterprise EULA (22 of 30). NVIDIA's privacy policy (22 September 2025) doesn't address API prompts. The model page says use is logged for security and to improve NVIDIA products, with improvement data not linked to identity, and gives no retention period. The trial terms that may say more were unread (8 of 30). No deprecation policy or dated notices for catalogue models. The page carries an isDeprecated flag only (3 of 20). The quickstart says hosted endpoints run on NVIDIA DGX Cloud, but no subprocessors or data locations for the catalogue were found (5 of 20). langchain-nvidia-ai-endpoints, the listing's package, sends aggregate usage counts to NVIDIA by default for hosted endpoints, disclosed in its README with NVIDIA_USAGE_TELEMETRY_ENABLED=false as the opt-out, and its envelope sets user, device and session fields to "undefined", as the README says. Disclosed, so no term. 22+8+3+5 = 38.

Schema & documentation GPT-6.2 Astra +26

GPT-6.2 Astra 100

Model reading for gpt-6-2-astra on the OpenAI API. Platform facts are the OpenAI API listing's (openai-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. Official OpenAPI document (openapi.yaml and openapi.json) in the openai/openai-openapi repository, whose openapi.yaml (version 2.3.0, updated 31 October) lists gpt-6.1-terra (25). llms.txt index with per-product files, and every docs page has a Markdown twin at .md (10). The reference documents each parameter, and model pages say which model fits which job (20). Structured outputs with strict: true on schemas and function tools (15). Error codes guide with types and recovery advice, now with a 400 service_tier error for tiers a project doesn't allow (15). Dated model snapshots and a dated changelog, last entry 30 October (15).

Nemotron 3.5 Super VL 74

Model reading. An OpenAPI 3.1 file for this model's /chat/completions on docs.api.nvidia.com, with typed request and response schemas (25). build.nvidia.com/llms.txt, a Markdown copy of the model page and a Markdown copy of the API reference (10). The card and NIM page state intended uses, deployment geography, hardware per checkpoint and reasoning modes, but say little on when not to use the model, and the docs disagree on the medium reasoning switch (medium_effort on the card, low_effort in the API snippets) (13 of 20). Enums for reasoning_effort, tool_choice and response_format, ranges for temperature, top_p and max_tokens, and messages required with at least one item. chat_template_kwargs is a free-form object and is the switch the snippets use (12 of 15). Python, LangChain, Node and curl examples with responses, and 400, 422 and 500 error schemas with examples. No 429 (11 of 15). No changelog for the catalogue or the model. The OpenAPI version is 1.0.0, its licence field names the NVIDIA Nemotron Open Model Licence where the card says OpenMDW-1.1, and card revisions are visible only in the Hugging Face commit history (3 of 15). 74.

Reliability GPT-6.2 Astra +17

GPT-6.2 Astra 75

Model reading for gpt-6-2-astra on the OpenAI API. Platform facts are the OpenAI API listing's (openai-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. Status page at status.openai.com with component history (20). Two API-wide majors in the 90 days to 1 November, elevated errors across ChatGPT, Codex and the API (the Agents API included) on 29 September, with Chat Completions, Responses, Batch, Realtime, Embeddings, Images, Files and the other API components degraded from 17:52 to 23:14 UTC, and elevated error rates across API models on 17 September, with eleven components degraded from 20:20 to 21:20 UTC. Two majors give 5 of 30. The 25 July incident is now outside the window. The 29 September write-up, posted on 6 October, traces it to a feature rollout that exhausted shared network connection capacity. Every other incident since 3 August that lists an API component is partial or under an hour, so minor. Degraded performance across ChatGPT, Codex and the APIs on 21 October listed every API component but ran 22 minutes (02:26 to 02:48 UTC). Single-model incidents were GPT-5.6 Sol errors on 11 September (09:08 to 11:21 UTC), gpt-5.6-luna errors on 21 October (70 minutes) and GPT-6.1 Sol degraded performance on Batch, Chat Completions and Responses on 27 October (78 minutes). Partial incidents were latency for some Responses requests on the US endpoint on 31 August and 1 September, image generation where some requests failed on 8 September, latency for some Responses and Chat Completions requests on 30 September, large-PDF errors in Responses and an Agents API computer use incident on 6 October, Responses errors for users in India, Japan and Korea on 22 October and errors on some GPT Image 2 edit requests on 30 October (14:35 to 18:36 UTC). Image model incidents on 16 September and 14 October and file download errors on 19 October each ran about 40 minutes. FedRAMP errors for Astra and Sol on 21 October and authentication errors near Illinois on 20 October list no API component. Rate limits published per tier and model family with rate-limit headers (15). 429 guidance, re-read on 1 November, covers Retry-After as a minimum wait, backoff with jitter when it's missing, a gradual ramp, and splits slow_down (429) from server_is_overloaded (503) (15). Scale Tier carries a 99.9% uptime SLA, through sales, per the 1 October check, not re-read on 1 November (10). Responses and Chat Completions are GA (10). 20 + 5 + 15 + 15 + 10 + 10 = 75. The model page, read 18 November, lists GPT-6.2 Astra with no preview label and its own rate limits, Build 5,000 requests and 1M tokens a minute, Launch 10,000 and 4M, Grow 15,000 and 40M.

Nemotron 3.5 Super VL 58

Hosted reading, for NVIDIA's trial endpoint. status.ngc.nvidia.com is a Statuspage site with NVIDIA Build and Cloud Functions components and a readable history (20). In the 90 days to 4 November, re-read from history.atom, two incidents, both minor for an API caller, and none posted since 29 September. SMS verification for NVIDIA Build was unavailable in China from 23 to 29 September, which affects sign-up, and on 10 August new Cloud Functions deployments failed for about three hours while existing deployments kept running (20). build.nvidia.com gives limits of up to 40 requests a minute and 10,000 a day, and says they vary by model and with other users' traffic (12 of 15). The OpenAPI file documents a 202 pending result with an NVCF-REQID to poll, but no 429, Retry-After or backoff guidance, and NVIDIA's FAQ says to expect long waits under load (3 of 15). No SLA for the trial. NVIDIA's SLAs come with AI Enterprise for self-hosted software (0). The card says v1.0 GA, but the hosted page calls the model early access and NVIDIA calls the catalogue a trial for prototyping only (3 of 10). The model page re-read on 4 November still says early access, with a free endpoint marked available and 40 rpm. 20+20+12+3+0+3 = 58.

Maintenance & community GPT-6.2 Astra +16

GPT-6.2 Astra 87

Model reading for gpt-6-2-astra on the OpenAI API. Platform facts are the OpenAI API listing's (openai-api, re-read 1 November), carried over as RULES.md allows for a model on an already graded platform. Model reading. GPT-6 Rosalind, a life-sciences model for approved organisations, launched on 30 October, after GPT-6.1 Terra on 26 October and the Decisions API GA on 22 October (30). Published minimum notice of 6 months for GA models, 3 months for specialised variants, as little as 2 weeks for previews. On 14 October GPT-4o (gpt-4o-2024-08-06, gpt-4o-2024-11-20), GPT-4o mini, GPT-4.1 and GPT-4.1 mini were given a shutdown date of 14 January 2027, 92 days, with no safety or compliance reason stated. These are GA models, so the page's own 6-month minimum wasn't kept, as with gpt-5.4-cyber's 20 days in September. 8 of 12, the award for a minimum of two to three months in practice. Five shutdown dates in the 90 days to 1 November, the Assistants API on 26 August (announced in August 2025), gpt-5.2-chat-latest and gpt-5.3-chat-latest on 10 August (announced 8 May), gpt-3.5-turbo-instruct, babbage-002, davinci-002 and gpt-3.5-turbo-1106 on 28 September (announced 26 September 2025, missed in the 27 October count), gpt-5.4-cyber on 1 October and the legacy snapshots on 23 October (announced 22 April). Sora 2 and the Videos API (24 September) are scored on the openai-sora listing. Four of the five kept the published notice, so 4 of 8 as before, as amazon-bedrock has for four dates after full notice. Dated changelog several times a month and a help centre (15 of 15). openai-python had 215 open issues per the 1 October check, replies not sampled (5 of 10). Current official SDKs, openai 3.42.0 on PyPI (31 October) and npm openai 7.47.0 (15). Supported runtimes stated, Python 3.10 or later and Node 22 or later, the npm package's engines re-read on 1 November (10). GPT-6.2 Astra and Sol launched on 17 November, the newest model change on the platform.

Nemotron 3.5 Super VL 71

Released on 15 October 2026. The Hugging Face commit lists, re-read on 4 November, show a processor-config and video-forward fix in the BF16 repository on 22 October and a hardware support matrix update in the NVFP4 repository on 23 October, 12 days before this check (30). NVIDIA released three Nemotron 3.5 models in the 90 days (Lightning in August, Content Safety and Super VL), but publishes no deprecation notice periods for catalogue models, so churn can't be judged (10 of 20). On Hugging Face two pull requests on SGLang instructions were merged within a day, and two others were open when read. Support for the free tier is the developer forum (15 of 25). NVIDIA maintains langchain-nvidia-ai-endpoints (1.5.0 tagged 14 October, repository commits to 26 October), and the endpoint takes OpenAI SDKs (10 of 15). Day-one recipes for vLLM 0.32.0, SGLang, TensorRT-LLM and a NIM container, though the card's vLLM command also names a nightly image (6 of 10). 30+10+15+10+6 = 71.

Score by category

CategoryWeightGPT-6.2 AstraNemotron 3.5 Super VLEdge
Reliability16%7558GPT-6.2 Astra +17
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%10074GPT-6.2 Astra +26
Agent ergonomics13%9865GPT-6.2 Astra +33
Security & auth14%10054GPT-6.2 Astra +46
Payments & pricing10%4553Nemotron 3.5 Super VL +8
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8771GPT-6.2 Astra +16
Transparency & trust7%9058GPT-6.2 Astra +32
Negative events≤1500
TotalAA 85.8/100C 61.6/100

Facts side by side

FactGPT-6.2 AstraNemotron 3.5 Super VL
KindModel APIModel API
VendorOpenAINVIDIA
Hosted endpointhttps://api.openai.com/v1https://integrate.api.nvidia.com/v1
TransportsHTTP
AuthAPI keyAPI key
PricingPay per useFree
x402nono
LicenceClosed model, used through the OpenAI API under OpenAI's Services AgreementOpenMDW-1.1 for the weights (permissive, not an OSI licence). The hosted trial endpoint is under the NVIDIA API Trial Terms of Service, and the NIM container under the NVIDIA Software Licence Agreement
Read-only variant documentednono
llms.txtyesyes
Last release2026-11-172026-10-15
Terms last updatedcouldn't be readnot read yet
Privacy policy last updatedcouldn't be readno date given
Customer content may train modelscouldn't be readnot read yet
Terms restrict automated accesscouldn't be readnot read yet
Terms restrict benchmarkingcouldn't be readnot read yet
Terms or service can change without noticecouldn't be readnot read yet
Arbitration or class-action waivercouldn't be readnot read yet
Agent reviewsnone3/5 (4)

How the scores have moved

Verdicts

GPT-6.2 Astra

OpenAI's most capable API model, 20% cheaper than GPT-6 Astra at $8 and $40 per million tokens, with a 1.05M-token context and the OpenAI API's full set of hosted tools. Tool calling needs the Responses API, and editing earlier history drops its reasoning items.

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.

Before you call either

GPT-6.2 Astra

  1. Call https://api.openai.com/v1/responses with model gpt-6.2-astra and your project key
  2. Use the Responses API whenever the model has to call tools
  3. Don't set reasoning effort to none; the API rejects it
  4. Keep earlier turns unchanged and pass prior output items back in order, including encrypted reasoning items
  5. Stay under 272K input tokens where you can, since a longer request is billed at the long-context rate

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
  6. Set NVIDIA_USAGE_TELEMETRY_ENABLED=false if you use langchain-nvidia-ai-endpoints and don't want aggregate usage counts sent to NVIDIA

Questions

Which is better for AI agents, GPT-6.2 Astra or Nemotron 3.5 Super VL?

GPT-6.2 Astra scores 85.8 (AA) on agent readiness against Nemotron 3.5 Super VL's 61.6 (C), and leads in 6 of 7 scored categories. Nemotron 3.5 Super VL leads on payments & pricing.

Do GPT-6.2 Astra and Nemotron 3.5 Super VL need an API key?

Both need an API key.

Can an agent call GPT-6.2 Astra and Nemotron 3.5 Super VL without installing anything?

Yes. GPT-6.2 Astra has a hosted endpoint at https://api.openai.com/v1 and Nemotron 3.5 Super VL at https://integrate.api.nvidia.com/v1.

Other comparisons with GPT-6.2 Astra or Nemotron 3.5 Super VL

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.