Head to head · LLM inference · October 2026 research run

Azure OpenAI in Foundry Models vs Novita AI

Azure OpenAI in Foundry Models scores 80 (A) on agent readiness against Novita AI's 53.9 (D), and leads in 6 of 7 scored categories. Novita AI leads on payments & pricing. Both do llm inference.

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

Which one, for what

Azure OpenAI in Foundry Models A

Best for Teams on Azure that need OpenAI models with Entra ID, private networking, EU or US data zones or FedRAMP scope, and one resource that also serves DeepSeek, Llama, Mistral and Grok models.

Ahead on

  • Reliability, 80 against 28
  • Schema & documentation, 87 against 62
  • Agent ergonomics, 98 against 72
  • Security & auth, 95 against 65
  • Maintenance & community, 86 against 66
  • Transparency & trust, 83 against 57

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

Intermittent failures and 5xx errors in Sweden Central for about six hours on 29 September 2026

Novita AI D

Best for Agents that want many open-weight models at per-token prices behind one OpenAI-style key, with keys that can be limited by model, IP and expiry.

Ahead on

  • Payments & pricing, 35 against 20

Watch for

No status page or SLA was found on the home page, the docs index or the docs site map. The home page states 99.5% uptime with no supporting document

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.

Reliability Azure OpenAI in Foundry Models +52

Azure OpenAI in Foundry Models 80

Azure status page with post-incident reviews, listing Azure OpenAI Service, Foundry Models and Foundry Agent Service as components (20). One incident in the 90 days to 6 November 2026 names Azure OpenAI, and no review after it does, intermittent request failures, higher latency and HTTP 5xx errors in Sweden Central from 10:03 to 15:58 UTC on 29 September 2026 (tracking 7QL5-Z50), counted as one major outage as in the Foundry fine-tuning dossier. The 23 July West US review and the 30 September gateway incident don't name it (10). Quota tiers from Free to Tier 6 with TPM and RPM per model and deployment type, 1,000 RPM and 1,000,000 TPM for each GPT-6 model on Global Standard at Tier 1 (15). 429 responses carry retry-after-ms, every response carries x-ratelimit-* headers, and the quota guide gives exponential backoff with jitter and SDK retry settings (15). The models page says models sold by Azure are covered by Azure service-level agreements and links the Online Services SLA. The consolidated SLA document wouldn't download on 6 October and wasn't retried on 6 November, so the clause rests on Microsoft's docs, read the same way as the 5 October Azure Speech check (10). The v1 API is GA and the GPT-6 models carry no preview label (10).

Novita AI 28

Hosted reading. No status page was found. None is linked from the home page, the pricing page, the docs introduction, either llms.txt or the docs site map (0), so there is no incident record to read (0). The rate limit page documents five account tiers set by monthly top-ups, from under $50 to $10,000 and over, and limits counted in RPM and TPM per model. The figures per model are drawn by script and were not readable, so this line takes part marks (8 of 15). 429 with RATE_LIMIT_EXCEEDED or TOKEN_LIMIT_EXCEEDED, advice to throttle and use exponential backoff, and a billing page that says 429, 500, 503 and 504 are not charged. No Retry-After header was found (10 of 15). No SLA was found. The home page states 99.5% uptime, and the terms say availability is not guaranteed (0). Generally available (10). Per the 9 October check, not re-read on 4 November, as the terms bar automated access to the site and docs.

Security & auth Azure OpenAI in Foundry Models +30

Azure OpenAI in Foundry Models 95

Model reading. Microsoft Entra ID tokens with Azure roles (the Cognitive Services OpenAI User role for calls), managed identities, and key authentication that can be disabled per resource, or two regenerable resource keys in the api-key header. No documented route puts the key in a URL query string (30). Prompts, completions, embeddings and training data aren't used to train foundation models without the customer's permission or instruction, per the data privacy page updated 4 August 2026 (20). Flagged prompts and completions may be stored in the customer's geography for human abuse review, with no retention period stated, and approved customers can turn that storage off through modified abuse monitoring. Responses API data is kept 30 days by default unless store is false (12 of 15). Azure Monitor resource logs and the subscription activity log, as read in the Foundry fine-tuning dossier (15). MSRC coordinated disclosure policy and Microsoft's bounty programme, both named in microsoft.com's security.txt, and Azure OpenAI is listed in FedRAMP High and DoD IL2 scope in Azure public regions. The security.txt passed its Expires date on 2026-09-23 and was still expired on 6 November, which the Bedrock and S3 dossiers mark down by 2, applied here too (18 of 20, down from 20 on 6 October for consistency).

Novita AI 65

