{ "data": { "a": { "slug": "azure-openai", "name": "Azure OpenAI in Foundry Models", "vendor": "Microsoft", "vendorUrl": "https://azure.microsoft.com", "kind": "model", "category": "inference", "summary": "Microsoft Azure's hosted API for OpenAI's GPT models and other Foundry Models sold by Azure, such as DeepSeek, Llama, Mistral and Grok, called through an OpenAI-compatible v1 endpoint on each customer's Azure resource.", "url": "https://www.anchorterminal.com/tools/azure-openai", "markdownUrl": "https://www.anchorterminal.com/tools/azure-openai.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/azure-openai.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/azure-openai.json", "dns": "azure-openai.grade.anchorterminal.com", "repo": "https://github.com/Azure/azure-rest-api-specs", "license": "Proprietary service under the Microsoft Product Terms. The v1 OpenAPI spec is MIT, and the OpenAI SDKs the docs use are Apache-2.0", "transports": [ "http" ], "remoteUrl": "https://\u003cresource\u003e.openai.azure.com/openai/v1", "packages": [ { "registry": "pypi", "name": "openai" }, { "registry": "npm", "name": "openai" }, { "registry": "npm", "name": "@azure/openai" } ], "auth": "mixed", "authNotes": "`api-key` header with one of the resource's two regenerable keys, or a Microsoft Entra ID bearer token (scope https://ai.azure.com/.default) with the Cognitive Services OpenAI User role. Key authentication can be disabled per resource (`disableLocalAuth`). Each model must be deployed in the resource before it can be called, by deployment name.", "pricing": "usage", "pricingNotes": "Pay per token on an Azure subscription. Global Standard GPT-6 and GPT-6.1 prices match OpenAI's list (GPT-6.1 Sol $2/$10, GPT-6.1 Terra $1/$5 per million tokens), Data Zone costs 10% more, long-context requests cost 2x input and 1.5x output, cached input 0.1x, cache writes 1.25x, Flex half price and priority processing 2x (GPT-6 Sol). Batch is 50% off Global Standard. Provisioned throughput is billed per PTU hour. Prices from the Azure Retail Prices API, because the pricing page fills its table with JavaScript (checked 2026-11-06).", "priceSummary": "from $0.10 / 1M in", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the Foundry docs, the v1 OpenAPI spec or the pricing page. Access needs an Azure subscription with a payment method (checked 2026-11-06).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 454039, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://learn.microsoft.com/en-us/azure/foundry/openai/", "rateLimitsUrl": "https://learn.microsoft.com/en-us/azure/foundry/openai/quotas-limits", "openapi": "https://github.com/Azure/azure-rest-api-specs/blob/main/specification/ai/data-plane/OpenAI.v1/azure-v1-v1-generated.json", "capabilities": [ "inference.llm", "inference.open-weights" ], "tags": [ "official", "hosted", "model", "card-required", "openapi", "openai-compatible", "closed-source", "enterprise", "eu", "python", "typescript", "status-page", "bug-bounty" ], "lastRelease": "2026-10-26", "graded": true, "anchor": { "graded": true, "score": 80, "grade": "A", "agentReady": true, "rank": 14, "ranked": true, "rankOf": 1486, "categoryRank": 4, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 98, "maintenance": 86, "payments": 20, "reliability": 80, "schema": 87, "security": 95, "transparency": 83 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "Public OpenAPI 3.2 spec for the v1 API, 71 paths covering Responses, Chat Completions, batches, files and vector stores", "Microsoft Entra ID tokens with Azure roles, and key authentication can be switched off per resource", "GA models carry a retirement date 18 months after launch, set at release and readable through the Models API", "Data Zone deployments keep processing inside the EU or US, and Azure OpenAI is in FedRAMP High scope", "GPT-6 Astra, Sol and Luna at $10/$50, $2/$10 and $0.10/$0.50 per million tokens on Global Standard" ], "weaknesses": [ "Intermittent failures and 5xx errors in Sweden Central for about six hours on 29 September 2026", "An Azure subscription with a card, a resource and a model deployment come before the first call", "No llms.txt, and no Azure OpenAI what's new page was found; the Foundry one still covered August on 6 November", "No retention period stated for prompts kept for human abuse review, and Responses data is kept 30 days by default", "The retirement schedule lists two `gpt-realtime-mini` versions twice with different retirement dates, and no GPT-6 retirement dates yet" ], "agentNotes": [ "Point the OpenAI SDK at https://\u003cresource\u003e.openai.azure.com/openai/v1/ and pass the deployment name as `model`, not the model id", "Prefer Entra ID with the Cognitive Services OpenAI User role over the resource key, which opens the whole data plane", "On 429 wait for `retry-after-ms`, then back off with jitter. The OpenAI SDK retries twice by default", "Set `store: false` on Responses calls you don't need kept. Stored responses persist 30 days by default", "Keep remote MCP approvals on for servers you don't control. They're required by default" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "A", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 80 } ], "editorialScores": { "ergonomics": 98, "maintenance": 86, "payments": 20, "reliability": 80, "schema": 87, "security": 95, "transparency": 77 }, "provenanceScore": 88, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "pip install openai azure-identity # or: npm i openai @azure/identity", "http": "curl \"https://$AZURE_OPENAI_RESOURCE.openai.azure.com/openai/v1/responses\" \\\n -H \"api-key: $AZURE_OPENAI_API_KEY\" -H \"content-type: application/json\" \\\n -d '{\"model\":\"\u003cyour-deployment-name\u003e\",\"input\":\"hello\"}'" }, "letme": { "capability": "https://letme.dev/inference.llm", "tool": "https://letme.dev/azure-openai" }, "sameCompany": [ "azure-foundry-fine-tuning", "azure-ai-content-safety", "azure-speech-to-text", "azure-text-to-speech", "microsoft-agent-framework", "microsoft-execution-containers", "microsoft-entra-agent-id", "azure-key-vault", "bing-grounding", "azure-document-intelligence", "azure-devops-mcp", "microsoft-learn-mcp", "tokeneconomizer", "playwright-mcp", "azure-mcp", "azure-maps", "azure-translator", "microsoft-graph-calendar", "azure-blob-storage", "onedrive-sharepoint", "microsoft-teams", "dynamics-365-sales", "copilot-studio-mcp", "power-automate", "foundry-local", "microsoft-decision-1", "microsoft-advertising-api", "microsoft-excel-graph", "outlook-mail-graph", "microsoft-graph-people", "mage-vl-cowork" ], "area": "models", "unitPrices": [ { "item": "GPT-6.1 Sol input, Global Standard", "unit": "1m-tokens", "usd": 2, "note": "short context, Retail Prices API meter effective 2026-10-01" }, { "item": "GPT-6.1 Sol output, Global Standard", "unit": "1m-tokens", "usd": 10, "note": "short context" }, { "item": "GPT-6.1 Terra input, Global Standard", "unit": "1m-tokens", "usd": 1, "note": "short context" }, { "item": "GPT-6.1 Terra output, Global Standard", "unit": "1m-tokens", "usd": 5, "note": "short context" }, { "item": "GPT-6 Astra input, Global Standard", "unit": "1m-tokens", "usd": 10, "note": "short context" }, { "item": "GPT-6 Astra output, Global Standard", "unit": "1m-tokens", "usd": 50, "note": "short context" } ], "provenance": { "legalEntity": "Microsoft Corporation", "domain": "microsoft.com", "domainRegistered": "1991-05-02", "domainNote": "Endpoints are on openai.azure.com and cognitiveservices.azure.com. microsoft.com publishes a security.txt, but it passed its Expires date on 2026-09-23 and was still expired on 2026-11-06.", "endpointOnVendorDomain": true, "terms": "https://www.microsoft.com/licensing/terms/product/ForOnlineServices/all", "privacy": "https://privacy.microsoft.com/en-us/privacystatement", "statusPage": "https://azure.status.microsoft/en-us/status", "changelog": "https://learn.microsoft.com/en-us/azure/foundry/whats-new-foundry", "securityTxt": "expired", "checked": "2026-11-06", "score": 88 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/azure-openai.json", "live": { "slug": "azure-openai", "probe": { "target": "https://\u003cresource\u003e.openai.azure.com/openai/v1", "method": "get", "lastAt": "2026-11-07T18:20:12.145420458Z", "lastOk": false, "lastStatus": 0, "lastMs": 0, "lastNote": "DNS lookup failed", "authRequired": false, "uptime24h": 0, "uptime30d": 0, "p50ms24h": 0, "p95ms24h": 0, "samples24h": 200, "samples30d": 200, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 0 }, { "date": "2026-11-07", "probes": 187, "ok": 0 } ], "outages": [ { "start": "2026-11-06T22:45:05.888142257Z", "end": "0001-01-01T00:00:00Z", "note": "DNS lookup failed" } ] }, "versions": [ { "registry": "npm", "name": "@azure/openai", "version": "2.0.0", "seenAt": "2026-11-06T23:09:28.988578937Z" }, { "registry": "npm", "name": "openai", "version": "7.53.0", "seenAt": "2026-11-06T23:09:28.954764315Z" }, { "registry": "pypi", "name": "openai", "version": "3.46.0", "released": "2026-11-05", "seenAt": "2026-11-06T23:09:28.844701934Z" } ], "githubStars": 3113, "npmWeekly": 56543040, "pypiWeekly": 91156146, "securityTxt": { "url": "https://microsoft.com/.well-known/security.txt", "state": "valid", "expires": "2027-10-27T16:00:00.000Z", "checkedAt": "2026-11-07T16:02:01.196666056Z" }, "pages": [ { "url": "https://learn.microsoft.com/en-us/azure/foundry/openai/concepts/model-retirement-schedule", "kind": "deprecations", "status": 200, "checkedAt": "2026-11-07T14:13:01.613678733Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "51438ff38076" } ], "updatedAt": "2026-11-07T18:20:12.145420458Z" } }, "answer": "Azure OpenAI in Foundry Models scores 80 (A) on agent readiness against RouterPlus's 50.3 (D), and leads in 6 of 7 scored categories. RouterPlus leads on payments \u0026 pricing.", "b": { "slug": "routerplus", "name": "RouterPlus", "vendor": "RouterPlus", "vendorUrl": "https://routerplus.com", "kind": "router", "category": "inference", "summary": "RouterPlus is an LLM gateway that puts Claude, GPT, open-weight, image, video and decision models behind one API key and a prepaid balance, with OpenAI-compatible and Anthropic-compatible endpoints.", "url": "https://www.anchorterminal.com/tools/routerplus", "markdownUrl": "https://www.anchorterminal.com/tools/routerplus.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/routerplus.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/routerplus.json", "dns": "routerplus.grade.anchorterminal.com", "license": "Closed service. No terms of service for the gateway were found on routerplus.com or app.routerplus.com on 13 October 2026. The only terms on the site govern the capacity request form and name EVO HQ Inc, a Delaware corporation (https://routerplus.com/capacity/terms/).", "transports": [ "http" ], "remoteUrl": "https://api.routerplus.com/v1", "packages": [], "auth": "api-key", "authNotes": "A `tm_vk_` virtual key, sent as `Authorization: Bearer` or `x-api-key` on every route. A person signs up in the browser through Clerk with email verification, and the first key is shown once after sign-in. More keys come from the console or from `POST /api/identity/keys` with a console session. The programmatic signup route `POST /v1/signup` was removed and returns 404 (https://app.routerplus.com/docs/authentication.md, https://app.routerplus.com/docs/api-signup.md).", "pricing": "usage", "pricingNotes": "Provider list prices per 1M tokens with no markup, paid from prepaid credits. Purchases start at $10, and RouterPlus matches the first $100 of purchases for eligible accounts. Signup adds no free credit. Inference through the caller's own provider keys (BYOK) carries no RouterPlus charge and needs no credit. Prices are public in the docs catalogue and the model pages without a login (https://app.routerplus.com/docs/models.md, https://app.routerplus.com/docs/pricing.md).", "priceSummary": "0% fee", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in https://app.routerplus.com/llms-full.txt, checked 13 October 2026. Calls draw on a prepaid balance bought in the console's Billing page.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-13" }, "docsUrl": "https://app.routerplus.com/docs/overview", "llmsTxt": "https://app.routerplus.com/llms.txt", "capabilities": [ "inference.router", "inference.llm", "inference.decision", "image.generate" ], "tags": [ "hosted", "router", "closed-source", "usage-priced", "prepaid", "llms-txt", "openai-compatible", "anthropic-compatible", "streaming" ], "graded": true, "anchor": { "graded": true, "score": 50.3, "grade": "D", "agentReady": false, "rank": 1061, "ranked": true, "rankOf": 1486, "categoryRank": 36, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 71, "maintenance": 44, "payments": 40, "reliability": 42, "schema": 59, "security": 59, "transparency": 41 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": -2, "negativeNotes": [ "Misleading claims, seen 13 October and again on 4 November 2026, one term. The banner on https://routerplus.com/ reads \"Try RouterPlus with free credits\", while the quickstart (https://app.routerplus.com/docs/quickstart.md) says \"Signup does not add free credit\" and the playground bills the organisation's credits. Only an invitation link adds credit. On 4 November 2026 the homepage FAQ also says \"The gateway does not store prompts or completions\", while the data policy (https://app.routerplus.com/docs/data-policy.md) says requests and responses to non-dedicated endpoints are logged for up to 30 days. Repeats of one kind fold into one term. -2." ], "verdict": "The docs are written for agents, every model price is public, and each response carries its own cost. No terms of service, privacy policy, status page or changelog were found. Request content is now logged for 30 days by default while the homepage says prompts aren't stored, and signup adds no free credit.", "bestFor": "Teams that call Claude, GPT and open-weight models from one key and want the cost of every call in the response, with their own provider keys where they have them.", "strengths": [ "llms.txt, llms-full.txt and a Markdown copy of every page, with an integration guide written for coding agents", "Every billed response carries `usage.cost` in USD, and `GET /v1/generation` lists each attempt behind a request", "Any chat model answers on both the OpenAI-compatible and Anthropic-compatible surfaces, with the format translated by the gateway", "Typed errors with a stable `error_type`, an origin header, a retry rule per class and `retry-after` on rate-limit 429s", "105 chat models from 18 providers on 4 November 2026, and BYOK inference carries no RouterPlus charge" ], "weaknesses": [ "No terms of service, privacy policy, status page, changelog or security.txt found for the gateway", "Request and response content to non-dedicated endpoints is logged for up to 30 days by default, and opting out takes a request to support", "Signup adds no free credit, purchases start at $10, and keys stay at 20 requests a minute until the first purchase", "No idempotency keys, no batch route and no embeddings, and the `zdr` and `regions` filters remove every marketplace route", "Optimize, the eval-based model search the homepage leads with, is paused" ], "agentNotes": [ "Send `max_tokens` on every request. Without it the balance hold assumes up to 32,768 output tokens and can return `insufficient_quota` on a small balance", "Switch on `error_type`. Retry `rate_limit` after `retry-after`, and stop on `insufficient_quota`, which needs a person to add credit or raise a cap", "Don't add a retry loop on top of the SDK's. There is no idempotency key, so a retry that reaches a provider is billed again", "Keep secrets out of prompts. Request content is logged for up to 30 days unless the organisation has opted out through support", "Use `/v1/messages` for Claude when you need `thinking` or server tools. `response_format` works for GPT ids and open models, not Claude" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 50.3 } ], "editorialScores": { "ergonomics": 71, "maintenance": 44, "payments": 40, "reliability": 42, "schema": 59, "security": 59, "transparency": 26 }, "provenanceScore": 55, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl -N https://api.routerplus.com/v1/chat/completions \\\n -H \"Authorization: Bearer $TM_API_KEY\" \\\n -H \"content-type: application/json\" \\\n -d '{\"model\":\"claude-haiku-4-5\",\"stream\":true,\"max_tokens\":60,\"messages\":[{\"role\":\"user\",\"content\":\"hello\"}]}'" }, "letme": { "capability": "https://letme.dev/inference.router", "tool": "https://letme.dev/routerplus" }, "area": "models", "unitPrices": [ { "item": "Markup on provider token prices", "unit": "pct", "usd": 0, "note": "Pass-through per the pricing docs. Credits are bought in $10 steps or more" }, { "item": "Claude Opus 5.5 input", "unit": "1m-tokens", "usd": 4, "note": "claude-opus-5-5, served by Anthropic's API" }, { "item": "Claude Opus 5.5 output", "unit": "1m-tokens", "usd": 20 }, { "item": "GPT-6.1 Sol input", "unit": "1m-tokens", "usd": 2, "note": "gpt-6.1-sol, served by OpenAI's API, 1,050,000-token context" }, { "item": "GPT-6.1 Sol output", "unit": "1m-tokens", "usd": 10 }, { "item": "Anthropic web search server tool", "unit": "1k-requests", "usd": 10, "note": "$10 per 1,000 searches, Anthropic's price, on top of tokens" } ], "provenance": { "legalEntity": "EVO HQ Inc", "domain": "routerplus.com", "domainRegistered": "2014-04-15", "endpointOnVendorDomain": true, "terms": "", "privacy": "", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-11-04", "notes": [ "EVO HQ Inc, a Delaware corporation, is named only in the terms of the capacity request form at https://routerplus.com/capacity/terms/ (effective and last updated 1 August 2026), which govern form submissions and not the gateway. The footer elsewhere reads © 2026 RouterPlus.", "No terms of service or privacy policy for the gateway were found, re-checked on 4 November 2026. The footer's Privacy and Security links open an email to founders@evo-hq.com. The docs' data policy page (https://app.routerplus.com/docs/data-policy.md) is the only data statement for the gateway.", "No status page. Model pages show per-provider uptime over the last 24 hours, with no incident history. Requests to status.routerplus.com failed at our proxy with a 502 on 13 October and 4 November 2026, so whether it exists is unchecked.", "No changelog found. The blog's newest post is dated 27 October 2026, and its 13 October 2026 post dates the ScaleDown models' launch. The docs date one console change, key copying from 17 October 2026.", "routerplus.com/.well-known/security.txt and app.routerplus.com/.well-known/security.txt answered 404 on 4 November 2026.", "routerplus.com/robots.txt carries only commented content-signal definitions and a sitemap line, with no rules and no Content-Signal directive (4 November 2026)." ], "score": 55 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/routerplus.json", "live": { "slug": "routerplus", "probe": { "target": "https://api.routerplus.com/v1", "method": "get", "lastAt": "2026-11-07T18:20:51.614650516Z", "lastOk": true, "lastStatus": 401, "lastMs": 628, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 99.41, "p50ms24h": 513, "p95ms24h": 628, "samples24h": 239, "samples30d": 6135, "days": [ { "date": "2026-10-13", "probes": 4, "ok": 4 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 252 }, { "date": "2026-10-16", "probes": 252, "ok": 249 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 239 }, { "date": "2026-10-24", "probes": 251, "ok": 230 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 248 }, { "date": "2026-10-28", "probes": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 245 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ], "outages": [ { "start": "2026-10-24T05:05:33.613541379Z", "end": "2026-10-24T07:08:12.366400327Z", "note": "HTTP 522 server error" }, { "start": "2026-10-23T17:39:27.824091162Z", "end": "2026-10-23T17:56:26.642152403Z", "note": "timed out" } ] }, "securityTxt": { "url": "https://routerplus.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:23.622290323Z" }, "llmsTxt": { "url": "https://app.routerplus.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:51.409195847Z" }, "domain": { "domain": "routerplus.com", "registered": "2014-04-15", "source": "https://rdap.verisign.com/com/v1/domain/routerplus.com", "checkedAt": "2026-11-01T14:22:51.180116459Z" }, "pages": [ { "url": "https://app.routerplus.com/docs/pricing.md", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T13:59:31.728346224Z", "changedAt": "2026-11-07T13:59:31.728346224Z", "fingerprint": "54b0c65abbd3" } ], "updatedAt": "2026-11-07T18:20:51.614650516Z" } }, "edges": [ { "by": 42, "category": "maintenance", "leads": "azure-openai", "name": "Maintenance \u0026 community", "reasons": { "a": "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\u0026A 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).", "b": "Router, read on the model lines. No changelog or release notes found. The blog, re-read on 4 November 2026, dates the launch of ScaleDown's extract-1 and summarize-1 on chat completions and classify-1 on the decisions API to 13 October 2026, and the catalogue now lists 105 chat models against 19 on 13 October, so the API changed within the last 30 days (30). The docs also date a console change on 17 October 2026 (keys can be copied again), which isn't counted, since it changes the console and not the API. Models carry a `deprecation_date` that delists them automatically, with no notice period stated (3 of 12). `POST /v1/signup` and the magic-link route were removed and Optimize is paused, none with a date we could find (3 of 8). No public changelog. Support is reached through the console and an email address, and wasn't tested (3 of 15). No public issue tracker for the gateway (0 of 10). No official SDK. The docs rely on the OpenAI and Anthropic SDKs and give client setups (5 of 15). No package or public repository to check (0 of 10)." }, "scores": { "a": 86, "b": 44 } }, { "by": 42, "category": "transparency", "leads": "azure-openai", "name": "Transparency \u0026 trust", "reasons": { "a": "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).", "b": "Closed service with no terms of service found. The only terms on the site govern the capacity request form, under EVO HQ Inc (0 of 30). The data policy page is detailed, lists what is stored and why, and gives a 30-day period for request logs and each provider's retention flag. Its 4 November 2026 text, which logs request content by default, no longer agrees with the homepage FAQ; that contradiction is charged once as a misleading claim under negative events, not on this line. There is no privacy policy, no DPA and no retention period for account data such as email addresses (14 of 30, held). Model retirement by `deprecation_date` is documented with no notice period, and no dated deprecation notices were found (4 of 20). The docs name Clerk, Resend and an AWS bucket, and say RouterPlus's own GPUs run in the United States. The form's terms name Supabase, Cloudflare and Resend. No complete subprocessor list or gateway hosting location was found (8 of 20)." }, "scores": { "a": 83, "b": 41 } }, { "by": 38, "category": "reliability", "leads": "azure-openai", "name": "Reliability", "reasons": { "a": "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).", "b": "Hosted reading. No status page found. Model pages show each provider's uptime over the last 24 hours and no incident history, and status.routerplus.com failed at our proxy again on 4 November 2026 (0). No readable incident history (5). The limits page, re-read on 4 November 2026, gives 20 requests a minute until the organisation's first purchase, then 300 per console key and 60 for the managed Playground key, with token-per-minute and in-flight limits per organisation and key (15). Rate-limit 429s carry `retry-after` from 1 to 59 seconds and `metadata.retry_at`, the errors page gives a retry or no-retry rule for each error class, and the docs say a retry is a new billed request because there is no idempotency key. That is safe-retry guidance without keys on the billed call, the value this run settled for routers such as ramp-router (12, 15 before). The homepage says \"Production-grade SLAs\", but no SLA terms were found, and the only terms on the site say a stated response time is not a service level (0). The chat and messages surfaces carry no beta label. The Responses API is a preview for non-OpenAI models and Optimize is paused, neither of which is the main surface (10). 0 + 5 + 15 + 12 + 0 + 10 = 42." }, "scores": { "a": 80, "b": 42 } }, { "by": 36, "category": "security", "leads": "azure-openai", "name": "Security \u0026 auth", "reasons": { "a": "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).", "b": "Router, read on the model lines. `tm_vk_` keys are stored as SHA-256 hashes and revocable, each bound to a workspace and principal, with per-key RPM and monthly spend caps. Since 17 October 2026 the console also keeps an encrypted copy so an owner or admin can copy a key again, and an organisation can ask for copying to be turned off. Inference keys have no management rights. There are no permission scopes on a key and no SSO or SCIM (24 of 30). RouterPlus says it does not train on request logs and does not share them, and deletes them after 30 days. Most Claude and GPT routes are marked `prompt_logging: retained` with no ZDR, so retention and training upstream rest on each provider's API terms, while DeepInfra's open models, Perplexity, Cloudflare Workers AI, Fastino and RouterPlus's own models declare `none` (12 of 20, held). The data policy re-read on 4 November 2026 says requests and responses to non-dedicated endpoints are now logged by default for up to 30 days for debugging, with recognised keys removed. On 13 October it said content was kept only for hackathon accounts. Opting out takes a request to support, dedicated endpoints are excluded, and the `zdr` and `data_collection: deny` filters still remove every marketplace route, so they work only on the caller's own provider keys. Cloudflare AI Gateway, with default logging and a per-request header to switch it off, has 11 here (7 of 15, 10 before). `GET /v1/generation` lists every attempt behind a request with provider, tokens and cost, and the console has usage and logs (14 of 15). No security.txt (404 on both hosts on 4 November 2026), disclosure policy, bug bounty or certification found. The footer's Security link is an email to founders@evo-hq.com (2 of 20). 24 + 12 + 7 + 14 + 2 = 59." }, "scores": { "a": 95, "b": 59 } }, { "by": 28, "category": "schema", "leads": "azure-openai", "name": "Schema \u0026 documentation", "reasons": { "a": "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).", "b": "Router, scored on the API lines. No OpenAPI or other machine-readable contract for the gateway was found. It follows the OpenAI and Anthropic wire formats, which this checklist doesn't credit to a reseller, the same reading as Antseed (0 of 25). llms.txt, llms-full.txt and a Markdown copy of every page (10). Each route page says what it is for, what isn't available, and which route to use for which model, and the agent integration guide lists what not to build on (18 of 20). Request fields follow the upstream formats, and the wire compatibility page tables which fields pass, translate, drop or fail with a typed 400 (12 of 15). Curl, Python and TypeScript examples on every page, and an error reference with a class, status and remedy for each error (15). Routes are versioned under /v1 and the wire compatibility page says changing it needs a recorded decision, but no changelog or dated release notes were found, re-read on 4 November 2026 (4 of 15)." }, "scores": { "a": 87, "b": 59 } }, { "by": 27, "category": "ergonomics", "leads": "azure-openai", "name": "Agent ergonomics", "reasons": { "a": "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.", "b": "Router, read on the model lines (tool use, structured output, caching, context, batch, SDKs, errors). Tools pass through on both surfaces, and Anthropic server tools such as web search work for Claude models on `/v1/messages`. Behaviour depends on the model (15 of 20). `response_format` works for GPT ids and the open models (re-read on 4 November 2026), and the docs tell callers to get JSON from Claude through a single tool, so structured output still rests on the provider (8 of 15, held). Cached-input and cache-write prices per model, a session id that keeps provider caches warm, and `cache_control` on the Anthropic surface (13 of 15). The catalogue's largest contexts are 1,050,000 tokens on GPT-6.1 Sol and 1,000,000 on Claude Sonnet 5.5, a judgement call since a router has no default model (15). No batch route (0 of 10). No SDK of its own. The OpenAI and Anthropic SDKs work with a changed base URL, and the docs give setups for ten coding tools (5 of 10). A stable `error_type` in every body and header, an origin header, the limit that refused a request, and `x-tm-dropped-params` naming every dropped field (15)." }, "scores": { "a": 98, "b": 71 } } ], "facts": [ { "a": "Model API", "b": "Model router", "name": "Kind" }, { "a": "Microsoft", "b": "RouterPlus", "name": "Vendor" }, { "a": "https://\u003cresource\u003e.openai.azure.com/openai/v1", "b": "https://api.routerplus.com/v1", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Pay per use", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the Microsoft Product Terms. The v1 OpenAPI spec is MIT, and the OpenAI SDKs the docs use are Apache-2.0", "b": "Closed service. No terms of service for the gateway were found on routerplus.com or app.routerplus.com on 13 October 2026. The only terms on the site govern the capacity request form and name EVO HQ Inc, a Delaware corporation (https://routerplus.com/capacity/terms/).", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-10-26", "b": "none", "name": "Last release" }, { "a": "no date given", "b": "no document linked", "name": "Terms last updated" }, { "a": "2026-09-01", "b": "no document linked", "name": "Privacy policy last updated" }, { "a": "yes", "b": "not read yet", "name": "Customer content may train models" }, { "a": "yes", "b": "not read yet", "name": "Terms restrict automated access" }, { "a": "yes", "b": "not read yet", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not read yet", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not read yet", "name": "Arbitration or class-action waiver" }, { "a": "454k npm/wk", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "Azure OpenAI in Foundry Models scores 80 (A) on agent readiness against RouterPlus's 50.3 (D), and leads in 6 of 7 scored categories. RouterPlus leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Azure OpenAI in Foundry Models or RouterPlus?" }, { "answer": "Azure OpenAI in Foundry Models takes an API key or an OAuth sign-in. RouterPlus needs an API key.", "question": "Do Azure OpenAI in Foundry Models and RouterPlus need an API key?" }, { "answer": "Yes. Azure OpenAI in Foundry Models has a hosted endpoint at https://\u003cresource\u003e.openai.azure.com/openai/v1 and RouterPlus at https://api.routerplus.com/v1.", "question": "Can an agent call Azure OpenAI in Foundry Models and RouterPlus without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 80 against 42", "Schema \u0026 documentation, 87 against 59", "Agent ergonomics, 98 against 71", "Security \u0026 auth, 95 against 59", "Maintenance \u0026 community, 86 against 44", "Transparency \u0026 trust, 83 against 41" ], "also": [ "Agent-ready, a grade of BB or better" ], "goodFor": "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.", "slug": "azure-openai", "watchFor": "Intermittent failures and 5xx errors in Sweden Central for about six hours on 29 September 2026" }, { "aheadOn": [ "Payments \u0026 pricing, 40 against 20" ], "also": null, "goodFor": "Teams that call Claude, GPT and open-weight models from one key and want the cost of every call in the response, with their own provider keys where they have them.", "slug": "routerplus", "watchFor": "No terms of service, privacy policy, status page, changelog or security.txt found for the gateway" } ], "history": { "azure-openai": null, "routerplus": [ { "causes": [ "product", "correction" ], "date": "2026-11-04", "delta": -1.1, "from": 51.4, "fromGrade": "D", "to": 50.3, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-28", "delta": 0.1, "from": 51.3, "fromGrade": "D", "to": 51.4, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 51.2, "fromGrade": "D", "to": 51.3, "toGrade": "D" } ] }, "job": { "capability": "inference.llm", "name": "LLM inference" }, "others": [ { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-azure-openai.json", "title": "Amazon Bedrock vs Azure OpenAI in Foundry Models", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-azure-openai" }, { "json": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-routerplus.json", "title": "Amazon Bedrock vs RouterPlus", "url": "https://www.anchorterminal.com/compare/amazon-bedrock-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/anthropic-api-vs-azure-openai.json", "title": "Claude API vs Azure OpenAI in Foundry Models", "url": "https://www.anchorterminal.com/compare/anthropic-api-vs-azure-openai" }, { "json": "https://www.anchorterminal.com/compare/anthropic-api-vs-routerplus.json", "title": "Claude API vs RouterPlus", "url": "https://www.anchorterminal.com/compare/anthropic-api-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/antseed-vs-azure-openai.json", "title": "Antseed vs Azure OpenAI in Foundry Models", "url": "https://www.anchorterminal.com/compare/antseed-vs-azure-openai" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-blockrun-ai.json", "title": "Azure OpenAI in Foundry Models vs BlockRun.AI", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-blockrun-ai" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-cerebras-inference.json", "title": "Azure OpenAI in Foundry Models vs Cerebras Inference", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-cerebras-inference" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-cloudflare-ai-gateway.json", "title": "Azure OpenAI in Foundry Models vs Cloudflare AI Gateway", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-cloudflare-ai-gateway" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-cloudflare-workers-ai.json", "title": "Azure OpenAI in Foundry Models vs Cloudflare Workers AI", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-cloudflare-workers-ai" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-cohere-chat.json", "title": "Azure OpenAI in Foundry Models vs Cohere Chat API (Command models)", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-cohere-chat" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-deepinfra.json", "title": "Azure OpenAI in Foundry Models vs DeepInfra", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-deepinfra" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-deepseek-api.json", "title": "Azure OpenAI in Foundry Models vs DeepSeek API", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-deepseek-api" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-eden-ai.json", "title": "Azure OpenAI in Foundry Models vs Eden AI", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-eden-ai" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-elorian-glimpse.json", "title": "Azure OpenAI in Foundry Models vs Glimpse", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-elorian-glimpse" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-fireworks-inference.json", "title": "Azure OpenAI in Foundry Models vs Fireworks AI Inference", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-fireworks-inference" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-gemini-api.json", "title": "Azure OpenAI in Foundry Models vs Gemini Developer API", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-gemini-api" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-groq.json", "title": "Azure OpenAI in Foundry Models vs GroqCloud", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-groq" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-hugging-face-inference-providers.json", "title": "Azure OpenAI in Foundry Models vs Hugging Face Inference Providers", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-hugging-face-inference-providers" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-inkling-2-small.json", "title": "Azure OpenAI in Foundry Models vs Inkling 2 Small", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-inkling-2-small" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-jais-3.json", "title": "Azure OpenAI in Foundry Models vs Jais 3", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-jais-3" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-meta-model-api.json", "title": "Azure OpenAI in Foundry Models vs Meta Model API", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-meta-model-api" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-minimax-api.json", "title": "Azure OpenAI in Foundry Models vs MiniMax API", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-minimax-api" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-mistral-api.json", "title": "Azure OpenAI in Foundry Models vs Mistral AI API", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-mistral-api" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-muse-spark-open.json", "title": "Azure OpenAI in Foundry Models vs Muse Spark Open", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-muse-spark-open" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-nemotron-3-5-super-vl.json", "title": "Azure OpenAI in Foundry Models vs Nemotron 3.5 Super VL", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-nemotron-3-5-super-vl" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-novita-ai.json", "title": "Azure OpenAI in Foundry Models vs Novita AI", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-novita-ai" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-openai-api.json", "title": "Azure OpenAI in Foundry Models vs OpenAI API", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-openai-api" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-openrouter.json", "title": "Azure OpenAI in Foundry Models vs OpenRouter", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-openrouter" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-prism-inference.json", "title": "Azure OpenAI in Foundry Models vs Prism Inference", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-prism-inference" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-ramp-router.json", "title": "Azure OpenAI in Foundry Models vs Router.com (Ramp Router)", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-ramp-router" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-reflection-beam.json", "title": "Azure OpenAI in Foundry Models vs Beam 1.0", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-reflection-beam" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-sambanova.json", "title": "Azure OpenAI in Foundry Models vs SambaCloud", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-sambanova" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-siliconflow.json", "title": "Azure OpenAI in Foundry Models vs SiliconFlow", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-siliconflow" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-simplismart.json", "title": "Azure OpenAI in Foundry Models vs Simplismart", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-simplismart" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-stepfun-api.json", "title": "Azure OpenAI in Foundry Models vs StepFun API", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-stepfun-api" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-swe-2-flash.json", "title": "Azure OpenAI in Foundry Models vs SWE-2 Flash", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-swe-2-flash" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-tencent-tokenhub.json", "title": "Azure OpenAI in Foundry Models vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-together-inference.json", "title": "Azure OpenAI in Foundry Models vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-vercel-ai-gateway.json", "title": "Azure OpenAI in Foundry Models vs Vercel AI Gateway", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-vercel-ai-gateway" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-vertex-ai.json", "title": "Azure OpenAI in Foundry Models vs Vertex AI (Gemini Enterprise Agent Platform)", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-vertex-ai" }, { "json": "https://www.anchorterminal.com/compare/azure-openai-vs-xai-api.json", "title": "Azure OpenAI in Foundry Models vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-xai-api" }, { "json": "https://www.anchorterminal.com/compare/blockrun-ai-vs-routerplus.json", "title": "BlockRun.AI vs RouterPlus", "url": "https://www.anchorterminal.com/compare/blockrun-ai-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/cerebras-inference-vs-routerplus.json", "title": "Cerebras Inference vs RouterPlus", "url": "https://www.anchorterminal.com/compare/cerebras-inference-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-routerplus.json", "title": "Cloudflare AI Gateway vs RouterPlus", "url": "https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-routerplus.json", "title": "Cloudflare Workers AI vs RouterPlus", "url": "https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/cohere-chat-vs-routerplus.json", "title": "Cohere Chat API (Command models) vs RouterPlus", "url": "https://www.anchorterminal.com/compare/cohere-chat-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/deepinfra-vs-routerplus.json", "title": "DeepInfra vs RouterPlus", "url": "https://www.anchorterminal.com/compare/deepinfra-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/deepseek-api-vs-routerplus.json", "title": "DeepSeek API vs RouterPlus", "url": "https://www.anchorterminal.com/compare/deepseek-api-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-routerplus.json", "title": "Glimpse vs RouterPlus", "url": "https://www.anchorterminal.com/compare/elorian-glimpse-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/fireworks-inference-vs-routerplus.json", "title": "Fireworks AI Inference vs RouterPlus", "url": "https://www.anchorterminal.com/compare/fireworks-inference-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/gemini-api-vs-routerplus.json", "title": "Gemini Developer API vs RouterPlus", "url": "https://www.anchorterminal.com/compare/gemini-api-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/groq-vs-routerplus.json", "title": "GroqCloud vs RouterPlus", "url": "https://www.anchorterminal.com/compare/groq-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/inkling-2-small-vs-routerplus.json", "title": "Inkling 2 Small vs RouterPlus", "url": "https://www.anchorterminal.com/compare/inkling-2-small-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/jais-3-vs-routerplus.json", "title": "Jais 3 vs RouterPlus", "url": "https://www.anchorterminal.com/compare/jais-3-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/meta-model-api-vs-routerplus.json", "title": "Meta Model API vs RouterPlus", "url": "https://www.anchorterminal.com/compare/meta-model-api-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/minimax-api-vs-routerplus.json", "title": "MiniMax API vs RouterPlus", "url": "https://www.anchorterminal.com/compare/minimax-api-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/mistral-api-vs-routerplus.json", "title": "Mistral AI API vs RouterPlus", "url": "https://www.anchorterminal.com/compare/mistral-api-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/muse-spark-open-vs-routerplus.json", "title": "Muse Spark Open vs RouterPlus", "url": "https://www.anchorterminal.com/compare/muse-spark-open-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/nemotron-3-5-super-vl-vs-routerplus.json", "title": "Nemotron 3.5 Super VL vs RouterPlus", "url": "https://www.anchorterminal.com/compare/nemotron-3-5-super-vl-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/novita-ai-vs-routerplus.json", "title": "Novita AI vs RouterPlus", "url": "https://www.anchorterminal.com/compare/novita-ai-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/openai-api-vs-routerplus.json", "title": "OpenAI API vs RouterPlus", "url": "https://www.anchorterminal.com/compare/openai-api-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/openrouter-vs-routerplus.json", "title": "OpenRouter vs RouterPlus", "url": "https://www.anchorterminal.com/compare/openrouter-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/prism-inference-vs-routerplus.json", "title": "Prism Inference vs RouterPlus", "url": "https://www.anchorterminal.com/compare/prism-inference-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/reflection-beam-vs-routerplus.json", "title": "Beam 1.0 vs RouterPlus", "url": "https://www.anchorterminal.com/compare/reflection-beam-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/routerplus-vs-sambanova.json", "title": "RouterPlus vs SambaCloud", "url": "https://www.anchorterminal.com/compare/routerplus-vs-sambanova" }, { "json": "https://www.anchorterminal.com/compare/routerplus-vs-siliconflow.json", "title": "RouterPlus vs SiliconFlow", "url": "https://www.anchorterminal.com/compare/routerplus-vs-siliconflow" }, { "json": "https://www.anchorterminal.com/compare/routerplus-vs-simplismart.json", "title": "RouterPlus vs Simplismart", "url": "https://www.anchorterminal.com/compare/routerplus-vs-simplismart" }, { "json": "https://www.anchorterminal.com/compare/routerplus-vs-stepfun-api.json", "title": "RouterPlus vs StepFun API", "url": "https://www.anchorterminal.com/compare/routerplus-vs-stepfun-api" }, { "json": "https://www.anchorterminal.com/compare/routerplus-vs-swe-2-flash.json", "title": "RouterPlus vs SWE-2 Flash", "url": "https://www.anchorterminal.com/compare/routerplus-vs-swe-2-flash" }, { "json": "https://www.anchorterminal.com/compare/routerplus-vs-together-inference.json", "title": "RouterPlus vs Together AI Inference", "url": "https://www.anchorterminal.com/compare/routerplus-vs-together-inference" }, { "json": "https://www.anchorterminal.com/compare/routerplus-vs-vertex-ai.json", "title": "RouterPlus vs Vertex AI (Gemini Enterprise Agent Platform)", "url": "https://www.anchorterminal.com/compare/routerplus-vs-vertex-ai" }, { "json": "https://www.anchorterminal.com/compare/routerplus-vs-xai-api.json", "title": "RouterPlus vs xAI API (Grok)", "url": "https://www.anchorterminal.com/compare/routerplus-vs-xai-api" }, { "json": "https://www.anchorterminal.com/compare/antseed-vs-routerplus.json", "title": "Antseed vs RouterPlus", "url": "https://www.anchorterminal.com/compare/antseed-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/eden-ai-vs-routerplus.json", "title": "Eden AI vs RouterPlus", "url": "https://www.anchorterminal.com/compare/eden-ai-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-routerplus.json", "title": "Hugging Face Inference Providers vs RouterPlus", "url": "https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/litellm-vs-routerplus.json", "title": "LiteLLM vs RouterPlus", "url": "https://www.anchorterminal.com/compare/litellm-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/ramp-router-vs-routerplus.json", "title": "Router.com (Ramp Router) vs RouterPlus", "url": "https://www.anchorterminal.com/compare/ramp-router-vs-routerplus" }, { "json": "https://www.anchorterminal.com/compare/routerplus-vs-tencent-tokenhub.json", "title": "RouterPlus vs Tencent Cloud TokenHub", "url": "https://www.anchorterminal.com/compare/routerplus-vs-tencent-tokenhub" }, { "json": "https://www.anchorterminal.com/compare/routerplus-vs-vercel-ai-gateway.json", "title": "RouterPlus vs Vercel AI Gateway", "url": "https://www.anchorterminal.com/compare/routerplus-vs-vercel-ai-gateway" } ], "panel": null, "scores": [ { "azure-openai": 80, "by": 38, "edge": "azure-openai", "key": "reliability", "name": "Reliability", "routerplus": 42, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "azure-openai": 87, "by": 28, "edge": "azure-openai", "key": "schema", "name": "Schema \u0026 documentation", "routerplus": 59, "weight": 13 }, { "azure-openai": 98, "by": 27, "edge": "azure-openai", "key": "ergonomics", "name": "Agent ergonomics", "routerplus": 71, "weight": 13 }, { "azure-openai": 95, "by": 36, "edge": "azure-openai", "key": "security", "name": "Security \u0026 auth", "routerplus": 59, "weight": 14 }, { "azure-openai": 20, "by": 20, "edge": "routerplus", "key": "payments", "name": "Payments \u0026 pricing", "routerplus": 40, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "azure-openai": 86, "by": 42, "edge": "azure-openai", "key": "maintenance", "name": "Maintenance \u0026 community", "routerplus": 44, "weight": 7 }, { "azure-openai": 83, "by": 42, "edge": "azure-openai", "key": "transparency", "name": "Transparency \u0026 trust", "routerplus": 41, "weight": 7 } ], "summary": "Azure OpenAI in Foundry Models scores 80 (A) on agent readiness against RouterPlus's 50.3 (D), and leads in 6 of 7 scored categories. RouterPlus leads on payments \u0026 pricing. Both do llm inference.", "tasks": null, "tutorials": [], "verdicts": { "azure-openai": "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.", "routerplus": "The docs are written for agents, every model price is public, and each response carries its own cost. No terms of service, privacy policy, status page or changelog were found. Request content is now logged for 30 days by default while the homepage says prompts aren't stored, and signup adds no free credit." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/azure-openai-vs-routerplus", "json": "https://www.anchorterminal.com/compare/azure-openai-vs-routerplus.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/azure-openai-vs-routerplus.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/azure-openai-vs-routerplus.min.md" }, "markdown": "Azure OpenAI in Foundry Models scores 80 (A) on agent readiness against RouterPlus's 50.3 (D), and leads in 6 of 7 scored categories. RouterPlus leads on payments \u0026 pricing. Both do llm inference.\n\n- Azure OpenAI in Foundry Models: grade A, 80/100, rank #14 of 1486. Markdown https://www.anchorterminal.com/tools/azure-openai.md · JSON https://www.anchorterminal.com/api/v1/tools/azure-openai.json\n- RouterPlus: grade D, 50.3/100, rank #1061 of 1486. Markdown https://www.anchorterminal.com/tools/routerplus.md · JSON https://www.anchorterminal.com/api/v1/tools/routerplus.json\n- Best model APIs and inference for AI agents: https://www.anchorterminal.com/best/inference/index.md\n- All 830 models comparisons: https://www.anchorterminal.com/compare/inference/index.md\n\n## Which one, for what\n\n### Azure OpenAI in Foundry Models (A)\n\nGood 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.\n\nAhead on:\n- Reliability, 80 against 42\n- Schema \u0026 documentation, 87 against 59\n- Agent ergonomics, 98 against 71\n- Security \u0026 auth, 95 against 59\n- Maintenance \u0026 community, 86 against 44\n- Transparency \u0026 trust, 83 against 41\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n\nWatch for: Intermittent failures and 5xx errors in Sweden Central for about six hours on 29 September 2026\n\n### RouterPlus (D)\n\nGood for: Teams that call Claude, GPT and open-weight models from one key and want the cost of every call in the response, with their own provider keys where they have them.\n\nAhead on:\n- Payments \u0026 pricing, 40 against 20\n\nWatch for: No terms of service, privacy policy, status page, changelog or security.txt found for the gateway\n\n\n## Why the edge\n\n### Maintenance \u0026 community: Azure OpenAI in Foundry Models +42\n\n- 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\u0026A 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).\n- RouterPlus (44): Router, read on the model lines. No changelog or release notes found. The blog, re-read on 4 November 2026, dates the launch of ScaleDown's extract-1 and summarize-1 on chat completions and classify-1 on the decisions API to 13 October 2026, and the catalogue now lists 105 chat models against 19 on 13 October, so the API changed within the last 30 days (30). The docs also date a console change on 17 October 2026 (keys can be copied again), which isn't counted, since it changes the console and not the API. Models carry a `deprecation_date` that delists them automatically, with no notice period stated (3 of 12). `POST /v1/signup` and the magic-link route were removed and Optimize is paused, none with a date we could find (3 of 8). No public changelog. Support is reached through the console and an email address, and wasn't tested (3 of 15). No public issue tracker for the gateway (0 of 10). No official SDK. The docs rely on the OpenAI and Anthropic SDKs and give client setups (5 of 15). No package or public repository to check (0 of 10).\n\n### Transparency \u0026 trust: Azure OpenAI in Foundry Models +42\n\n- 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).\n- RouterPlus (41): Closed service with no terms of service found. The only terms on the site govern the capacity request form, under EVO HQ Inc (0 of 30). The data policy page is detailed, lists what is stored and why, and gives a 30-day period for request logs and each provider's retention flag. Its 4 November 2026 text, which logs request content by default, no longer agrees with the homepage FAQ; that contradiction is charged once as a misleading claim under negative events, not on this line. There is no privacy policy, no DPA and no retention period for account data such as email addresses (14 of 30, held). Model retirement by `deprecation_date` is documented with no notice period, and no dated deprecation notices were found (4 of 20). The docs name Clerk, Resend and an AWS bucket, and say RouterPlus's own GPUs run in the United States. The form's terms name Supabase, Cloudflare and Resend. No complete subprocessor list or gateway hosting location was found (8 of 20).\n\n### Reliability: Azure OpenAI in Foundry Models +38\n\n- 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).\n- RouterPlus (42): Hosted reading. No status page found. Model pages show each provider's uptime over the last 24 hours and no incident history, and status.routerplus.com failed at our proxy again on 4 November 2026 (0). No readable incident history (5). The limits page, re-read on 4 November 2026, gives 20 requests a minute until the organisation's first purchase, then 300 per console key and 60 for the managed Playground key, with token-per-minute and in-flight limits per organisation and key (15). Rate-limit 429s carry `retry-after` from 1 to 59 seconds and `metadata.retry_at`, the errors page gives a retry or no-retry rule for each error class, and the docs say a retry is a new billed request because there is no idempotency key. That is safe-retry guidance without keys on the billed call, the value this run settled for routers such as ramp-router (12, 15 before). The homepage says \"Production-grade SLAs\", but no SLA terms were found, and the only terms on the site say a stated response time is not a service level (0). The chat and messages surfaces carry no beta label. The Responses API is a preview for non-OpenAI models and Optimize is paused, neither of which is the main surface (10). 0 + 5 + 15 + 12 + 0 + 10 = 42.\n\n### Security \u0026 auth: Azure OpenAI in Foundry Models +36\n\n- 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).\n- RouterPlus (59): Router, read on the model lines. `tm_vk_` keys are stored as SHA-256 hashes and revocable, each bound to a workspace and principal, with per-key RPM and monthly spend caps. Since 17 October 2026 the console also keeps an encrypted copy so an owner or admin can copy a key again, and an organisation can ask for copying to be turned off. Inference keys have no management rights. There are no permission scopes on a key and no SSO or SCIM (24 of 30). RouterPlus says it does not train on request logs and does not share them, and deletes them after 30 days. Most Claude and GPT routes are marked `prompt_logging: retained` with no ZDR, so retention and training upstream rest on each provider's API terms, while DeepInfra's open models, Perplexity, Cloudflare Workers AI, Fastino and RouterPlus's own models declare `none` (12 of 20, held). The data policy re-read on 4 November 2026 says requests and responses to non-dedicated endpoints are now logged by default for up to 30 days for debugging, with recognised keys removed. On 13 October it said content was kept only for hackathon accounts. Opting out takes a request to support, dedicated endpoints are excluded, and the `zdr` and `data_collection: deny` filters still remove every marketplace route, so they work only on the caller's own provider keys. Cloudflare AI Gateway, with default logging and a per-request header to switch it off, has 11 here (7 of 15, 10 before). `GET /v1/generation` lists every attempt behind a request with provider, tokens and cost, and the console has usage and logs (14 of 15). No security.txt (404 on both hosts on 4 November 2026), disclosure policy, bug bounty or certification found. The footer's Security link is an email to founders@evo-hq.com (2 of 20). 24 + 12 + 7 + 14 + 2 = 59.\n\n### Schema \u0026 documentation: Azure OpenAI in Foundry Models +28\n\n- 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).\n- RouterPlus (59): Router, scored on the API lines. No OpenAPI or other machine-readable contract for the gateway was found. It follows the OpenAI and Anthropic wire formats, which this checklist doesn't credit to a reseller, the same reading as Antseed (0 of 25). llms.txt, llms-full.txt and a Markdown copy of every page (10). Each route page says what it is for, what isn't available, and which route to use for which model, and the agent integration guide lists what not to build on (18 of 20). Request fields follow the upstream formats, and the wire compatibility page tables which fields pass, translate, drop or fail with a typed 400 (12 of 15). Curl, Python and TypeScript examples on every page, and an error reference with a class, status and remedy for each error (15). Routes are versioned under /v1 and the wire compatibility page says changing it needs a recorded decision, but no changelog or dated release notes were found, re-read on 4 November 2026 (4 of 15).\n\n### Agent ergonomics: Azure OpenAI in Foundry Models +27\n\n- 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.\n- RouterPlus (71): Router, read on the model lines (tool use, structured output, caching, context, batch, SDKs, errors). Tools pass through on both surfaces, and Anthropic server tools such as web search work for Claude models on `/v1/messages`. Behaviour depends on the model (15 of 20). `response_format` works for GPT ids and the open models (re-read on 4 November 2026), and the docs tell callers to get JSON from Claude through a single tool, so structured output still rests on the provider (8 of 15, held). Cached-input and cache-write prices per model, a session id that keeps provider caches warm, and `cache_control` on the Anthropic surface (13 of 15). The catalogue's largest contexts are 1,050,000 tokens on GPT-6.1 Sol and 1,000,000 on Claude Sonnet 5.5, a judgement call since a router has no default model (15). No batch route (0 of 10). No SDK of its own. The OpenAI and Anthropic SDKs work with a changed base URL, and the docs give setups for ten coding tools (5 of 10). A stable `error_type` in every body and header, an origin header, the limit that refused a request, and `x-tm-dropped-params` naming every dropped field (15).\n\n## Score by category\n\n| Category | Weight | Azure OpenAI in Foundry Models | RouterPlus | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 80 | 42 | Azure OpenAI in Foundry Models +38 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 87 | 59 | Azure OpenAI in Foundry Models +28 |\n| Agent ergonomics | 13% (16.2 this run) | 98 | 71 | Azure OpenAI in Foundry Models +27 |\n| Security \u0026 auth | 14% (17.5 this run) | 95 | 59 | Azure OpenAI in Foundry Models +36 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 40 | RouterPlus +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 86 | 44 | Azure OpenAI in Foundry Models +42 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 83 | 41 | Azure OpenAI in Foundry Models +42 |\n| Negative events | ≤15 | 0 | -2 | |\n| **Total** | | **80 · A** | **50.3 · D** | |\n\n## Facts side by side\n\n| Fact | Azure OpenAI in Foundry Models | RouterPlus |\n| --- | --- | --- |\n| Kind | Model API | Model router |\n| Vendor | Microsoft | RouterPlus |\n| Hosted endpoint | `https://\u003cresource\u003e.openai.azure.com/openai/v1` | `https://api.routerplus.com/v1` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth or key | API key |\n| Pricing | Pay per use | Pay per use |\n| x402 | no | no |\n| Licence | Proprietary service under the Microsoft Product Terms. The v1 OpenAPI spec is MIT, and the OpenAI SDKs the docs use are Apache-2.0 | Closed service. No terms of service for the gateway were found on routerplus.com or app.routerplus.com on 13 October 2026. The only terms on the site govern the capacity request form and name EVO HQ Inc, a Delaware corporation (https://routerplus.com/capacity/terms/). |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | 2026-10-26 | none |\n| Terms last updated | no date given | no document linked |\n| Privacy policy last updated | 2026-09-01 | no document linked |\n| Customer content may train models | yes | not read yet |\n| Terms restrict automated access | yes | not read yet |\n| Terms restrict benchmarking | yes | not read yet |\n| Terms or service can change without notice | not found in the text | not read yet |\n| Arbitration or class-action waiver | not found in the text | not read yet |\n| Popularity | 454k npm/wk | none |\n\n## How the scores have moved\n\n### Azure OpenAI in Foundry Models\n\nNo score change since it was listed.\n\n### RouterPlus\n\n- -1.1 on 4 November 2026: product, correction\n- +0.1 on 28 October 2026: checklist\n- +0.1 on 27 October 2026: checklist\n\n## Verdicts\n\n**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.\n\n**RouterPlus.** The docs are written for agents, every model price is public, and each response carries its own cost. No terms of service, privacy policy, status page or changelog were found. Request content is now logged for 30 days by default while the homepage says prompts aren't stored, and signup adds no free credit.\n\n## Before you call either\n\n### Azure OpenAI in Foundry Models\n\n1. Point the OpenAI SDK at https://\u003cresource\u003e.openai.azure.com/openai/v1/ and pass the deployment name as `model`, not the model id\n2. Prefer Entra ID with the Cognitive Services OpenAI User role over the resource key, which opens the whole data plane\n3. On 429 wait for `retry-after-ms`, then back off with jitter. The OpenAI SDK retries twice by default\n4. Set `store: false` on Responses calls you don't need kept. Stored responses persist 30 days by default\n5. Keep remote MCP approvals on for servers you don't control. They're required by default\n\n### RouterPlus\n\n1. Send `max_tokens` on every request. Without it the balance hold assumes up to 32,768 output tokens and can return `insufficient_quota` on a small balance\n2. Switch on `error_type`. Retry `rate_limit` after `retry-after`, and stop on `insufficient_quota`, which needs a person to add credit or raise a cap\n3. Don't add a retry loop on top of the SDK's. There is no idempotency key, so a retry that reaches a provider is billed again\n4. Keep secrets out of prompts. Request content is logged for up to 30 days unless the organisation has opted out through support\n5. Use `/v1/messages` for Claude when you need `thinking` or server tools. `response_format` works for GPT ids and open models, not Claude\n\n## Questions\n\n### Which is better for AI agents, Azure OpenAI in Foundry Models or RouterPlus?\n\nAzure OpenAI in Foundry Models scores 80 (A) on agent readiness against RouterPlus's 50.3 (D), and leads in 6 of 7 scored categories. RouterPlus leads on payments \u0026 pricing.\n\n### Do Azure OpenAI in Foundry Models and RouterPlus need an API key?\n\nAzure OpenAI in Foundry Models takes an API key or an OAuth sign-in. RouterPlus needs an API key.\n\n### Can an agent call Azure OpenAI in Foundry Models and RouterPlus without installing anything?\n\nYes. Azure OpenAI in Foundry Models has a hosted endpoint at https://\u003cresource\u003e.openai.azure.com/openai/v1 and RouterPlus at https://api.routerplus.com/v1.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/azure-openai-vs-routerplus.json, and with the fewest tokens: https://www.anchorterminal.com/compare/azure-openai-vs-routerplus.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"azure-openai\", \"b\": \"routerplus\"}`. From a terminal: `anchor compare azure-openai routerplus`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/azure-openai.json and https://www.anchorterminal.com/api/v1/tools/routerplus.json\n\n## Other comparisons with Azure OpenAI in Foundry Models or RouterPlus\n\n- [Amazon Bedrock vs Azure OpenAI in Foundry Models](https://www.anchorterminal.com/compare/amazon-bedrock-vs-azure-openai.md)\n- [Amazon Bedrock vs RouterPlus](https://www.anchorterminal.com/compare/amazon-bedrock-vs-routerplus.md)\n- [Claude API vs Azure OpenAI in Foundry Models](https://www.anchorterminal.com/compare/anthropic-api-vs-azure-openai.md)\n- [Claude API vs RouterPlus](https://www.anchorterminal.com/compare/anthropic-api-vs-routerplus.md)\n- [Antseed vs Azure OpenAI in Foundry Models](https://www.anchorterminal.com/compare/antseed-vs-azure-openai.md)\n- [Azure OpenAI in Foundry Models vs BlockRun.AI](https://www.anchorterminal.com/compare/azure-openai-vs-blockrun-ai.md)\n- [Azure OpenAI in Foundry Models vs Cerebras Inference](https://www.anchorterminal.com/compare/azure-openai-vs-cerebras-inference.md)\n- [Azure OpenAI in Foundry Models vs Cloudflare AI Gateway](https://www.anchorterminal.com/compare/azure-openai-vs-cloudflare-ai-gateway.md)\n- [Azure OpenAI in Foundry Models vs Cloudflare Workers AI](https://www.anchorterminal.com/compare/azure-openai-vs-cloudflare-workers-ai.md)\n- [Azure OpenAI in Foundry Models vs Cohere Chat API (Command models)](https://www.anchorterminal.com/compare/azure-openai-vs-cohere-chat.md)\n- [Azure OpenAI in Foundry Models vs DeepInfra](https://www.anchorterminal.com/compare/azure-openai-vs-deepinfra.md)\n- [Azure OpenAI in Foundry Models vs DeepSeek API](https://www.anchorterminal.com/compare/azure-openai-vs-deepseek-api.md)\n- [Azure OpenAI in Foundry Models vs Eden AI](https://www.anchorterminal.com/compare/azure-openai-vs-eden-ai.md)\n- [Azure OpenAI in Foundry Models vs Glimpse](https://www.anchorterminal.com/compare/azure-openai-vs-elorian-glimpse.md)\n- [Azure OpenAI in Foundry Models vs Fireworks AI Inference](https://www.anchorterminal.com/compare/azure-openai-vs-fireworks-inference.md)\n- [Azure OpenAI in Foundry Models vs Gemini Developer API](https://www.anchorterminal.com/compare/azure-openai-vs-gemini-api.md)\n- [Azure OpenAI in Foundry Models vs GroqCloud](https://www.anchorterminal.com/compare/azure-openai-vs-groq.md)\n- [Azure OpenAI in Foundry Models vs Hugging Face Inference Providers](https://www.anchorterminal.com/compare/azure-openai-vs-hugging-face-inference-providers.md)\n- [Azure OpenAI in Foundry Models vs Inkling 2 Small](https://www.anchorterminal.com/compare/azure-openai-vs-inkling-2-small.md)\n- [Azure OpenAI in Foundry Models vs Jais 3](https://www.anchorterminal.com/compare/azure-openai-vs-jais-3.md)\n- [Azure OpenAI in Foundry Models vs Meta Model API](https://www.anchorterminal.com/compare/azure-openai-vs-meta-model-api.md)\n- [Azure OpenAI in Foundry Models vs MiniMax API](https://www.anchorterminal.com/compare/azure-openai-vs-minimax-api.md)\n- [Azure OpenAI in Foundry Models vs Mistral AI API](https://www.anchorterminal.com/compare/azure-openai-vs-mistral-api.md)\n- [Azure OpenAI in Foundry Models vs Muse Spark Open](https://www.anchorterminal.com/compare/azure-openai-vs-muse-spark-open.md)\n- [Azure OpenAI in Foundry Models vs Nemotron 3.5 Super VL](https://www.anchorterminal.com/compare/azure-openai-vs-nemotron-3-5-super-vl.md)\n- [Azure OpenAI in Foundry Models vs Novita AI](https://www.anchorterminal.com/compare/azure-openai-vs-novita-ai.md)\n- [Azure OpenAI in Foundry Models vs OpenAI API](https://www.anchorterminal.com/compare/azure-openai-vs-openai-api.md)\n- [Azure OpenAI in Foundry Models vs OpenRouter](https://www.anchorterminal.com/compare/azure-openai-vs-openrouter.md)\n- [Azure OpenAI in Foundry Models vs Prism Inference](https://www.anchorterminal.com/compare/azure-openai-vs-prism-inference.md)\n- [Azure OpenAI in Foundry Models vs Router.com (Ramp Router)](https://www.anchorterminal.com/compare/azure-openai-vs-ramp-router.md)\n- [Azure OpenAI in Foundry Models vs Beam 1.0](https://www.anchorterminal.com/compare/azure-openai-vs-reflection-beam.md)\n- [Azure OpenAI in Foundry Models vs SambaCloud](https://www.anchorterminal.com/compare/azure-openai-vs-sambanova.md)\n- [Azure OpenAI in Foundry Models vs SiliconFlow](https://www.anchorterminal.com/compare/azure-openai-vs-siliconflow.md)\n- [Azure OpenAI in Foundry Models vs Simplismart](https://www.anchorterminal.com/compare/azure-openai-vs-simplismart.md)\n- [Azure OpenAI in Foundry Models vs StepFun API](https://www.anchorterminal.com/compare/azure-openai-vs-stepfun-api.md)\n- [Azure OpenAI in Foundry Models vs SWE-2 Flash](https://www.anchorterminal.com/compare/azure-openai-vs-swe-2-flash.md)\n- [Azure OpenAI in Foundry Models vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/azure-openai-vs-tencent-tokenhub.md)\n- [Azure OpenAI in Foundry Models vs Together AI Inference](https://www.anchorterminal.com/compare/azure-openai-vs-together-inference.md)\n- [Azure OpenAI in Foundry Models vs Vercel AI Gateway](https://www.anchorterminal.com/compare/azure-openai-vs-vercel-ai-gateway.md)\n- [Azure OpenAI in Foundry Models vs Vertex AI (Gemini Enterprise Agent Platform)](https://www.anchorterminal.com/compare/azure-openai-vs-vertex-ai.md)\n- [Azure OpenAI in Foundry Models vs xAI API (Grok)](https://www.anchorterminal.com/compare/azure-openai-vs-xai-api.md)\n- [BlockRun.AI vs RouterPlus](https://www.anchorterminal.com/compare/blockrun-ai-vs-routerplus.md)\n- [Cerebras Inference vs RouterPlus](https://www.anchorterminal.com/compare/cerebras-inference-vs-routerplus.md)\n- [Cloudflare AI Gateway vs RouterPlus](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-routerplus.md)\n- [Cloudflare Workers AI vs RouterPlus](https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-routerplus.md)\n- [Cohere Chat API (Command models) vs RouterPlus](https://www.anchorterminal.com/compare/cohere-chat-vs-routerplus.md)\n- [DeepInfra vs RouterPlus](https://www.anchorterminal.com/compare/deepinfra-vs-routerplus.md)\n- [DeepSeek API vs RouterPlus](https://www.anchorterminal.com/compare/deepseek-api-vs-routerplus.md)\n- [Glimpse vs RouterPlus](https://www.anchorterminal.com/compare/elorian-glimpse-vs-routerplus.md)\n- [Fireworks AI Inference vs RouterPlus](https://www.anchorterminal.com/compare/fireworks-inference-vs-routerplus.md)\n- [Gemini Developer API vs RouterPlus](https://www.anchorterminal.com/compare/gemini-api-vs-routerplus.md)\n- [GroqCloud vs RouterPlus](https://www.anchorterminal.com/compare/groq-vs-routerplus.md)\n- [Inkling 2 Small vs RouterPlus](https://www.anchorterminal.com/compare/inkling-2-small-vs-routerplus.md)\n- [Jais 3 vs RouterPlus](https://www.anchorterminal.com/compare/jais-3-vs-routerplus.md)\n- [Meta Model API vs RouterPlus](https://www.anchorterminal.com/compare/meta-model-api-vs-routerplus.md)\n- [MiniMax API vs RouterPlus](https://www.anchorterminal.com/compare/minimax-api-vs-routerplus.md)\n- [Mistral AI API vs RouterPlus](https://www.anchorterminal.com/compare/mistral-api-vs-routerplus.md)\n- [Muse Spark Open vs RouterPlus](https://www.anchorterminal.com/compare/muse-spark-open-vs-routerplus.md)\n- [Nemotron 3.5 Super VL vs RouterPlus](https://www.anchorterminal.com/compare/nemotron-3-5-super-vl-vs-routerplus.md)\n- [Novita AI vs RouterPlus](https://www.anchorterminal.com/compare/novita-ai-vs-routerplus.md)\n- [OpenAI API vs RouterPlus](https://www.anchorterminal.com/compare/openai-api-vs-routerplus.md)\n- [OpenRouter vs RouterPlus](https://www.anchorterminal.com/compare/openrouter-vs-routerplus.md)\n- [Prism Inference vs RouterPlus](https://www.anchorterminal.com/compare/prism-inference-vs-routerplus.md)\n- [Beam 1.0 vs RouterPlus](https://www.anchorterminal.com/compare/reflection-beam-vs-routerplus.md)\n- [RouterPlus vs SambaCloud](https://www.anchorterminal.com/compare/routerplus-vs-sambanova.md)\n- [RouterPlus vs SiliconFlow](https://www.anchorterminal.com/compare/routerplus-vs-siliconflow.md)\n- [RouterPlus vs Simplismart](https://www.anchorterminal.com/compare/routerplus-vs-simplismart.md)\n- [RouterPlus vs StepFun API](https://www.anchorterminal.com/compare/routerplus-vs-stepfun-api.md)\n- [RouterPlus vs SWE-2 Flash](https://www.anchorterminal.com/compare/routerplus-vs-swe-2-flash.md)\n- [RouterPlus vs Together AI Inference](https://www.anchorterminal.com/compare/routerplus-vs-together-inference.md)\n- [RouterPlus vs Vertex AI (Gemini Enterprise Agent Platform)](https://www.anchorterminal.com/compare/routerplus-vs-vertex-ai.md)\n- [RouterPlus vs xAI API (Grok)](https://www.anchorterminal.com/compare/routerplus-vs-xai-api.md)\n- [Antseed vs RouterPlus](https://www.anchorterminal.com/compare/antseed-vs-routerplus.md)\n- [Eden AI vs RouterPlus](https://www.anchorterminal.com/compare/eden-ai-vs-routerplus.md)\n- [Hugging Face Inference Providers vs RouterPlus](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-routerplus.md)\n- [LiteLLM vs RouterPlus](https://www.anchorterminal.com/compare/litellm-vs-routerplus.md)\n- [Router.com (Ramp Router) vs RouterPlus](https://www.anchorterminal.com/compare/ramp-router-vs-routerplus.md)\n- [RouterPlus vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/routerplus-vs-tencent-tokenhub.md)\n- [RouterPlus vs Vercel AI Gateway](https://www.anchorterminal.com/compare/routerplus-vs-vercel-ai-gateway.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Azure OpenAI in Foundry Models vs RouterPlus", "url": "" } ], "description": "Azure OpenAI in Foundry Models scores 80 (A) to RouterPlus's 50.3 (D) for llm inference. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Azure OpenAI in Foundry Models A 80", "RouterPlus D 50.3", "scores" ], "h1": "Azure OpenAI in Foundry Models vs RouterPlus", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/azure-openai-vs-routerplus", "published": "2026-10-01", "section": "tools", "title": "Azure OpenAI in Foundry Models vs RouterPlus for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/azure-openai-vs-routerplus" }, "tokens": { "markdown": 8050, "slim": 4480 }, "version": 1 }