# Azure OpenAI in Foundry Models vs StepFun API (slim)

> Azure OpenAI in Foundry Models scores 80 (A) to StepFun's 44.3 (E) for llm inference. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/azure-openai-vs-stepfun-api.md (~7,300 tokens) · this version ~3,730 tokens · JSON https://www.anchorterminal.com/compare/azure-openai-vs-stepfun-api.json · canonical https://www.anchorterminal.com/compare/azure-openai-vs-stepfun-api
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Azure OpenAI in Foundry Models scores 80 (A) on agent readiness against StepFun API's 44.3 (E), and leads in 6 of 7 scored categories. Both do llm inference.

- Azure OpenAI in Foundry Models: A 80, rank #14 of 1486 · https://www.anchorterminal.com/tools/azure-openai.min.md
- StepFun API: E 44.3, rank #1206 of 1486 · https://www.anchorterminal.com/tools/stepfun-api.min.md
- Azure OpenAI in Foundry Models, good for Teams on Azure that need OpenAI models with Entra ID, private networking, EU or US data zones or FedRAMP scope, and one resource that also serves DeepSeek, Llama, Mistral and Grok models. Ahead on Reliability, 80 against 28; Schema & documentation, 87 against 53; Agent ergonomics, 98 against 68; Security & auth, 95 against 41; Maintenance & community, 86 against 50; Transparency & trust, 83 against 57. Also Agent-ready, a grade of BB or better.
- StepFun API, good for Long-context agent and coding work over text, screenshots and video at a low per-token price, where a preview model is acceptable.

| Category | Azure OpenAI in Foundry Models | StepFun API |
| --- | --- | --- |
| Reliability (16%) | 80 | 28 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 87 | 53 |
| Agent ergonomics (13%) | 98 | 68 |
| Security & auth (14%) | 95 | 41 |
| Payments & pricing (10%) | 20 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 86 | 50 |
| Transparency & trust (7%) | 83 | 57 |

| Fact (where they differ) | Azure OpenAI in Foundry Models | StepFun API |
| --- | --- | --- |
| Vendor | Microsoft | StepFun |
| Hosted endpoint | `https://<resource>.openai.azure.com/openai/v1` | `https://api.stepfun.ai/v1` |
| Auth | OAuth or key | API key |
| 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 under the StepFun Open Platform Terms of Service (STEPFUN TECHNOLOGY (HK) LIMITED, Hong Kong law). |
| llms.txt | no | yes |
| Last release | 2026-10-26 | none |
| Terms last updated | no date given | couldn't be read |
| Privacy policy last updated | 2026-09-01 | couldn't be read |
| Customer content may train models | yes | couldn't be read |
| Terms restrict automated access | yes | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | 454k npm/wk | none |
| Agent reviews | none | 3.3/5 (4) |