Model reading. Bearer keys with the sk_ prefix, shown once, up to 10 an account, with an expiry of 24 hours, 30 days, 90 days or none fixed at creation, deletable in the console, and a per-key model access policy and source IP allowlist that can be set by API. OAuth with PKCE and the scopes api and balance:read is described in auth.md, with no token revocation endpoint. No documented way to send a key in a URL was found (26 of 30). The terms, re-read on 4 November and still updated 5 August 2026, say content is not used to train Novita's models or improve the services by default (17 of 20). The terms state zero data retention, with exceptions for law and for what is necessary to run or support the service, and allow automated safety screening. Batch input files are kept for 15 days (11 of 15). Billing can be queried per key, and budget, monitoring and metrics pages are listed in the docs index and were not read (7 of 15). The trust centre at trust.novita.ai is drawn by script and was not read. /.well-known/security.txt returns 404, and no disclosure policy or bug bounty was found (4 of 20). The key, retention and trust-centre readings are per the 9 October check, not re-read on 4 November.

Agent ergonomics Azure OpenAI in Foundry Models +26

Azure OpenAI in Foundry Models 98

Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Tool use with parallel calls and a forced call by naming the function in tool_choice, 18 of 20 because gpt-6.1-sol calls tools only through the Responses API (18). Strict structured outputs (15). Prompt caching from 1,024 tokens, cached input at 0.1x on GPT-6 ($1 per million on Astra) and cache writes at 1.25x from GPT-5.6 on, with explicit breakpoints (15). 1,050,000-token context on GPT-6 and GPT-6.1, input capped at 922,000 (15). Batch at 50% off Global Standard with a 24-hour target (10). The docs use OpenAI's own SDKs for Python, JavaScript, C#, Go and Java against the v1 endpoint (10). 429 and quota errors documented with retry headers (15). Calls name a deployment rather than a model, so each model must be deployed in the resource first, which the model checklist doesn't score.

Novita AI 72

Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). tools with a strict flag and a worked example. The list of models that support it is drawn by script, and tool_choice is absent from the chat reference (13 of 20). response_format takes json_object and json_schema with strict in the reference, while the FAQ says only json_object works (9 of 15). Prompt caching is automatic on supported models, cache-read prices are on the pricing page and cached_tokens is returned in usage (12 of 15). Context of 1M tokens on DeepSeek V4, GLM 5.3 and Kimi K3 per the pricing page. Output caps were not read (12 of 15). OpenAI-style files and batches with a 24-hour window, one model per file and an introductory 50 per cent discount (10). The OpenAI client works with a changed base URL. Both vendor SDK repositories are archived (5 of 10). Named error codes, a 429 that separates request and token limits, and a trace_id for support (11 of 15). Per the 9 October check, not re-read on 4 November, as the terms bar automated access to the site and docs.

Transparency & trust Azure OpenAI in Foundry Models +26

Azure OpenAI in Foundry Models 83

Closed service under the Microsoft Product Terms, with the v1 spec under MIT and the OpenAI SDKs under Apache-2.0 (15). The data privacy page agrees with the product terms on no training and states where data is processed and stored by deployment type, but gives no retention period for the human-review store and sits beside a 30-day default for Responses data (24 of 30). A published lifecycle policy and a retirement schedule with dates and replacements, but on 6 November the schedule listed gpt-realtime-mini 2025-10-06 and 2025-12-15 twice each with different retirement dates, and no GPT-6 model yet (18 of 20, down from 20). Data locations stated for Standard, Data Zone and Global deployments, and a public sub-processor list per the 5 October Azure Speech check, not re-read (20).

Novita AI 57

Closed service. The terms set Delaware law and arbitration but name the party only as Novita AI, with no corporate form or address. The skill and the MCP server are MIT (10 of 30). The terms state zero data retention and no training by default, and the privacy policy lists retention periods (account data for the life of the account plus 7 years, technical data 2 years). The privacy policy says it does not cover content processed for customers and points to customer agreements. No DPA was found (16 of 30). Retirement notices in the changelog carry a UTC time and a replacement. The terms reserve the right to discontinue any service without notice (12 of 20). The privacy policy names categories of recipients only and transfers that include the United States. No sub-processor list was found (4 of 20). Per the 9 October check, not re-read on 4 November, as the terms bar automated access to the site and docs.

Schema & documentation Azure OpenAI in Foundry Models +25

Azure OpenAI in Foundry Models 87

