# Azure OpenAI in Foundry Models vs StepFun API

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

- Canonical: https://www.anchorterminal.com/compare/azure-openai-vs-stepfun-api
- Markdown: https://www.anchorterminal.com/compare/azure-openai-vs-stepfun-api.md (~7,300 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

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: 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
- StepFun API: grade E, 44.3/100, rank #1206 of 1486. Markdown https://www.anchorterminal.com/tools/stepfun-api.md · JSON https://www.anchorterminal.com/api/v1/tools/stepfun-api.json
- Best model APIs and inference for AI agents: https://www.anchorterminal.com/best/inference/index.md
- All 830 models comparisons: https://www.anchorterminal.com/compare/inference/index.md

## Which one, for what

### Azure OpenAI in Foundry Models (A)

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 in its favour:
- Agent-ready, a grade of BB or better

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

### StepFun API (E)

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.

Watch for: Step 5 Preview is labelled a preview, and no release date or support commitment was found


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

## Score by category

| Category | Weight | Azure OpenAI in Foundry Models | StepFun API | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 80 | 28 | Azure OpenAI in Foundry Models +52 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 87 | 53 | Azure OpenAI in Foundry Models +34 |
| Agent ergonomics | 13% (16.2 this run) | 98 | 68 | Azure OpenAI in Foundry Models +30 |
| Security & auth | 14% (17.5 this run) | 95 | 41 | Azure OpenAI in Foundry Models +54 |
| Payments & pricing | 10% (12.5 this run) | 20 | 20 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 86 | 50 | Azure OpenAI in Foundry Models +36 |
| Transparency & trust | 7% (8.8 this run) | 83 | 57 | Azure OpenAI in Foundry Models +26 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **80 · A** | **44.3 · E** | |

## Facts side by side

| Fact | Azure OpenAI in Foundry Models | StepFun API |
| --- | --- | --- |
| Kind | Model API | Model API |
| Vendor | Microsoft | StepFun |
| Hosted endpoint | `https://<resource>.openai.azure.com/openai/v1` | `https://api.stepfun.ai/v1` |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| 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). |
| Read-only variant documented | no | no |
| 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) |

## What the same task costs

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

## How the scores have moved

### Azure OpenAI in Foundry Models

No score change since it was listed.

### StepFun API

- -0.1 on 28 October 2026: correction
- +0.3 on 27 October 2026: checklist

## Verdicts

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

**StepFun API.** StepFun's API serves Step 5 Preview with a 1M-token context, video input, strict JSON Schema output and published per-token prices, documented in Markdown with an llms.txt. The model is a preview with no release date found, there's no free allowance or SLA, and the terms and privacy policy leave room to train on customer data.

## Before you call either

### Azure OpenAI in Foundry Models

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

### StepFun API

1. Set `max_tokens` yourself. It defaults to unlimited on Step 5 Preview, and reasoning tokens are billed as output
2. Use `response_format` with `type: json_schema` and `strict: true` when the shape matters. JSON Mode alone isn't schema-checked
3. Back off and retry on 429, 500, 503 and 504. The docs give no Retry-After header or backoff schedule
4. Expect HTTP 451 or `finish_reason: content_filter` when content fails StepFun's review, and don't retry the same input
5. Use api.stepfun.ai for the international platform. api.stepfun.com is the China platform with yuan pricing

## Questions

### Which is better for AI agents, Azure OpenAI in Foundry Models or StepFun API?

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.

### Do Azure OpenAI in Foundry Models and StepFun API need an API key?

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

### Can an agent call Azure OpenAI in Foundry Models and StepFun API without installing anything?

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


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/azure-openai-vs-stepfun-api.json, and with the fewest tokens: https://www.anchorterminal.com/compare/azure-openai-vs-stepfun-api.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "azure-openai", "b": "stepfun-api"}`. From a terminal: `anchor compare azure-openai stepfun-api`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/azure-openai.json and https://www.anchorterminal.com/api/v1/tools/stepfun-api.json

## Other comparisons with Azure OpenAI in Foundry Models or StepFun API