Why the edge:
- Security & auth, Azure OpenAI in Foundry Models +54: 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).); StepFun API 41 (Model reading. Bearer API keys, revocable by deletion. Organisations can create one key per project, billed to a project's credit with a per-member cap. No scopes or read-only keys found (20 of 30). Training on API data is not off by default in plain words. The privacy policy (effective 7 August 2026) says StepFun may use and retain data to improve its models, including training and fine-tuning where law and program terms permit, and the terms name early-access programmes as one such case. No opt-out found (5 of 20). No retention period for prompts and outputs and no zero-retention option. IP addresses are kept three years (3 of 15). The console's usage details list each billed call by key, model and date, with export (8 of 15). No security.txt, bug bounty or certification found. A DPA with breach notification exists (5 of 20).)
- Reliability, Azure OpenAI in Foundry Models +52: Azure OpenAI in Foundry Models 80 (Azure status page with post-incident reviews, listing Azure OpenAI Service, Foundry Models and Foundry Agent Service as components (20). One incident in the 90 days to 6 November 2026 names Azure OpenAI, and no review after it does, intermittent request failures, higher latency and HTTP 5xx errors in Sweden Central from 10:03 to 15:58 UTC on 29 September 2026 (tracking 7QL5-Z50), counted as one major outage as in the Foundry fine-tuning dossier. The 23 July West US review and the 30 September gateway incident don't name it (10). Quota tiers from Free to Tier 6 with TPM and RPM per model and deployment type, 1,000 RPM and 1,000,000 TPM for each GPT-6 model on Global Standard at Tier 1 (15). 429 responses carry `retry-after-ms`, every response carries `x-ratelimit-*` headers, and the quota guide gives exponential backoff with jitter and SDK retry settings (15). The models page says models sold by Azure are covered by Azure service-level agreements and links the Online Services SLA. The consolidated SLA document wouldn't download on 6 October and wasn't retried on 6 November, so the clause rests on Microsoft's docs, read the same way as the 5 October Azure Speech check (10). The v1 API is GA and the GPT-6 models carry no preview label (10).); StepFun API 28 (No status page read. status.stepfun.ai refused our reader by robots.txt and the shell couldn't connect, so we couldn't establish whether it is a status page or read any history. Scored absent for both lines, with 5 for unreadable history, and named in the open questions (0 + 5). Rate limits published with numbers per tier, from 5 concurrent, 100 RPM and 500,000 TPM to 130, 2,600 and 13,000,000 (15). The error and exception guides say to retry 429, 500, 503 and 504 after a short delay, with no Retry-After header, backoff schedule or idempotency guidance (8 of 15). No SLA found in the terms or pricing (0). Step 5 Preview is labelled a preview (0).)
- Maintenance & community, Azure OpenAI in Foundry Models +36: Azure OpenAI in Foundry Models 86 (Model reading. GPT-6.1 Terra released on Azure on 26 October 2026 and a `gpt-chat-latest` preview of 7 October was added, after GPT-6.1 Sol on 29 September (30). GA models get a retirement date 18 months after launch, set at release and readable through the Models API, with at least 60 days' email and Service Health notice, and previews at least 30 days, so a GA retirement is known more than six months ahead (12 of 12). Many shutdown dates in the 90 days to 6 November, most of them previews or partner models, among them DeepSeek-R1 (13 August), MAI-Image-2 and 2e (15 August), model-router previews (30 August), MAI-Transcribe-1 (15 September), MAI-Image-2.5 previews (1 October), the 2025-03-20 audio models and sora-2 (15 October), a Cohere Command A Plus preview (16 October) and gpt-image-1 (23 October), each in the schedule with a replacement where one exists (4 of 8). The Foundry what's new page, still on August when read on 6 November, plus Microsoft Q&A and paid support; no Azure OpenAI what's new was found (10 of 15). The SDKs are OpenAI's repositories, replies not sampled (5 of 10). Current official SDKs, `openai` 3.46.0 on PyPI (5 November) and 7.53.0 on npm, plus Microsoft's `@azure/openai` 2.0.0 companion (15). Supported runtimes stated, Python 3.9 or later and Node.js 20 or later, though `openai` 3.46.0 requires Python 3.10 (10).); StepFun API 50 (Model reading. The image models `step-2x-large` and `step-image-edit-2` were retired on 10 October 2026, and a Step 5 Preview price change is announced for 14 October (30). No stated notice period. The 10 October image retirement had a dated notice page and the July retirements a migration table, but we couldn't date when either notice went up (4 of 12). One retirement date in the last 90 days, 10 October, with nine models retired on 8 July just outside that window (6 of 8). Dated announcements, a Discord server and platform@stepfun.com for support. We didn't test whether either answers (10 of 15). No official SDK (0 of 15, 0 of 10).)
- Schema & documentation, Azure OpenAI in Foundry Models +34: 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).); StepFun API 53 (No OpenAPI or similar machine-readable contract found. The API reference is Markdown pages (0). llms.txt at platform.stepfun.ai/docs/llms.txt, and every page has a Markdown copy (10). The Chat Completions reference describes each parameter with its default, and the model page lists what Step 5 Preview supports, but little on when not to use an option (12 of 20). Tool definitions take JSON Schema parameters, structured output takes a JSON Schema with `strict: true`, and `reasoning_effort` is an enum of low, medium and high. No `tool_choice` parameter is documented (11 of 15). Worked requests and responses on each page, and an error table of eight codes with causes and fixes, but no error bodies (12 of 15). No API changelog. A model lifecycle page with dated retirements and announcement pages (8 of 15).)
- Agent ergonomics, Azure OpenAI in Foundry Models +30: 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.); StepFun API 68 (Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Tool calls through Chat Completions, Responses and Messages, with no documented way to force or forbid a call (15 of 20). Strict JSON Schema output on Step 5 Preview (13 of 15). Prompt caching with a published cache-hit price at a tenth of the miss price (15). 1M-token context and 64k output (15). No batch endpoint found (0). No official SDK. The docs use the OpenAI and Anthropic clients against compatible endpoints (0). Eight error codes with a fix each, plus `finish_reason` handling for length, content filter and tool calls (10 of 15).)
- Transparency & trust, Azure OpenAI in Foundry Models +26: Azure OpenAI in Foundry Models 83 (Closed service under the Microsoft Product Terms, with the v1 spec under MIT and the OpenAI SDKs under Apache-2.0 (15). The data privacy page agrees with the product terms on no training and states where data is processed and stored by deployment type, but gives no retention period for the human-review store and sits beside a 30-day default for Responses data (24 of 30). A published lifecycle policy and a retirement schedule with dates and replacements, but on 6 November the schedule listed `gpt-realtime-mini` 2025-10-06 and 2025-12-15 twice each with different retirement dates, and no GPT-6 model yet (18 of 20, down from 20). Data locations stated for Standard, Data Zone and Global deployments, and a public sub-processor list per the 5 October Azure Speech check, not re-read (20).); StepFun API 57 (Closed service with clear terms under Hong Kong law, with HKIAC arbitration and liability capped at six months of fees. Some earlier Step models have open weights, which doesn't change the hosted service (15). The privacy policy, terms and DPA agree that data may be used for training under program terms, but the terms' licence to Content is broad and perpetual, no retention period is given for prompts and outputs, and no subprocessor list was found (12 of 30). A model lifecycle page with dated retirements and replacements (14 of 20). Servers are disclosed as in the United States. The DPA gives general authorisation for subprocessors without a published list (10 of 20).)

| Task | Azure OpenAI in Foundry Models | StepFun API |
| --- | --- | --- |
| Research a product and write a sourced report | $110 | $1.38 |
| Build a small four-page website | $25.07 | $0.44 |
| Find and fix a bug in a large codebase | $5.41 | $0.11 |