OpenAPI 3.2 spec for the v1 data plane in Azure/azure-rest-api-specs (azure-v1-v1-generated.json, 71 paths and 852 schemas), linked from the v1 API page (25). No llms.txt at learn.microsoft.com (404). Learn pages offer Copy Markdown and the Markdown sources are public in MicrosoftDocs/azure-ai-docs, last merged 5 October (5 of 10). The models page lists each model's capabilities, context and API support, but the model choice guide, dated 19 May 2026, doesn't cover GPT-6 (15 of 20). Structured outputs with strict: true on schemas and function tools, though not together with parallel function calls (15). Examples in Python, C#, JavaScript, Go, Java and REST, and an error table on the quotas page with a fix for 429 and other codes (15). The v1 path replaces monthly api-version values, with preview capabilities opted into by header, a dated API version changelog and dated model versions. On 6 November the Foundry what's new still covered August, though updated on 5 November, and no Azure OpenAI what's new was found at learn.microsoft.com/en-us/azure/foundry/openai/whats-new, which answered 404 (12 of 15).

Novita AI 62

Model reading. The OpenAPI 3.1.0 document at /.well-known/openapi.json is a 964-byte discovery file with four paths and no schemas, and the API reference is written by hand (6 of 25). llms.txt on both hosts, a Markdown copy of every docs page and an llms-full.txt (10). Guides for function calling, structured output, prompt caching, batch and reasoning say what each is for, and the chat reference describes 136 request and response fields (14 of 20). Fields are typed with required flags and defaults. Enums and ranges are stated in prose only (10 of 15). Curl and Python examples on each guide, error tables by product, a common errors guide and a table of which statuses are billed. The FAQ says json_schema and top_logprobs are unsupported while the reference and a guide document both (10 of 15). A dated changelog with 84 entries since February 2024. The API has no version scheme beyond /v1 (12 of 15). Per the 9 October check, not re-read on 4 November, as the terms bar automated access to the site and docs.

Maintenance & community Azure OpenAI in Foundry Models +20

Azure OpenAI in Foundry Models 86

Model reading. GPT-6.1 Terra released on Azure on 26 October 2026 and a gpt-chat-latest preview of 7 October was added, after GPT-6.1 Sol on 29 September (30). GA models get a retirement date 18 months after launch, set at release and readable through the Models API, with at least 60 days' email and Service Health notice, and previews at least 30 days, so a GA retirement is known more than six months ahead (12 of 12). Many shutdown dates in the 90 days to 6 November, most of them previews or partner models, among them DeepSeek-R1 (13 August), MAI-Image-2 and 2e (15 August), model-router previews (30 August), MAI-Transcribe-1 (15 September), MAI-Image-2.5 previews (1 October), the 2025-03-20 audio models and sora-2 (15 October), a Cohere Command A Plus preview (16 October) and gpt-image-1 (23 October), each in the schedule with a replacement where one exists (4 of 8). The Foundry what's new page, still on August when read on 6 November, plus Microsoft Q&A and paid support; no Azure OpenAI what's new was found (10 of 15). The SDKs are OpenAI's repositories, replies not sampled (5 of 10). Current official SDKs, openai 3.46.0 on PyPI (5 November) and 7.53.0 on npm, plus Microsoft's @azure/openai 2.0.0 companion (15). Supported runtimes stated, Python 3.9 or later and Node.js 20 or later, though openai 3.46.0 requires Python 3.10 (10).

Novita AI 66

Model reading. Changelog entries per the 27 October reading of each entry page, not re-read on 4 November because Novita's terms bar automated access to the site and its linked channels. The newest entry is dated 22 October 2026 (30). Retirement notices carry a UTC time and a replacement, with notice of 1 day (22 October for xiaomimimo/mimo-v2.5 at 00:00 UTC on 23 October) to 29 days (1 September for multimodal models on 30 September). No written notice period was found (6 of 12). Nine dated entries in the 90 days from 6 August (1, 8, 18, 20, 23 and 28 September, 15, 19 and 22 October), each read on its own page (8 of 8). A dated changelog, a Discord server and a support address per the 9 October check (12 of 15). novitalabs/python-sdk and novitalabs/javascript-sdk are archived, unchanged since 8 November 2024 and 4 March 2025, and issue replies were not examined (2 of 10). The docs rely on the OpenAI client, the SDK page still named the two archived packages on 9 October, and the skill repository is unchanged since 24 September 2026 (5 of 15). The JavaScript SDK repository has a publish workflow only and the Python one has none (3 of 10). 30 + 6 + 8 + 12 + 2 + 5 + 3 = 66.

Score by category

CategoryWeight this runAzure OpenAI in Foundry ModelsNovita AIEdge
Reliability16%208028Azure OpenAI in Foundry Models +52
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28762Azure OpenAI in Foundry Models +25
Agent ergonomics13%16.29872Azure OpenAI in Foundry Models +26
Security & auth14%17.59565Azure OpenAI in Foundry Models +30
Payments & pricing10%12.52035Novita AI +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88666Azure OpenAI in Foundry Models +20
Transparency & trust7%8.88357Azure OpenAI in Foundry Models +26
Negative events≤1500
TotalA 80/100D 53.9/100