- [Amazon Bedrock vs Azure OpenAI in Foundry Models](https://www.anchorterminal.com/compare/amazon-bedrock-vs-azure-openai.md)
- [Amazon Bedrock vs StepFun API](https://www.anchorterminal.com/compare/amazon-bedrock-vs-stepfun-api.md)
- [Claude API vs Azure OpenAI in Foundry Models](https://www.anchorterminal.com/compare/anthropic-api-vs-azure-openai.md)
- [Claude API vs StepFun API](https://www.anchorterminal.com/compare/anthropic-api-vs-stepfun-api.md)
- [Antseed vs Azure OpenAI in Foundry Models](https://www.anchorterminal.com/compare/antseed-vs-azure-openai.md)
- [Antseed vs StepFun API](https://www.anchorterminal.com/compare/antseed-vs-stepfun-api.md)
- [Azure OpenAI in Foundry Models vs BlockRun.AI](https://www.anchorterminal.com/compare/azure-openai-vs-blockrun-ai.md)
- [Azure OpenAI in Foundry Models vs Cerebras Inference](https://www.anchorterminal.com/compare/azure-openai-vs-cerebras-inference.md)
- [Azure OpenAI in Foundry Models vs Cloudflare AI Gateway](https://www.anchorterminal.com/compare/azure-openai-vs-cloudflare-ai-gateway.md)
- [Azure OpenAI in Foundry Models vs Cloudflare Workers AI](https://www.anchorterminal.com/compare/azure-openai-vs-cloudflare-workers-ai.md)
- [Azure OpenAI in Foundry Models vs Cohere Chat API (Command models)](https://www.anchorterminal.com/compare/azure-openai-vs-cohere-chat.md)
- [Azure OpenAI in Foundry Models vs DeepInfra](https://www.anchorterminal.com/compare/azure-openai-vs-deepinfra.md)
- [Azure OpenAI in Foundry Models vs DeepSeek API](https://www.anchorterminal.com/compare/azure-openai-vs-deepseek-api.md)
- [Azure OpenAI in Foundry Models vs Eden AI](https://www.anchorterminal.com/compare/azure-openai-vs-eden-ai.md)
- [Azure OpenAI in Foundry Models vs Glimpse](https://www.anchorterminal.com/compare/azure-openai-vs-elorian-glimpse.md)
- [Azure OpenAI in Foundry Models vs Fireworks AI Inference](https://www.anchorterminal.com/compare/azure-openai-vs-fireworks-inference.md)
- [Azure OpenAI in Foundry Models vs Gemini Developer API](https://www.anchorterminal.com/compare/azure-openai-vs-gemini-api.md)
- [Azure OpenAI in Foundry Models vs GroqCloud](https://www.anchorterminal.com/compare/azure-openai-vs-groq.md)
- [Azure OpenAI in Foundry Models vs Hugging Face Inference Providers](https://www.anchorterminal.com/compare/azure-openai-vs-hugging-face-inference-providers.md)
- [Azure OpenAI in Foundry Models vs Inkling 2 Small](https://www.anchorterminal.com/compare/azure-openai-vs-inkling-2-small.md)
- [Azure OpenAI in Foundry Models vs Jais 3](https://www.anchorterminal.com/compare/azure-openai-vs-jais-3.md)
- [Azure OpenAI in Foundry Models vs Meta Model API](https://www.anchorterminal.com/compare/azure-openai-vs-meta-model-api.md)
- [Azure OpenAI in Foundry Models vs MiniMax API](https://www.anchorterminal.com/compare/azure-openai-vs-minimax-api.md)
- [Azure OpenAI in Foundry Models vs Mistral AI API](https://www.anchorterminal.com/compare/azure-openai-vs-mistral-api.md)
- [Azure OpenAI in Foundry Models vs Muse Spark Open](https://www.anchorterminal.com/compare/azure-openai-vs-muse-spark-open.md)
- [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)
- [Azure OpenAI in Foundry Models vs Novita AI](https://www.anchorterminal.com/compare/azure-openai-vs-novita-ai.md)
- [Azure OpenAI in Foundry Models vs OpenAI API](https://www.anchorterminal.com/compare/azure-openai-vs-openai-api.md)
- [Azure OpenAI in Foundry Models vs OpenRouter](https://www.anchorterminal.com/compare/azure-openai-vs-openrouter.md)
- [Azure OpenAI in Foundry Models vs Prism Inference](https://www.anchorterminal.com/compare/azure-openai-vs-prism-inference.md)
- [Azure OpenAI in Foundry Models vs Router.com (Ramp Router)](https://www.anchorterminal.com/compare/azure-openai-vs-ramp-router.md)
- [Azure OpenAI in Foundry Models vs Beam 1.0](https://www.anchorterminal.com/compare/azure-openai-vs-reflection-beam.md)
- [Azure OpenAI in Foundry Models vs RouterPlus](https://www.anchorterminal.com/compare/azure-openai-vs-routerplus.md)
- [Azure OpenAI in Foundry Models vs SambaCloud](https://www.anchorterminal.com/compare/azure-openai-vs-sambanova.md)
- [Azure OpenAI in Foundry Models vs SiliconFlow](https://www.anchorterminal.com/compare/azure-openai-vs-siliconflow.md)
- [Azure OpenAI in Foundry Models vs Simplismart](https://www.anchorterminal.com/compare/azure-openai-vs-simplismart.md)
- [Azure OpenAI in Foundry Models vs SWE-2 Flash](https://www.anchorterminal.com/compare/azure-openai-vs-swe-2-flash.md)
- [Azure OpenAI in Foundry Models vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/azure-openai-vs-tencent-tokenhub.md)
- [Azure OpenAI in Foundry Models vs Together AI Inference](https://www.anchorterminal.com/compare/azure-openai-vs-together-inference.md)
- [Azure OpenAI in Foundry Models vs Vercel AI Gateway](https://www.anchorterminal.com/compare/azure-openai-vs-vercel-ai-gateway.md)
- [Azure OpenAI in Foundry Models vs Vertex AI (Gemini Enterprise Agent Platform)](https://www.anchorterminal.com/compare/azure-openai-vs-vertex-ai.md)
- [Azure OpenAI in Foundry Models vs xAI API (Grok)](https://www.anchorterminal.com/compare/azure-openai-vs-xai-api.md)
- [BlockRun.AI vs StepFun API](https://www.anchorterminal.com/compare/blockrun-ai-vs-stepfun-api.md)
- [Cerebras Inference vs StepFun API](https://www.anchorterminal.com/compare/cerebras-inference-vs-stepfun-api.md)
- [Cloudflare AI Gateway vs StepFun API](https://www.anchorterminal.com/compare/cloudflare-ai-gateway-vs-stepfun-api.md)
- [Cloudflare Workers AI vs StepFun API](https://www.anchorterminal.com/compare/cloudflare-workers-ai-vs-stepfun-api.md)
- [Cohere Chat API (Command models) vs StepFun API](https://www.anchorterminal.com/compare/cohere-chat-vs-stepfun-api.md)
- [DeepInfra vs StepFun API](https://www.anchorterminal.com/compare/deepinfra-vs-stepfun-api.md)
- [DeepSeek API vs StepFun API](https://www.anchorterminal.com/compare/deepseek-api-vs-stepfun-api.md)
- [Eden AI vs StepFun API](https://www.anchorterminal.com/compare/eden-ai-vs-stepfun-api.md)
- [Glimpse vs StepFun API](https://www.anchorterminal.com/compare/elorian-glimpse-vs-stepfun-api.md)
- [Fireworks AI Inference vs StepFun API](https://www.anchorterminal.com/compare/fireworks-inference-vs-stepfun-api.md)
- [Gemini Developer API vs StepFun API](https://www.anchorterminal.com/compare/gemini-api-vs-stepfun-api.md)
- [GroqCloud vs StepFun API](https://www.anchorterminal.com/compare/groq-vs-stepfun-api.md)
- [Hugging Face Inference Providers vs StepFun API](https://www.anchorterminal.com/compare/hugging-face-inference-providers-vs-stepfun-api.md)
- [Inkling 2 Small vs StepFun API](https://www.anchorterminal.com/compare/inkling-2-small-vs-stepfun-api.md)
- [Jais 3 vs StepFun API](https://www.anchorterminal.com/compare/jais-3-vs-stepfun-api.md)
- [Meta Model API vs StepFun API](https://www.anchorterminal.com/compare/meta-model-api-vs-stepfun-api.md)
- [MiniMax API vs StepFun API](https://www.anchorterminal.com/compare/minimax-api-vs-stepfun-api.md)
- [Mistral AI API vs StepFun API](https://www.anchorterminal.com/compare/mistral-api-vs-stepfun-api.md)
- [Muse Spark Open vs StepFun API](https://www.anchorterminal.com/compare/muse-spark-open-vs-stepfun-api.md)
- [Nemotron 3.5 Super VL vs StepFun API](https://www.anchorterminal.com/compare/nemotron-3-5-super-vl-vs-stepfun-api.md)
- [Novita AI vs StepFun API](https://www.anchorterminal.com/compare/novita-ai-vs-stepfun-api.md)
- [OpenAI API vs StepFun API](https://www.anchorterminal.com/compare/openai-api-vs-stepfun-api.md)
- [OpenRouter vs StepFun API](https://www.anchorterminal.com/compare/openrouter-vs-stepfun-api.md)
- [Prism Inference vs StepFun API](https://www.anchorterminal.com/compare/prism-inference-vs-stepfun-api.md)
- [Router.com (Ramp Router) vs StepFun API](https://www.anchorterminal.com/compare/ramp-router-vs-stepfun-api.md)
- [Beam 1.0 vs StepFun API](https://www.anchorterminal.com/compare/reflection-beam-vs-stepfun-api.md)
- [RouterPlus vs StepFun API](https://www.anchorterminal.com/compare/routerplus-vs-stepfun-api.md)
- [SambaCloud vs StepFun API](https://www.anchorterminal.com/compare/sambanova-vs-stepfun-api.md)
- [SiliconFlow vs StepFun API](https://www.anchorterminal.com/compare/siliconflow-vs-stepfun-api.md)
- [Simplismart vs StepFun API](https://www.anchorterminal.com/compare/simplismart-vs-stepfun-api.md)
- [StepFun API vs SWE-2 Flash](https://www.anchorterminal.com/compare/stepfun-api-vs-swe-2-flash.md)
- [StepFun API vs Tencent Cloud TokenHub](https://www.anchorterminal.com/compare/stepfun-api-vs-tencent-tokenhub.md)
- [StepFun API vs Together AI Inference](https://www.anchorterminal.com/compare/stepfun-api-vs-together-inference.md)
- [StepFun API vs Vercel AI Gateway](https://www.anchorterminal.com/compare/stepfun-api-vs-vercel-ai-gateway.md)
- [StepFun API vs Vertex AI (Gemini Enterprise Agent Platform)](https://www.anchorterminal.com/compare/stepfun-api-vs-vertex-ai.md)
- [StepFun API vs xAI API (Grok)](https://www.anchorterminal.com/compare/stepfun-api-vs-xai-api.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp