Head to head · LLM inference · October 2026 research run

Azure OpenAI in Foundry Models vs Inkling 2 Small

Azure OpenAI in Foundry Models scores 80 (A) on agent readiness against Inkling 2 Small's 52.1 (D), and leads in 6 of 7 scored categories. 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 30
  • Schema & documentation, 87 against 70
  • Agent ergonomics, 98 against 62
  • Security & auth, 95 against 57
  • Maintenance & community, 86 against 75
  • Transparency & trust, 83 against 64

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

Inkling 2 Small D

Best for Developers who want a capable multimodal open-family model through an OpenAI-compatible API today, or to fine-tune it on Tinker, and who can live with a beta surface until the weights are published.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

Serverless inference and the OpenAI-compatible API are both labelled beta, with a waitlist for higher throughput

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 +50

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).

Inkling 2 Small 30

Model reading, for the surface it's called on, Tinker's serverless inference and OpenAI-compatible API. No status page found, per the tinker listing's checks of 1 October and 4 November (0), so no readable incident history (5). The only published limit is the in-flight sample cap of 2,000, per the tinker listing's 1 October check; the OpenAI-compatible page gives no numbers and says higher or more stable throughput needs the waitlist (10). The SDK retries sampling with stable request IDs, per the tinker listing's reading of the SDK repository; the OpenAI-compatible page has no retry guidance (15). No SLA found (0). Serverless inference is 'currently in beta' on the models and pricing page and the OpenAI-compatible API is labelled Beta, read 6 November (0). 0 + 5 + 10 + 15 + 0 + 0 = 30.

Security & auth Azure OpenAI in Foundry Models +38

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).

Inkling 2 Small 57

Platform readings are the tinker listing's. Revocable API keys from the console, with no per-key scopes found (20). Org, team and project permissions with no read-only role (5). The model returns its own completions, no third-party content (10). get_audit_log() for admins (15). security.txt with a reporting address and no stated acknowledgement time (7). For the model reading, Tinker's terms commit not to use Customer Content for training, recorded under transparency. 20 + 5 + 10 + 15 + 7 = 57.

Agent ergonomics Azure OpenAI in Foundry Models +36

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.

Inkling 2 Small 62

Model reading (tool use, structured output, caching, context, batch, SDKs). A 256K served context, max_tokens and a priced cache at $0.03 per million; tool use isn't documented for this model (15 of 25). Output-size controls through max_tokens, reasoning_effort and separate_reasoning (15 of 20). One documented error, the 400 for unsupported reasoning_effort (5 of 20). Stable request IDs make SDK sampling retries safe, per the tinker listing (15 of 20). OpenAI's SDKs work against the endpoint, with Tinker's Python SDK besides, and reasoning defaults to 0.9 (12 of 15). 15 + 15 + 5 + 15 + 12 = 62.

Transparency & trust Azure OpenAI in Foundry Models +19

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).

Inkling 2 Small 64

Editorial half. Closed for now under the Tinker Terms of Use and the Model Acceptable Use Policy, per the model card, with Apache 2.0 weights promised the week after launch (15). Terms commit not to use Customer Content for training, keep it only as needed, with a DPA and deletion on request; the privacy notice wasn't re-read, per the tinker listing (15). Dated deprecation notices with no stated period (15). The DPA annex names Google Cloud, Cloudflare, WorkOS and OpenAI with service and location (15). 15 + 15 + 15 + 15 = 60.

Schema & documentation Azure OpenAI in Foundry Models +17

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).

Inkling 2 Small 70

Model reading. No OpenAPI file of its own; the OpenAI-compatible chat and completions endpoints and the typed Python SDK are the contract, as the tinker listing reads it (15). llms.txt on the docs host, per the tinker listing's 1 October check (10). The model card states intended use (agentic and tool-use systems, coding assistants, chatbots, RAG), inputs, outputs and limitations, and the launch post its benchmarks (16 of 20). Model IDs, context lengths and the reasoning_effort values (none to xhigh, or 0.0 to 0.99) are documented; the tool-call format and structured output aren't, for this model (8 of 15). A Python example and an HTTP 400 for models without reasoning_effort, with no error page (6 of 15). A dated Tinker changelog and a model deprecations page, per the tinker listing (15). 15 + 10 + 16 + 8 + 6 + 15 = 70.