Facts side by side

FactAzure OpenAI in Foundry ModelsNovita AI
KindModel APIModel API
VendorMicrosoftNovita AI
Hosted endpointhttps://<resource>.openai.azure.com/openai/v1https://api.novita.ai/openai
TransportsHTTPHTTP
AuthOAuth or keyAPI key
PricingPay per usePay per use
x402nono
LicenceProprietary service under the Microsoft Product Terms. The v1 OpenAPI spec is MIT, and the OpenAI SDKs the docs use are Apache-2.0Proprietary service under the Novita AI Terms of Service. The agent skill and the MCP server are MIT
Read-only variant documentednono
llms.txtnoyes
Last release2026-10-262026-10-22
Terms last updatedno date given2026-08-05
Privacy policy last updated2026-09-012026-05-13
Customer content may train modelsyesnot found in the text
Terms restrict automated accessyesnot found in the text
Terms restrict benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Popularity454k npm/wk6 stars, 1.4k npm/wk

What the same task costs

TaskAzure OpenAI in Foundry ModelsNovita AI
Research a product and write a sourced reportgpt-6-astra on Azure OpenAI in Foundry Models, deepseek/deepseek-v4.1-flash on Novita AI$110$0.18
Build a small four-page websitegpt-6-astra on Azure OpenAI in Foundry Models, deepseek/deepseek-v4.1-flash on Novita AI$25.07$0.09
Find and fix a bug in a large codebasegpt-6-astra on Azure OpenAI in Foundry Models, deepseek/deepseek-v4.1-flash on Novita AI$5.41$0.02

Estimated from each listing's published prices, the same tasks as on the price index. Plans, minimums and free allowances aren't counted.

How the scores have moved

Verdicts

Azure OpenAI in Foundry Models

An OpenAI-compatible v1 API with a public OpenAPI spec, Entra ID roles in place of shared keys and FedRAMP High scope, with GPT-6 and GPT-6.1 at OpenAI's list prices on Global Standard. Access needs an Azure subscription with a card and a deployment per model, and a 29 September 2026 incident caused about six hours of failures in Sweden Central.

Novita AI

Per-token prices for about 140 language models are public, and each key can carry an expiry, a model allowlist and a source IP allowlist. No status page, SLA or security.txt was found, the per-model rate limit figures are drawn by script, and both vendor SDK repositories are archived while the docs still point to them.

Before you call either

Azure OpenAI in Foundry Models

  1. Point the OpenAI SDK at https://<resource>.openai.azure.com/openai/v1/ and pass the deployment name as model, not the model id
  2. Prefer Entra ID with the Cognitive Services OpenAI User role over the resource key, which opens the whole data plane
  3. On 429 wait for retry-after-ms, then back off with jitter. The OpenAI SDK retries twice by default
  4. Set store: false on Responses calls you don't need kept. Stored responses persist 30 days by default
  5. Keep remote MCP approvals on for servers you don't control. They're required by default

Novita AI

  1. Set the OpenAI client base URL to https://api.novita.ai/openai and send the key as Authorization: Bearer. Keys start with sk_
  2. Do not close a connection to stop generation. A request that reached the model is billed in full under status 499, so cap output with max_tokens
  3. On 429, check whether the code is RATE_LIMIT_EXCEEDED or TOKEN_LIMIT_EXCEEDED and back off exponentially. No Retry-After header is documented
  4. Read the changelog for retirement notices before pinning a model id. One retirement in October 2026 came with 11 days' notice
  5. Ask the account owner for a key with an expiry, a model access policy and an IP allowlist. Keys are created and deleted only in the console

Questions

Which is better for AI agents, Azure OpenAI in Foundry Models or Novita AI?

Azure OpenAI in Foundry Models scores 80 (A) on agent readiness against Novita AI's 53.9 (D), and leads in 6 of 7 scored categories. Novita AI leads on payments & pricing.

Do Azure OpenAI in Foundry Models and Novita AI need an API key?

Azure OpenAI in Foundry Models takes an API key or an OAuth sign-in. Novita AI needs an API key.

Can an agent call Azure OpenAI in Foundry Models and Novita AI without installing anything?

Yes. Azure OpenAI in Foundry Models has a hosted endpoint at https://<resource>.openai.azure.com/openai/v1 and Novita AI at https://api.novita.ai/openai.

Other comparisons with Azure OpenAI in Foundry Models or Novita AI

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.