Maintenance & community Azure OpenAI in Foundry Models +11

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).

Inkling 2 Small 75

Model reading. Released 5 November 2026 (30). Churn and notice in place of release counts: Inkling, Inkling-Small (30 July) and Inkling 2 Small in about four months, and a deprecations page with dated retirements and a promise to 'aim to give advance notice' by email, with no stated period, per the tinker listing (10 of 20). A public changelog and a support address and Discord, per the tinker listing (10 of 15). Current official SDKs, Tinker's Python SDK and the OpenAI-compatible endpoint (15). SDK and cookbook CI, per the tinker listing (10). 30 + 10 + 10 + 15 + 10 = 75.

Score by category

CategoryWeight this runAzure OpenAI in Foundry ModelsInkling 2 SmallEdge
Reliability16%208030Azure OpenAI in Foundry Models +50
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28770Azure OpenAI in Foundry Models +17
Agent ergonomics13%16.29862Azure OpenAI in Foundry Models +36
Security & auth14%17.59557Azure OpenAI in Foundry Models +38
Payments & pricing10%12.52020even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88675Azure OpenAI in Foundry Models +11
Transparency & trust7%8.88364Azure OpenAI in Foundry Models +19
Negative events≤1500
TotalA 80/100D 52.1/100

Facts side by side

FactAzure OpenAI in Foundry ModelsInkling 2 Small
KindModel APIModel API
VendorMicrosoftThinking Machines Lab
Hosted endpointhttps://<resource>.openai.azure.com/openai/v1https://tinker.thinkingmachines.dev/services/tinker-prod/oai/api/v1
TransportsHTTP
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 for now, used through Tinker under the Tinker Terms of Use and Thinking Machines' Model Acceptable Use Policy, per the model card. Thinking Machines says it will publish the weights under Apache 2.0 the week after launch, once outside safety testing is done
Read-only variant documentednono
llms.txtnoyes
Last release2026-10-262026-11-05
Terms last updatedno date givennot read yet
Privacy policy last updated2026-09-01not read yet
Customer content may train modelsyesnot read yet
Terms restrict automated accessyesnot read yet
Terms restrict benchmarkingyesnot read yet
Terms or service can change without noticenot found in the textnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Popularity454k npm/wknone

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.

Inkling 2 Small

A new multimodal mixture-of-experts model from Thinking Machines, callable today through Tinker's OpenAI-compatible endpoint at $0.30 and $1.00 per million tokens, with strong vendor-reported coding and agent scores. Tinker's serverless inference is beta, with no status page or SLA, and the weights aren't public yet.

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

Inkling 2 Small

  1. Call https://tinker.thinkingmachines.dev/services/tinker-prod/oai/api/v1 with an OpenAI client and TINKER_API_KEY, using /chat/completions
  2. The serverless model ID is thinkingmachines/Inkling-2-Small:peft:262144:sampling-nvfp4, per Tinker's pricing page. The OpenAI page's examples use your own checkpoint paths, so confirm it before relying on it
  3. Pass reasoning_effort as none to xhigh or 0.0 to 0.99 (default 0.9); reasoning arrives in reasoning_content unless separate_reasoning is false
  4. Keep images between 40 and 4096 px a side, per the model card
  5. Validate JSON yourself, since structured output and the tool-call format aren't documented
  6. Plan for a move to open weights. When they publish, the open-weights listing will carry sizes and runtimes

Questions

Which is better for AI agents, Azure OpenAI in Foundry Models or Inkling 2 Small?

Azure OpenAI in Foundry Models scores 80 (A) on agent readiness against Inkling 2 Small's 52.1 (D), and leads in 6 of 7 scored categories.

Do Azure OpenAI in Foundry Models and Inkling 2 Small need an API key?

Azure OpenAI in Foundry Models takes an API key or an OAuth sign-in. Inkling 2 Small needs an API key.

Can an agent call Azure OpenAI in Foundry Models and Inkling 2 Small without installing anything?

Yes. Azure OpenAI in Foundry Models has a hosted endpoint at https://<resource>.openai.azure.com/openai/v1 and Inkling 2 Small at https://tinker.thinkingmachines.dev/services/tinker-prod/oai/api/v1.

Other comparisons with Azure OpenAI in Foundry Models or Inkling 2 Small

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.