DeepInfra vs Morph
DeepInfra
Deep Infra, Inc.
DeepInfra wins · 16–9 (19 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to MorphDeepInfranone0/10Direct probes show llms.txt, docs.md, and openapi.json all return 404 on deepinfra.com, and no evidence pack item claims an agent-oriented docs format exists; the only machine-readable endpoint found is the models list, not documentation.
Morph confirms llms.txt is live and documented (HTTP 200) with a full documentation index, and also exposes .md versions of docs pages explicitly for agent consumption, directly matching the story's ask. Missing for 10: no independent/community confirmation of agents actually consuming llms.txt in practice.
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.morphllm.com/llms.txt # Morph API Documentation > https://docs.morphllm.com > Base URL: https://api…”
- [probe] “PROBE docs-md: HTTP 200 at https://docs.morphllm.com/introduction.md > ## Documentation Index > Fetch the complete documentation index at: h…”
- [claimed-docs] “Point any OpenAI SDK at `https://api.morphllm.com/v1`. One API key covers the open-weight chat models and the specialized tools”
ai-native userRun the product headlessly / in CI for automation
weight 2 · round to DeepInfraDeepInfra is a REST/OpenAI-compatible API (base_url + api_key model, keyless model enumeration) that is inherently scriptable and stateless, making it straightforward to call from CI/automation pipelines without any UI dependency. missing for 10: no explicit CI/CD examples (GitHub Actions, cron jobs), no official CLI, and no independent hands-on report of someone running it headlessly in a pipeline.
- [claimed-docs] “The only changes you need to make from your existing OpenAI code: 1. Set `base_url` to `https://api.deepinfra.com/v1/openai` 2. Set `api_…”
- [claimed-docs] “The only changes you need to make from your existing OpenAI code: Set base_url to https://api.deepinfra.com/v1/openai”
- [probe] “PROBE models-endpoint (2026-09-04): GET https://api.deepinfra.com/v1/openai/models with NO API key returned HTTP 200 with a machine-readable…”
- [claimed-docs] “You only pay per token — no idle GPU time, no minimums, no seat fees.”
Morph is delivered as an OpenAI/Anthropic-compatible HTTP API (morph-docs-1, morph-docs-16) plus a batch mode explicitly designed for running 'thousands of chat completions offline' (morph-docs-13), both of which are naturally scriptable/headless and usable from CI pipelines. However, there is no explicit CI/CD documentation, GitHub Actions example, or automation-pipeline guide in the evidence pack. Missing for 10: explicit CI/automation guide or example, dedicated headless-mode docs beyond generic API access, independent confirmation of CI usage.
- [claimed-docs] “Point any OpenAI SDK at `https://api.morphllm.com/v1`. One API key covers the open-weight chat models and the specialized tools”
- [claimed-docs] “Run thousands of chat completions offline at half price.”
- [claimed-docs] “Anthropic Messages supports the same open source chat models, token billing, and rate limits.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.morphllm.com/llms.txt # Morph API Documentation > https://docs.morphllm.com > Base URL: https://api…”
ai-native userConnect an agent via an official MCP server
weight 3 · round to MorphDeepInfranone0/10DeepInfra is an inference API/platform (not an agent), so an official MCP server is a fair axis to expect, but no evidence in the pack mentions MCP support at all—only OpenAI-compatible REST API docs.
Morph publishes an official MCP server (guides/mcp.md, quickstart 'Install the Morph MCP so Claude Code can read it') that lets external agents like Claude Code connect to its fast file-editing/search tools, confirmed live via probe [morph-probe-4]. missing for 10: independent/hands-on confirmation that the MCP server works as documented (community evidence only covers the apply model, not MCP connectivity), and no detail on MCP tool list/config beyond the guide.
- [claimed-docs] “Connect your favorite AI tools to Morph's blazing-fast file editing via Model Context Protocol.”
- [claimed-docs] “Install the Morph MCP so Claude Code can read it”
- [claimed-docs] “Use Morph's Warp-Grep for fast, local code search alongside your MCP setup.”
- [probe] “official MCP server documented at https://docs.morphllm.com/guides/mcp”
ai-native userUse an official CLI
weight 2 · round drawnDeepInfranone0/10No evidence of an official DeepInfra CLI tool; docs focus on REST/OpenAI-SDK compatibility, and probes for docs/openapi/llms.txt turned up nothing about a CLI. DeepInfra is an inference API/cloud platform, so an official CLI is a plausible and fair capability to ask about, but none is evidenced.
- [claimed-docs] “Point your existing OpenAI SDK to `https://api.deepinfra.com/v1/openai` and your code works without changes. No migration required.”
- [probe] “PROBE llms.txt: HTTP 404 at https://deepinfra.com/llms.txt”
- [probe] “PROBE docs-md: HTTP 404 at https://deepinfra.com/docs.md”
- [probe] “PROBE openapi: all candidate paths 404 (https://deepinfra.com/openapi.json, https://deepinfra.com/swagger.json, https://deepinfra.com/api/op…”
Morphnone0/10Morph is API/SDK-focused (OpenAI-compatible endpoints, MCP integration, Fast Apply, etc.) but no evidence pack item mentions an official Morph CLI tool; community only references third-party CLIs (llm.datasette.io) connecting to Morph's API, not a first-party CLI shipped by Morph.
ai-native userDrive the product through a documented public API
weight 3 · round drawnDeepInfra publishes extensive documentation for a fully OpenAI-compatible REST API (chat completions, embeddings, vision, image/video, speech, service tiers, reasoning_effort, fail_fast, etc.), confirmed live via a keyless probe that enumerated 189 models through the documented endpoint. Missing for 10: no discoverable OpenAPI/swagger spec or llms.txt for machine-readable agent consumption (all returned 404), so an AI agent must rely on human-oriented docs rather than a formal machine spec.
- [claimed-docs] “Point your existing OpenAI SDK to `https://api.deepinfra.com/v1/openai` and your code works without changes. No migration required.”
- [claimed-docs] “OpenAI-compatible chat completions API — just change the base URL and model name.”
- [claimed-docs] “The only changes you need to make from your existing OpenAI code: 1. Set `base_url` to `https://api.deepinfra.com/v1/openai` 2. Set `api_…”
- [claimed-docs] “The only changes you need to make from your existing OpenAI code: Set base_url to https://api.deepinfra.com/v1/openai”
- [claimed-docs] “Set service_tier to "priority" to request priority inference on supported models. Priority requests get faster time-to-first-token and highe…”
- [claimed-docs] “Set service_tier to "flex" to run Chat Completions requests at a lower cost in exchange for slower response times and occasional resource un…”
- [claimed-docs] “Set the optional fail_fast parameter to true to get an immediate HTTP 429 instead of waiting.”
- [probe] “PROBE models-endpoint (2026-09-04): GET https://api.deepinfra.com/v1/openai/models with NO API key returned HTTP 200 with a machine-readable…”
- [probe] “PROBE llms.txt: HTTP 404 at https://deepinfra.com/llms.txt”
- [probe] “PROBE openapi: all candidate paths 404 (https://deepinfra.com/openapi.json, https://deepinfra.com/swagger.json, https://deepinfra.com/api/op…”
Morph documents a public OpenAI-compatible API at api.morphllm.com/v1 plus a native Anthropic Messages endpoint, with SDK docs covering chat, Fast Apply, Compact, Batch, caching, and dedicated endpoints, and this is corroborated by third-party usage (HN commenters, github demos) actually driving it programmatically. Missing for 10: no discoverable OpenAPI/swagger spec (404s on all probed paths) and mixed community reports on output reliability reduce polish.
- [claimed-docs] “Point any OpenAI SDK at `https://api.morphllm.com/v1`. One API key covers the open-weight chat models and the specialized tools”
- [claimed-docs] “Fast Apply merges just the changed lines at 10,500 tok/s, 98% accuracy.”
- [claimed-docs] “Drop filler from chat history and code context at 33,000 tok/s. 50-70% reduction, every surviving line byte-for-byte identical to input.”
- [claimed-docs] “Run thousands of chat completions offline at half price.”
- [claimed-docs] “Anthropic Messages supports the same open source chat models, token billing, and rate limits.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.morphllm.com/llms.txt # Morph API Documentation > https://docs.morphllm.com > Base URL: https://api…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.morphllm.com/openapi.json, https://docs.morphllm.com/swagger.json, https://docs.morphll…”
- [github] “Use Morph's API to intelligently modify existing code at 4,500+ tokens/sec”
- [community] “Have been using morph for a while (I am one of the authors of goose) and was surprised when introduced at the boost it gave me (much less it…”
- [community] “This uses an OpenAI-compatible endpoint, so got this working with my llm.datasette.io CLI tool... One thing that worries me: since it's usin…”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · round drawnDeepInfranone0/10No evidence of scoped or least-privilege API key/credential management (e.g., per-agent tokens, permission scoping, role-based keys) — only a single generic API token model is implied via base_url/api_key usage. Missing for 10: any docs on creating multiple scoped keys, permission/role restrictions, credential expiration, or per-agent token issuance.
- [claimed-docs] “The only changes you need to make from your existing OpenAI code: 1. Set `base_url` to `https://api.deepinfra.com/v1/openai` 2. Set `api_…”
- [claimed-docs] “Drop-in OpenAI replacement. Point your existing OpenAI SDK to https://api.deepinfra.com/v1/openai and your code works without changes.”
Morphnone0/10Evidence shows only a single API key covering all models/tools with no mention of scoped, least-privilege, or role-based credential issuance for agents; no docs on permission scoping, sub-keys, or credential restriction. missing for 10: scoped/limited-permission API key creation, per-agent credential issuance, role-based access control docs.
- [claimed-docs] “Point any OpenAI SDK at `https://api.morphllm.com/v1`. One API key covers the open-weight chat models and the specialized tools”
ai-native userBuild against official SDKs
weight 2 · round to DeepInfraDeepInfra explicitly documents OpenAI SDK compatibility as a drop-in replacement (just change base_url, api_key, model) with no code migration required, and a live probe confirms the OpenAI-compatible endpoint is functional and enumerable. This directly satisfies building against an official/well-known SDK ecosystem rather than a bespoke library. missing for 10: no dedicated first-party DeepInfra-branded SDK packages mentioned (relies on OpenAI SDK compatibility), and no independent third-party developer corroboration beyond docs and endpoint probes.
- [claimed-docs] “Point your existing OpenAI SDK to `https://api.deepinfra.com/v1/openai` and your code works without changes. No migration required.”
- [claimed-docs] “Point your existing OpenAI SDK to https://api.deepinfra.com/v1/openai and your code works without changes. No migration required.”
- [claimed-docs] “The only changes you need to make from your existing OpenAI code: 1. Set `base_url` to `https://api.deepinfra.com/v1/openai` 2. Set `api_…”
- [claimed-docs] “The only changes you need to make from your existing OpenAI code: Set base_url to https://api.deepinfra.com/v1/openai”
- [claimed-docs] “Drop-in OpenAI replacement. Point your existing OpenAI SDK to https://api.deepinfra.com/v1/openai and your code works without changes.”
- [probe] “PROBE models-endpoint (2026-09-04): GET https://api.deepinfra.com/v1/openai/models with NO API key returned HTTP 200 with a machine-readable…”
Morph documents OpenAI-SDK and Anthropic Messages-API compatibility (point any OpenAI SDK at api.morphllm.com, native /v1/messages support), and community evidence confirms real developers wiring it up via OpenAI-compatible clients (e.g. llm.datasette.io CLI). However there's no evidence of a first-party Morph-branded SDK package, and an OpenAPI spec probe returned 404s across all candidate paths, suggesting no formal machine-readable API spec is published. missing for 10: dedicated first-party Morph SDK package, discoverable OpenAPI/swagger spec, broader language-SDK coverage beyond OpenAI/Anthropic compatibility.
- [claimed-docs] “Point any OpenAI SDK at `https://api.morphllm.com/v1`. One API key covers the open-weight chat models and the specialized tools”
- [claimed-docs] “Claude Code speaks the Anthropic Messages API, which Morph serves natively at `/v1/messages`.”
- [claimed-docs] “Anthropic Messages supports the same open source chat models, token billing, and rate limits.”
- [community] “This uses an OpenAI-compatible endpoint, so got this working with my llm.datasette.io CLI tool... One thing that worries me: since it's usin…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.morphllm.com/openapi.json, https://docs.morphllm.com/swagger.json, https://docs.morphll…”
ai-native userSubscribe to events via webhooks
weight 2 · round drawnDeepInfranone0/10No evidence of any webhook subscription or event-notification mechanism anywhere in the docs; DeepInfra is a request/response inference API with no mention of async event callbacks.
Agentic features
ai-native userSet up automations that run autonomously in the background
weight 2 · round drawnDeepInfranone0/10The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)
Morphnone0/10Morph is presented as an LLM inference/API platform (fast apply, compact, batch completions, canary/reflex model switching) rather than a background automation or agent-orchestration product; nothing in the evidence describes setting up autonomous, self-running background automations or scheduled agentic tasks. The closest features (batch processing, canary traffic routing) are developer-triggered infra operations, not autonomous background automations.
- [claimed-docs] “Run thousands of chat completions offline at half price.”
- [claimed-docs] “Move a production agent off Anthropic or OpenAI onto Kimi K3 — a 5% traffic trial or a full migration, gated by Reflexes.”
- [claimed-docs] “A canary keeps your current provider, sends a slice of production traffic to Kimi K3, and compares Reflex results before you switch.”
Api quality
ai-native userExplore an interactive API reference with runnable examples
weight 2 · round drawnDeepInfranone0/10The docs pack shows static code snippets (e.g., OpenAI SDK base_url examples) but no evidence of an interactive, runnable API console or playground; probes for openapi.json/swagger.json all returned 404, and no llms.txt/docs.md machine-readable spec exists, indicating no interactive reference is exposed.
- [probe] “PROBE llms.txt: HTTP 404 at https://deepinfra.com/llms.txt”
- [probe] “PROBE docs-md: HTTP 404 at https://deepinfra.com/docs.md”
- [probe] “PROBE openapi: all candidate paths 404 (https://deepinfra.com/openapi.json, https://deepinfra.com/swagger.json, https://deepinfra.com/api/op…”
- [claimed-docs] “The only changes you need to make from your existing OpenAI code: 1. Set `base_url` to `https://api.deepinfra.com/v1/openai` 2. Set `api_…”
Morphnone0/10The evidence shows standard markdown docs (llms.txt, introduction.md) but no interactive API reference or runnable-example explorer — probes for an OpenAPI/Swagger spec returned 404 on every candidate path, and no docs mention a live API console. A community mention of a separate 'playground' relates to testing the apply model, not an API reference tool, and doesn't establish this capability.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.morphllm.com/openapi.json, https://docs.morphllm.com/swagger.json, https://docs.morphll…”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.morphllm.com/llms.txt # Morph API Documentation > https://docs.morphllm.com > Base URL: https://api…”
- [probe] “PROBE docs-md: HTTP 200 at https://docs.morphllm.com/introduction.md > ## Documentation Index > Fetch the complete documentation index at: h…”
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round drawnDeepInfranone0/10Direct probes for llms.txt, docs.md, and common OpenAPI/swagger spec paths all returned 404, indicating no machine-readable API spec is published; the docs only describe OpenAI SDK compatibility, not a downloadable OpenAPI/JSON schema.
Morphnone0/10Morph is API-based (OpenAI-compatible endpoint), so an OpenAPI spec is a fair expectation, but a direct probe found all candidate OpenAPI/swagger spec paths returned 404, and no evidence pack item shows a downloadable machine-readable spec.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.morphllm.com/openapi.json, https://docs.morphllm.com/swagger.json, https://docs.morphll…”
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · round drawnDeepInfranone0/10The evidence pack shows OpenAI-compatible endpoints and a model catalog but contains no documentation of API versioning scheme, changelog, or deprecation/sunset policy for models or endpoints; probes even show missing openapi/spec files (404s), reinforcing the absence of such formal API-lifecycle documentation.
- [probe] “PROBE docs-md: HTTP 404 at https://deepinfra.com/docs.md”
- [probe] “PROBE openapi: all candidate paths 404 (https://deepinfra.com/openapi.json, https://deepinfra.com/swagger.json, https://deepinfra.com/api/op…”
- [claimed-docs] “The only changes you need to make from your existing OpenAI code: 1. Set `base_url` to `https://api.deepinfra.com/v1/openai` 2. Set `api_…”
Morphnone0/10No evidence of API versioning scheme (e.g., v1/v2) or a documented deprecation policy anywhere in the docs; the /v1 path is just the base URL, not a versioning/deprecation commitment. OpenAPI spec probes also 404, further indicating no formal versioned API contract is published.
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.morphllm.com/openapi.json, https://docs.morphllm.com/swagger.json, https://docs.morphll…”
- [claimed-docs] “Point any OpenAI SDK at `https://api.morphllm.com/v1`. One API key covers the open-weight chat models and the specialized tools”
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
ai-native userPerform bulk operations across many items at once
weight 2 · round to MorphDeepInfranone0/10The docs mention a 'flex' pricing tier suited to asynchronous, non-production workloads like data enrichment and model evaluations, but there is no documented batch API, bulk upload endpoint, or mechanism to submit and process many items in a single call — only single-request chat/completions semantics are described.
- [claimed-docs] “It’s ideal for non-production or lower-priority tasks such as model evaluations, data enrichment, and asynchronous workloads.”
- [claimed-docs] “Set service_tier to "flex" to run Chat Completions requests at a lower cost in exchange for slower response times and occasional resource un…”
Morph offers batch offline completions (morph-docs-13) and fast bulk file-editing/apply capabilities (morph-docs-11, morph-gh-1), which support some bulk/automation-depth use cases, but there is no documented feature for bulk operations across many arbitrary items (e.g., batch file renames, mass repo-wide refactors, multi-item dataset operations) beyond chat completions and code apply. missing for 10: explicit bulk/batch operation APIs beyond chat completions, evidence of bulk operations across many discrete items (files, records, tickets) rather than just token throughput, independent verification of bulk reliability at scale.
- [claimed-docs] “Run thousands of chat completions offline at half price.”
- [claimed-docs] “Fast Apply merges just the changed lines at 10,500 tok/s, 98% accuracy.”
- [github] “Use Morph's API to intelligently modify existing code at 4,500+ tokens/sec”
Batch async — stories about batch async in this arenaBatch async
Stories about batch async in this arena
Batch
ml-engineerSubmit asynchronous batch inference jobs at a documented discount versus real-time pricing
weight 2 · round to MorphDeepInfra documents a 'flex' service_tier that gives a 20% discount versus standard pricing and is explicitly recommended for 'asynchronous workloads' and lower-priority tasks, which partially matches the story's intent of discounted async processing. However, this is a request-level QoS flag on the standard synchronous chat API, not a true batch-job system (no file upload, job submission ID, or polling/webhook completion pattern like OpenAI's Batch API). Missing for 10: a documented batch-job submission endpoint (upload/queue a set of prompts, get a job ID, poll or receive callback), explicit SLA/turnaround time for batch jobs, and independent confirmation of the discount and workflow in practice.
- [claimed-docs] “It’s ideal for non-production or lower-priority tasks such as model evaluations, data enrichment, and asynchronous workloads.”
- [claimed-docs] “Flex inference is billed at a 20% discount off the model's standard per-token price.”
- [claimed-docs] “Set service_tier to "flex" to run Chat Completions requests at a lower cost in exchange for slower response times and occasional resource un…”
Morph documents a batch component explicitly for offline, asynchronous chat completions at 'half price' (morph-docs-13), directly matching the story's async-job-with-discount claim. However, there's no detail on job submission/status API mechanics, SLA/turnaround time, or independent confirmation of the discount in practice. missing for 10: detailed batch API docs (submission, polling, output retrieval), documented turnaround SLAs, independent/community verification of discount pricing.
- [claimed-docs] “Run thousands of chat completions offline at half price.”
Dedicated capacity — stories about dedicated capacity in this arenaDedicated capacity
Stories about dedicated capacity in this arena
Dedicated
ml-engineerDeploy a model on dedicated GPU capacity with autoscaling so my traffic is isolated from the shared serverless pool
weight 2 · round to DeepInfraDeepInfra docs explicitly offer dedicated instance deployment on A100/H100/H200/B200/B300 GPUs with autoscaling and a private endpoint for data isolation, directly matching the story's request for isolated, dedicated capacity separate from the shared serverless pool. missing for 10: independent/hands-on confirmation of autoscaling behavior under load, SLA/isolation guarantees, and pricing/latency benchmarks for dedicated vs shared tiers.
- [claimed-docs] “Run your own fine-tuned LLM on A100 / H100 / H200 / B200 / B300 with autoscaling.”
- [claimed-docs] “Need to run your own fine-tuned weights, or require data isolation? Deploy a dedicated instance on A100/H100/H200/B200/B300 with autoscaling…”
- [claimed-docs] “Deploy Private Models Run your own fine-tuned LLM on A100 / H100 / H200 / B200 / B300 with autoscaling.”
Morph docs mention 'dedicated endpoints' where you reserve model capacity and plan and Morph provisions/operates it, which implies isolated capacity, but there is no mention of autoscaling, traffic isolation guarantees, or GPU-level specifics. missing for 10: explicit autoscaling behavior, confirmation of traffic isolation from shared serverless pool, GPU capacity details, independent corroboration of dedicated endpoint performance.
- [claimed-docs] “Reserve model capacity by choosing a model and plan. Morph provisions and operates it”
Fine tune serving — stories about fine tune serving in this arenaFine tune serving
Stories about fine tune serving in this arena
Fine tune
ml-engineerFine-tune a supported base model on my own data and serve the result on the same platform
weight 2 · round drawnDeepInfra documents deploying your own fine-tuned weights for serving (docs-8/9/18) and separately offers GPU clusters with SSH for training (docs-10), so the pieces to fine-tune-then-serve exist, but there is no evidence of an integrated managed fine-tuning job/dataset-upload API on a supported base model — customers must train themselves on rented GPUs and then manually deploy the resulting weights as a private endpoint. Missing for 10: a first-party fine-tuning job service (upload dataset, select base model, launch job) that outputs directly into the serving catalog, and any hands-on/community confirmation of this end-to-end flow.
- [claimed-docs] “Run your own fine-tuned LLM on A100 / H100 / H200 / B200 / B300 with autoscaling.”
- [claimed-docs] “Need to run your own fine-tuned weights, or require data isolation? Deploy a dedicated instance on A100/H100/H200/B200/B300 with autoscaling…”
- [claimed-docs] “GPU Clusters for training and full control. Rent a B200 or B300 cluster with SSH access and run whatever you want.”
- [claimed-docs] “Deploy Private Models Run your own fine-tuned LLM on A100 / H100 / H200 / B200 / B300 with autoscaling.”
Morph offers 'Reflexes' — small custom classifiers that train in ~30s on your data and are then served/gated in production (morph-docs-6, morph-docs-3, morph-docs-4) — plus dedicated endpoints to reserve capacity for a chosen model (morph-docs-15). This is a narrow, specialized form of 'train on your data and serve it' rather than fine-tuning a general-purpose base chat/completion model. Missing for 10: explicit fine-tuning API/pipeline for full base language models (not just small classifiers), documentation on custom dataset upload/training for chat models, and evidence that a fine-tuned base model (vs. a Reflex classifier) can be served alongside the standard endpoints.
- [claimed-docs] “A small Reflex trains in about 30 seconds.”
- [claimed-docs] “Move a production agent off Anthropic or OpenAI onto Kimi K3 — a 5% traffic trial or a full migration, gated by Reflexes.”
- [claimed-docs] “A canary keeps your current provider, sends a slice of production traffic to Kimi K3, and compares Reflex results before you switch.”
- [claimed-docs] “Reserve model capacity by choosing a model and plan. Morph provisions and operates it”
ml-engineerUpload and serve my own custom model weights or LoRA adapters
weight 2 · round to DeepInfraDeepInfra documents deploying custom fine-tuned LLM weights on dedicated GPU instances (A100/H100/H200/B200/B300) with autoscaling and private endpoints, directly addressing the 'serve my own custom model weights' part of the story. However, there is no explicit mention of LoRA adapter upload/serving specifically, nor details on the upload workflow, supported formats, or independent/hands-on confirmation that this works as claimed. Missing for 10: LoRA adapter support specifics, upload/serving workflow documentation, independent verification of custom weight deployment.
- [claimed-docs] “Run your own fine-tuned LLM on A100 / H100 / H200 / B200 / B300 with autoscaling.”
- [claimed-docs] “Need to run your own fine-tuned weights, or require data isolation? Deploy a dedicated instance on A100/H100/H200/B200/B300 with autoscaling…”
- [claimed-docs] “Deploy Private Models Run your own fine-tuned LLM on A100 / H100 / H200 / B200 / B300 with autoscaling.”
Morphnone0/10Morph's docs describe serving open-weight chat models, dedicated capacity reservations, and training small in-house 'Reflex' classifiers, but nothing about ml-engineers uploading their own custom model weights or LoRA adapters for serving. missing for 10: any weight/adapter upload API, LoRA fine-tuning support, or documentation of bringing custom checkpoints to Morph's serving layer.
- [claimed-docs] “A small Reflex trains in about 30 seconds.”
- [claimed-docs] “Reserve model capacity by choosing a model and plan. Morph provisions and operates it”
- [claimed-docs] “Point any OpenAI SDK at `https://api.morphllm.com/v1`. One API key covers the open-weight chat models and the specialized tools”
Model catalog — stories about model catalog in this arenaModel catalog
Stories about model catalog in this arena
Catalog
ml-engineerGet newly released open-weight models on the platform quickly after their public release
weight 2 · round drawnDeepInfranone0/10The evidence pack shows a broad model catalog (189 models) and general inference features, but nothing documents DeepInfra's speed in adding newly released open-weight models after public release — no changelog, launch-day availability claims, or timing data are present.
- [probe] “PROBE models-endpoint (2026-09-04): GET https://api.deepinfra.com/v1/openai/models with NO API key returned HTTP 200 with a machine-readable…”
Morphnone0/10The evidence shows Morph supports a curated set of open-weight chat models (e.g., Kimi K3) and offers OpenAI/Anthropic-compatible access, but there is no documentation or report about how quickly new open-weight model releases are added to the platform. A community comment even questions why only an older model was listed on OpenRouter, suggesting possible lag, but this is not a concrete contradiction of a specific claim. Missing for 10: any release-cadence documentation, changelog, or independent confirmation of rapid onboarding of newly released open-weight models.
- [claimed-docs] “Move a production agent off Anthropic or OpenAI onto Kimi K3 — a 5% traffic trial or a full migration, gated by Reflexes.”
- [claimed-docs] “Anthropic Messages supports the same open source chat models, token billing, and rate limits.”
- [community] “Last time I looked into Morph, I noticed you weren't yet on OpenRouter. I see that's changed, but it looks like only an older model is liste…”
developerRely on a documented deprecation policy with advance notice before a hosted model is removed
weight 1 · round drawnDeepInfranone0/10No evidence pack item mentions a deprecation policy, sunset notice period, or advance notice process for removing hosted models; the docs cover API usage, pricing, and infrastructure but nothing about model lifecycle/removal policy.
ai-native userHave an agent enumerate the live model catalog programmatically via a documented GET /v1/models-style endpoint
weight 2 · round to DeepInfraA live probe confirms GET https://api.deepinfra.com/v1/openai/models returns HTTP 200 with a machine-readable list of 189 models, and DeepInfra's docs establish that its API is a documented OpenAI-compatible drop-in (same base_url, same client libraries), which conventionally includes the /v1/models listing endpoint. Missing for 10: a dedicated docs page explicitly describing the /v1/models endpoint schema/parameters rather than relying on general OpenAI-compatibility claims.
- [probe] “PROBE models-endpoint (2026-09-04): GET https://api.deepinfra.com/v1/openai/models with NO API key returned HTTP 200 with a machine-readable…”
- [claimed-docs] “Point your existing OpenAI SDK to https://api.deepinfra.com/v1/openai and your code works without changes. No migration required.”
- [claimed-docs] “The only changes you need to make from your existing OpenAI code: 1. Set `base_url` to `https://api.deepinfra.com/v1/openai` 2. Set `api_…”
- [claimed-docs] “OpenAI-compatible chat completions API — just change the base URL and model name.”
Morphnone0/10Morph documents an OpenAI-compatible base URL (/v1) and multiple endpoints (/v1/messages, batch, caching, dedicated endpoints) but no evidence pack item mentions a GET /v1/models catalog endpoint, and the OpenAPI schema probe returned 404s across all candidate paths, meaning no documented machine-readable catalog listing was found.
- [claimed-docs] “Point any OpenAI SDK at `https://api.morphllm.com/v1`. One API key covers the open-weight chat models and the specialized tools”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.morphllm.com/openapi.json, https://docs.morphllm.com/swagger.json, https://docs.morphll…”
developerChoose among a broad catalog of current open-weight model families (Llama, Qwen, DeepSeek, GPT-OSS and peers) on shared serverless endpoints
weight 3 · round to DeepInfraDeepInfra's docs confirm an OpenAI-compatible shared serverless endpoint where you 'set model to a model from our catalog,' and a live probe confirms 189 models are enumerable via the API without cold-start dedicated deployment. However, the evidence pack never explicitly names or confirms coverage of Llama, Qwen, DeepSeek, or GPT-OSS specifically as catalog entries. Missing for 10: explicit documentation or listing naming these specific model families as available, and independent commentary on catalog breadth/freshness beyond the raw count.
- [claimed-docs] “The only changes you need to make from your existing OpenAI code: 1. Set `base_url` to `https://api.deepinfra.com/v1/openai` 2. Set `api_…”
- [claimed-docs] “DeepInfra is an AI inference cloud that makes it simple to run the latest machine learning models at scale — LLMs, vision, embeddings, image…”
- [probe] “PROBE models-endpoint (2026-09-04): GET https://api.deepinfra.com/v1/openai/models with NO API key returned HTTP 200 with a machine-readable…”
Morph's docs confirm an OpenAI-compatible endpoint serving 'open-weight chat models' broadly, with prefix caching enabled for 'every open source model' and specific mention of migrating between providers like Kimi K3, but no evidence explicitly lists Llama, Qwen, DeepSeek, GPT-OSS or enumerates a broad multi-family catalog. Missing for 10: an explicit model catalog/list naming specific open-weight families (Llama, Qwen, DeepSeek, GPT-OSS), and independent confirmation of catalog breadth beyond Kimi K3.
- [claimed-docs] “Point any OpenAI SDK at `https://api.morphllm.com/v1`. One API key covers the open-weight chat models and the specialized tools”
- [claimed-docs] “Move a production agent off Anthropic or OpenAI onto Kimi K3 — a 5% traffic trial or a full migration, gated by Reflexes.”
- [claimed-docs] “Prefix caching is on for every open source model. No configuration, no cache-write surcharge.”
- [claimed-docs] “Anthropic Messages supports the same open source chat models, token billing, and rate limits.”
Multimodal — stories about multimodal in this arenaMultimodal
Stories about multimodal in this arena
Modalities
developerGenerate embeddings (and rerank results) for retrieval pipelines without a second vendor
weight 1 · round to DeepInfraDeepInfra explicitly offers embeddings and reranking models via an OpenAI-compatible API alongside LLMs, letting developers build retrieval pipelines on one vendor. Missing for 10: independent hands-on validation of embedding/rerank endpoints, benchmark quality comparisons, and detailed API-parameter docs for these specific endpoints.
- [claimed-docs] “Embeddings & Reranking State-of-the-art embedding and reranker models for search and RAG.”
- [claimed-docs] “DeepInfra is an AI inference cloud that makes it simple to run the latest machine learning models at scale — LLMs, vision, embeddings, image…”
- [claimed-docs] “Point your existing OpenAI SDK to `https://api.deepinfra.com/v1/openai` and your code works without changes. No migration required.”
developerCall vision, audio, or image-generation models beyond text chat on the same platform
weight 1 · round to DeepInfraDocs explicitly list Vision & OCR, Speech (Whisper/TTS), and Image & Video generation (FLUX, Stable Diffusion, text-to-video) as first-class model categories alongside chat, all accessible via the same OpenAI-compatible API/platform. Missing for 10: independent hands-on confirmation of calling these non-text endpoints and more detail on request/response formats for each modality.
- [claimed-docs] “DeepInfra is an AI inference cloud that makes it simple to run the latest machine learning models at scale — LLMs, vision, embeddings, image…”
- [claimed-docs] “FLUX, Stable Diffusion, text-to-video, and more.”
- [claimed-docs] “Embeddings & Reranking State-of-the-art embedding and reranker models for search and RAG.”
- [claimed-docs] “Image & Video Generation FLUX, Stable Diffusion, text-to-video, and more.”
- [claimed-docs] “Speech recognition (Whisper) and text-to-speech models.”
- [claimed-docs] “Vision & OCR Multimodal models for visual understanding and document text extraction.”
Morphnone0/10All evidence describes Morph as a text/code-focused LLM API platform (chat completions, Fast Apply code editing, Reflexes classifiers, batch/caching) with no mention of vision, audio, or image-generation model endpoints. This axis applies to an LLM API platform, but no evidence supports multimodal capability.
Openai compat — stories about openai compat in this arenaOpenai compat
Stories about openai compat in this arena
Compat
ai-native userPlug the provider into coding agents and agent frameworks through documented, first-party integration guides
weight 2 · round to MorphDeepInfra documents a drop-in OpenAI-compatible endpoint (base_url swap, same SDK, model catalog) which is the mechanism most coding agents/agent frameworks rely on to add a custom provider, and a live probe confirms the OpenAI-style /models endpoint works keylessly. However, the evidence pack contains no first-party guide naming or walking through integration with any specific coding agent or agent framework (e.g., LangChain, LlamaIndex, Cursor, Continue) — only generic 'point your OpenAI SDK here' instructions. missing for 10: named integration guides for specific coding agents/agent frameworks, third-party/community confirmation of successful agent hookups.
- [claimed-docs] “Point your existing OpenAI SDK to `https://api.deepinfra.com/v1/openai` and your code works without changes. No migration required.”
- [claimed-docs] “OpenAI-compatible chat completions API — just change the base URL and model name.”
- [claimed-docs] “The only changes you need to make from your existing OpenAI code: 1. Set `base_url` to `https://api.deepinfra.com/v1/openai` 2. Set `api_…”
- [claimed-docs] “Drop-in OpenAI replacement. Point your existing OpenAI SDK to https://api.deepinfra.com/v1/openai and your code works without changes.”
- [probe] “PROBE models-endpoint (2026-09-04): GET https://api.deepinfra.com/v1/openai/models with NO API key returned HTTP 200 with a machine-readable…”
Morph provides first-party documented guides for integrating with coding agents/frameworks: OpenAI-compatible endpoint (morph-docs-1), native Anthropic Messages API for Claude Code (morph-docs-7), MCP server setup for Claude Code (morph-docs-5, morph-docs-9, morph-probe-4), and Codex integration via edit_file (morph-docs-8). Community evidence (goose author, HN discussion) corroborates real-world use in agent frameworks. Missing for 10: independent verification of MCP/agent integration reliability beyond docs and mixed community feedback on apply accuracy.
- [claimed-docs] “Point any OpenAI SDK at `https://api.morphllm.com/v1`. One API key covers the open-weight chat models and the specialized tools”
- [claimed-docs] “Install the Morph MCP so Claude Code can read it”
- [claimed-docs] “Claude Code speaks the Anthropic Messages API, which Morph serves natively at `/v1/messages`.”
- [claimed-docs] “Keep your current Codex model and give it `edit_file` backed by `morph-v3-fast` at 10,500+ tok/s”
- [claimed-docs] “Connect your favorite AI tools to Morph's blazing-fast file editing via Model Context Protocol.”
- [probe] “official MCP server documented at https://docs.morphllm.com/guides/mcp”
- [community] “Have been using morph for a while (I am one of the authors of goose) and was surprised when introduced at the boost it gave me (much less it…”
ai-native userHave an agent switch to or away from this provider mid-workflow because it speaks the standard chat-completions API without provider-specific code changes
weight 3 · round to DeepInfraDeepInfra explicitly documents a drop-in OpenAI-compatible endpoint requiring only base_url/api_key/model changes, and a live probe confirms the OpenAI-compatible models endpoint is reachable and functional, supporting agents switching providers without provider-specific code. Missing for 10: independent third-party (non-vendor) confirmation of seamless mid-workflow agent switching in practice.
- [claimed-docs] “Point your existing OpenAI SDK to `https://api.deepinfra.com/v1/openai` and your code works without changes. No migration required.”
- [claimed-docs] “Point your existing OpenAI SDK to https://api.deepinfra.com/v1/openai and your code works without changes. No migration required.”
- [claimed-docs] “The only changes you need to make from your existing OpenAI code: 1. Set `base_url` to `https://api.deepinfra.com/v1/openai` 2. Set `api_…”
- [claimed-docs] “The only changes you need to make from your existing OpenAI code: Set base_url to https://api.deepinfra.com/v1/openai”
- [claimed-docs] “Drop-in OpenAI replacement. Point your existing OpenAI SDK to https://api.deepinfra.com/v1/openai and your code works without changes.”
- [probe] “PROBE models-endpoint (2026-09-04): GET https://api.deepinfra.com/v1/openai/models with NO API key returned HTTP 200 with a machine-readable…”
Morph explicitly documents an OpenAI-compatible endpoint (and Anthropic Messages compatibility) plus first-class provider-switching workflows—canary traffic splits and full migration from OpenAI/Anthropic to another model—showing the standard API enables mid-workflow provider switches without code changes. Community evidence (morph-comm-5) independently confirms the OpenAI-compatible endpoint works with third-party tools. missing for 10: independent hands-on verification of the canary/migration switching feature itself (only vendor docs), and no evidence of switching away from Morph to another provider.
- [claimed-docs] “Point any OpenAI SDK at `https://api.morphllm.com/v1`. One API key covers the open-weight chat models and the specialized tools”
- [claimed-docs] “Move a production agent off Anthropic or OpenAI onto Kimi K3 — a 5% traffic trial or a full migration, gated by Reflexes.”
- [claimed-docs] “A canary keeps your current provider, sends a slice of production traffic to Kimi K3, and compares Reflex results before you switch.”
- [claimed-docs] “Anthropic Messages supports the same open source chat models, token billing, and rate limits.”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.morphllm.com/llms.txt # Morph API Documentation > https://docs.morphllm.com > Base URL: https://api…”
- [community] “This uses an OpenAI-compatible endpoint, so got this working with my llm.datasette.io CLI tool... One thing that worries me: since it's usin…”
developerPoint an existing OpenAI SDK client at the provider by changing only the base URL and API key
weight 3 · round to DeepInfraDocumentation explicitly and repeatedly states developers only need to change base_url and api_key to point an existing OpenAI SDK at DeepInfra, with a live probe confirming the OpenAI-compatible endpoint is functional and reachable. Missing for 10: independent third-party hands-on confirmation of a full SDK migration beyond docs and a keyless probe.
- [claimed-docs] “Point your existing OpenAI SDK to `https://api.deepinfra.com/v1/openai` and your code works without changes. No migration required.”
- [claimed-docs] “The only changes you need to make from your existing OpenAI code: 1. Set `base_url` to `https://api.deepinfra.com/v1/openai` 2. Set `api_…”
- [claimed-docs] “Drop-in OpenAI replacement. Point your existing OpenAI SDK to https://api.deepinfra.com/v1/openai and your code works without changes.”
- [probe] “PROBE models-endpoint (2026-09-04): GET https://api.deepinfra.com/v1/openai/models with NO API key returned HTTP 200 with a machine-readable…”
Docs explicitly state to point any OpenAI SDK at https://api.morphllm.com/v1 with a single API key, corroborated by a probe confirming the llms.txt describes it as OpenAI-compatible, and community evidence confirms it was actually wired up with an OpenAI-compatible client tool. missing for 10: independent hands-on confirmation of a truly drop-in swap with zero code changes beyond base URL/key, and no official OpenAPI spec found to verify full compatibility surface.
- [claimed-docs] “Point any OpenAI SDK at `https://api.morphllm.com/v1`. One API key covers the open-weight chat models and the specialized tools”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.morphllm.com/llms.txt # Morph API Documentation > https://docs.morphllm.com > Base URL: https://api…”
- [community] “This uses an OpenAI-compatible endpoint, so got this working with my llm.datasette.io CLI tool... One thing that worries me: since it's usin…”
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to DeepInfraDeepInfra's docs show broad API coverage matching most UI-facing capabilities: chat/completions, embeddings, vision/OCR, speech, image/video generation, private model deployment, and GPU clusters are all exposed via API endpoints, and the models endpoint is even queryable keylessly. However, there's no explicit statement of full UI/API parity, no OpenAPI/swagger spec was found (probes returned 404s), and no evidence covers account/billing/dashboard-management actions being API-accessible. missing for 10: explicit parity documentation, a discoverable OpenAPI schema, and evidence that account/billing/UI-console actions are also API-controllable.
- [claimed-docs] “OpenAI-compatible chat completions API — just change the base URL and model name.”
- [claimed-docs] “Run your own fine-tuned LLM on A100 / H100 / H200 / B200 / B300 with autoscaling.”
- [claimed-docs] “Need to run your own fine-tuned weights, or require data isolation? Deploy a dedicated instance on A100/H100/H200/B200/B300 with autoscaling…”
- [claimed-docs] “GPU Clusters for training and full control. Rent a B200 or B300 cluster with SSH access and run whatever you want.”
- [claimed-docs] “Embeddings & Reranking State-of-the-art embedding and reranker models for search and RAG.”
- [claimed-docs] “Image & Video Generation FLUX, Stable Diffusion, text-to-video, and more.”
- [claimed-docs] “Speech recognition (Whisper) and text-to-speech models.”
- [claimed-docs] “Vision & OCR Multimodal models for visual understanding and document text extraction.”
- [probe] “PROBE llms.txt: HTTP 404 at https://deepinfra.com/llms.txt”
- [probe] “PROBE docs-md: HTTP 404 at https://deepinfra.com/docs.md”
- [probe] “PROBE openapi: all candidate paths 404 (https://deepinfra.com/openapi.json, https://deepinfra.com/swagger.json, https://deepinfra.com/api/op…”
- [probe] “PROBE models-endpoint (2026-09-04): GET https://api.deepinfra.com/v1/openai/models with NO API key returned HTTP 200 with a machine-readable…”
Morph is fundamentally API-first — nearly all documented functionality (chat completions, Fast Apply, Compact, Reflexes, batch, dedicated endpoints, MCP) is exposed via the API/SDK per morph-docs-1 through morph-docs-16, and a playground/dashboard UI is only mentioned in passing (morph-comm-2). There's no explicit documentation enumerating dashboard-only features (billing, endpoint provisioning UI, playground testing) and confirming each has an API equivalent, so full parity isn't demonstrated. Missing for 10: explicit UI/dashboard feature list mapped to API endpoints, confirmation that account/billing/endpoint-management actions available in the dashboard are also API-accessible, and independent verification of parity.
- [claimed-docs] “Point any OpenAI SDK at `https://api.morphllm.com/v1`. One API key covers the open-weight chat models and the specialized tools”
- [claimed-docs] “Reserve model capacity by choosing a model and plan. Morph provisions and operates it”
- [community] “Seems completely broken. I used the provided HTML example on morphllm.com playground. Without editing anything, I pressed apply. Your model …”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.morphllm.com/llms.txt # Morph API Documentation > https://docs.morphllm.com > Base URL: https://api…”
ai-native userExport all of my data in open formats and leave
weight 3 · round drawnDeepInfranone0/10DeepInfra's evidence pack focuses entirely on its OpenAI-compatible inference API, model catalog, and infrastructure offerings; there is no mention of any user data export feature, open-format data portability, or account data download capability. Given the zero-retention policy, DeepInfra does not appear to store persistent user data, but no evidence at all addresses export tooling for whatever account/usage data does exist.
- [claimed-docs] “With our zero retention policy your inputs, your outputs, and your user data stay private. DeepInfra is SOC 2 and ISO 27001 certified.”
ai-native userRead the product's source under an open license
weight 2 · round drawnDeepInfranone0/10The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)
Pricing limits — free-tier ceilings, usage caps, and rate limits before you have to payPricing limits
Free-tier ceilings, usage caps, and rate limits before you have to pay
Limits
developerRead documented rate limits and how they scale across usage tiers before I hit them in production
weight 2 · round drawnDeepInfranone0/10Evidence shows DeepInfra documents a fail_fast parameter to get immediate 429s and priority/flex service tiers for speed vs cost tradeoffs, but there is no documentation of actual rate limit numbers, quotas, or how limits scale across usage/spend tiers. Missing for 10: explicit rate-limit tables, per-tier request/token quotas, and any usage-tier scaling documentation.
- [claimed-docs] “Set the optional `fail_fast` parameter to `true` to get an immediate HTTP 429 instead of waiting.”
- [claimed-docs] “Set service_tier to "priority" to request priority inference on supported models. Priority requests get faster time-to-first-token and highe…”
- [claimed-docs] “Set service_tier to "flex" to run Chat Completions requests at a lower cost in exchange for slower response times and occasional resource un…”
- [claimed-docs] “Set the optional fail_fast parameter to true to get an immediate HTTP 429 instead of waiting.”
Morphnone0/10The evidence mentions rate limits exist (morph-docs-16: 'same open source chat models, token billing, and rate limits') but never documents actual limit numbers, tiers, or how they scale with usage — no pricing/tier table or rate-limit reference is shown. Missing for 10: an actual rate-limit table or tier breakdown, numeric thresholds, and documentation on how limits change across plans.
- [claimed-docs] “Anthropic Messages supports the same open source chat models, token billing, and rate limits.”
- [claimed-docs] “Reserve model capacity by choosing a model and plan. Morph provisions and operates it”
Pricing
founderSet spending caps or budget alerts so a runaway workload cannot generate an unbounded bill
weight 1 · round drawnDeepInfranone0/10The evidence pack contains no mention of spending caps, budget alerts, usage limits, or billing controls anywhere in DeepInfra's docs or pages; only pay-per-token pricing and service-tier options (priority/flex) are described. This is a fair question for a usage-based API platform, so absence of evidence means 'none' rather than 'na'.
- [claimed-docs] “You only pay per token — no idle GPU time, no minimums, no seat fees.”
- [claimed-docs] “Low pay-as-you-go pricing - no long-term contracts, no hidden fees, no surprises.”
- [claimed-docs] “Low pay-as-you-go pricing - no long-term contracts, no hidden fees, no surprises. Startup? Enterprise? We can scale.”
Morphnone0/10No evidence pack item mentions spending caps, budget alerts, usage limits, or billing controls of any kind; docs focus on models, tools, and pricing mechanics like batch/cache but not cap-setting features. This axis applies to any paid API/cloud product but no capability is documented, so it's 'none' rather than 'na'.
founderSee public per-token prices for every hosted model without talking to sales
weight 3 · round to DeepInfraDocs repeatedly state pay-as-you-go, per-token pricing with no contracts or sales required (docs-12, docs-16, docs-24, docs-31), strongly implying self-serve access to prices, and the model catalog is enumerable via a keyless API (deepinfra-probe-rt-1). However, no evidence pack item shows an actual public price list or per-model $/token table a founder could browse. missing for 10: explicit citation of a pricing page or API field listing per-token prices for each hosted model, independent confirmation that prices are visible without account/sales contact.
- [claimed-docs] “You only pay per token — no idle GPU time, no minimums, no seat fees.”
- [claimed-docs] “Flex inference is billed at a 20% discount off the model's standard per-token price.”
- [claimed-docs] “Low pay-as-you-go pricing - no long-term contracts, no hidden fees, no surprises.”
- [claimed-docs] “Low pay-as-you-go pricing - no long-term contracts, no hidden fees, no surprises. Startup? Enterprise? We can scale.”
- [probe] “PROBE models-endpoint (2026-09-04): GET https://api.deepinfra.com/v1/openai/models with NO API key returned HTTP 200 with a machine-readable…”
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userChoose where my data is stored (region/residency)
weight 2 · round drawnDeepInfranone0/10No evidence of region selection or data residency controls; only zero-retention/SOC2/ISO27001 privacy claims are mentioned, with no mention of choosing storage region or geographic data residency options.
Morphnone0/10No evidence in the pack mentions data residency, regional storage options, or geographic controls; the closest is a comment about retention/training policy tiers (morph-comm-6), which is about usage not location. Missing for 10: any documentation of region selection, data residency guarantees, or geo-specific hosting options.
- [community] “Please clarify your privacy policy. If my interpretation is correct, paying users will have their data retained and trained on? ... Free Tie…”
ai-native userPrevent my data from being used to train AI models
weight 3 · round to DeepInfraDeepInfra explicitly states a zero data retention policy covering inputs, outputs, and user data, backed by SOC 2 and ISO 27001 certifications, directly addressing the no-training-data-use concern. Missing for 10: independent/third-party audit confirmation or explicit contractual opt-out language beyond the marketing statement.
- [claimed-docs] “With our zero retention policy your inputs, your outputs, and your user data stay private. DeepInfra is SOC 2 and ISO 27001 certified.”
A community-sourced excerpt of Morph's privacy policy (morph-comm-6) shows Enterprise Tier users can opt out of having code/data used for training, satisfying the story, but Free Tier data is explicitly used to train models by default — a significant caveat requiring a paid tier to actually prevent training use. No first-party Morph docs in the evidence pack directly address data retention/training opt-out. Missing for 10: first-party documentation of the privacy/data-use policy and opt-out mechanism, independent confirmation that Enterprise-tier exclusion is honored in practice.
- [community] “Please clarify your privacy policy. If my interpretation is correct, paying users will have their data retained and trained on? ... Free Tie…”
ai-native userControl data retention and deletion
weight 2 · round to DeepInfraDeepInfra states a 'zero retention policy' for inputs/outputs/user data and cites SOC 2 and ISO 27001 certification, implying strong default privacy posture, but there is no documented user-facing mechanism to configure retention periods, request deletion of stored data, or verify enforcement of the zero-retention claim. missing for 10: explicit data-deletion/retention-control API or settings, independent audit/verification of the zero-retention claim, and documentation of what data (if any) is logged/retained by default.
- [claimed-docs] “With our zero retention policy your inputs, your outputs, and your user data stay private. DeepInfra is SOC 2 and ISO 27001 certified.”
Morphnone0/10Evidence only shows a general privacy-policy statement about free vs enterprise data usage (morph-comm-6), with a community member explicitly asking for clarification — there is no documented user-facing control for data retention settings or deletion requests. Missing for 10: any docs on data retention windows, user-initiated deletion/export tools, or enterprise data handling guarantees beyond the raw policy snippet.
- [community] “Please clarify your privacy policy. If my interpretation is correct, paying users will have their data retained and trained on? ... Free Tie…”
ai-native userOpt out of telemetry and usage tracking
weight 2 · round to MorphDeepInfranone0/10The evidence pack describes a zero-retention data policy and SOC2/ISO27001 certification, but this addresses data retention rather than a specific telemetry/usage-tracking opt-out control; no docs mention any setting, header, or account option to disable telemetry or usage analytics.
Community evidence indicates a tiered privacy policy where free-tier code may be used for training while Enterprise-tier data is not used beyond immediate processing, implying paying/enterprise users can effectively opt out of data usage — but there is no explicit telemetry/usage-tracking opt-out control or documentation for individual users. missing for 10: explicit telemetry opt-out toggle/setting, first-party privacy documentation confirming opt-out mechanics, independent confirmation beyond a single HN comment.
- [community] “Please clarify your privacy policy. If my interpretation is correct, paying users will have their data retained and trained on? ... Free Tie…”
Reliability status — stories about reliability status in this arenaReliability status
Stories about reliability status in this arena
Reliability
founderGet a stated availability SLA on paid or enterprise tiers
weight 1 · round drawnDeepInfranone0/10The evidence pack includes pricing, features, and a public status page, but nowhere states an uptime/availability SLA percentage or enterprise contractual guarantee — no mention of SLA terms for paid or enterprise tiers.
- [probe] “PROBE status-page (2026-09-04): https://status.deepinfra.com returns HTTP 200 and renders a public service-status page (page body includes "…”
- [claimed-docs] “Low pay-as-you-go pricing - no long-term contracts, no hidden fees, no surprises. Startup? Enterprise? We can scale.”
- [claimed-docs] “Low pay-as-you-go pricing - no long-term contracts, no hidden fees, no surprises.”
Morphnone0/10No evidence pack item mentions an SLA, uptime commitment, or reliability guarantee for paid/enterprise tiers — dedicated endpoints and enterprise privacy terms are mentioned but no stated availability percentage or SLA terms are documented.
- [claimed-docs] “Reserve model capacity by choosing a model and plan. Morph provisions and operates it”
- [community] “Please clarify your privacy policy. If my interpretation is correct, paying users will have their data retained and trained on? ... Free Tie…”
founderCheck a public status page with incident history before betting production traffic on the platform
weight 2 · round to DeepInfraA probe confirms DeepInfra runs a public status page (status.deepinfra.com) that returns HTTP 200 and displays operational status, which a founder could check before committing production traffic. However, the evidence does not show an incident-history log, uptime SLA, or past-incident detail on that page, so the story is only partially confirmed. Missing for 10: evidence of incident history/timeline, uptime percentage stats, or independent commentary on past outages.
- [probe] “PROBE status-page (2026-09-04): https://status.deepinfra.com returns HTTP 200 and renders a public service-status page (page body includes "…”
Speed latency — stories about speed latency in this arenaSpeed latency
Stories about speed latency in this arena
Benchmarks
ml-engineerSee published tokens-per-second or latency numbers, benchmarks, or load-testing guides backing the provider's speed claims
weight 2 · round to MorphDeepInfranone0/10The evidence describes qualitative service tiers (priority/flex) that claim to affect speed, and one anecdotal HN comment about cold-start latency, but there are no published tokens-per-second figures, latency benchmarks, or load-testing guides substantiating DeepInfra's speed claims.
- [claimed-docs] “Priority requests get faster time-to-first-token and higher throughput during peak demand.”
- [claimed-docs] “Set service_tier to "priority" to request priority inference on supported models. Priority requests get faster time-to-first-token and highe…”
- [claimed-docs] “Set service_tier to "flex" to run Chat Completions requests at a lower cost in exchange for slower response times and occasional resource un…”
- [community] “Because this is popular model and many people use it, you will not experience the cold-start latency most likely. But in general it is <10s.”
Morph publishes specific throughput numbers (10,500+ tok/s Fast Apply, 33,000 tok/s Compact, 90ms classifiers, 30s Reflex training) across its docs and even one independent community post corroborates a speed/iteration boost, but there is no independent benchmark suite, third-party load-testing report, or reproducible methodology, and one community report describes inaccurate output rather than confirming throughput. missing for 10: independent benchmark/load-testing reports, published methodology or test conditions behind the tok/s figures, and resolution of the community accuracy complaint.
- [claimed-docs] “Keep your current Codex model and give it `edit_file` backed by `morph-v3-fast` at 10,500+ tok/s”
- [claimed-docs] “Fast Apply merges just the changed lines at 10,500 tok/s, 98% accuracy.”
- [claimed-docs] “Drop filler from chat history and code context at 33,000 tok/s. 50-70% reduction, every surviving line byte-for-byte identical to input.”
- [claimed-docs] “Small text classifiers that label a turn in ~90ms — jailbreaks, NSFW, stuck-in-a-loop, user frustration.”
- [claimed-docs] “A small Reflex trains in about 30 seconds.”
- [github] “Use Morph's API to intelligently modify existing code at 4,500+ tokens/sec”
- [community] “Have been using morph for a while (I am one of the authors of goose) and was surprised when introduced at the boost it gave me (much less it…”
- [community] “Seems completely broken. I used the provided HTML example on morphllm.com playground. Without editing anything, I pressed apply. Your model …”
Serving
developerServe latency-sensitive workloads with fast time-to-first-token and high-throughput generation
weight 3 · round drawnDeepInfra provides explicit priority service tier for faster time-to-first-token and higher throughput during peak demand (docs-4, docs-26), plus fail_fast for latency-sensitive workflows and a flex tier tradeoff, showing deliberate latency/throughput controls. Community evidence corroborates generally low cold-start latency (<10s) for popular models. Missing for 10: independent benchmark data on actual TTFT/throughput numbers and hands-on comparison to competitors.
- [claimed-docs] “Priority requests get faster time-to-first-token and higher throughput during peak demand.”
- [claimed-docs] “Set service_tier to "priority" to request priority inference on supported models. Priority requests get faster time-to-first-token and highe…”
- [claimed-docs] “Set service_tier to "flex" to run Chat Completions requests at a lower cost in exchange for slower response times and occasional resource un…”
- [claimed-docs] “Set the optional `fail_fast` parameter to `true` to get an immediate HTTP 429 instead of waiting.”
- [community] “Because this is popular model and many people use it, you will not experience the cold-start latency most likely. But in general it is <10s.”
Morph publishes concrete high-throughput numbers (10,500+ tok/s Fast Apply, 33,000 tok/s Compact, ~90ms classifiers, prefix caching with no surcharge) aimed squarely at low-latency/high-throughput serving, and independent community use (goose author) corroborates a real speed boost in practice. Missing for 10: explicit time-to-first-token benchmarks and independent third-party throughput verification beyond vendor docs and one anecdotal HN comment.
- [claimed-docs] “Keep your current Codex model and give it `edit_file` backed by `morph-v3-fast` at 10,500+ tok/s”
- [claimed-docs] “Fast Apply merges just the changed lines at 10,500 tok/s, 98% accuracy.”
- [claimed-docs] “Drop filler from chat history and code context at 33,000 tok/s. 50-70% reduction, every surviving line byte-for-byte identical to input.”
- [claimed-docs] “Small text classifiers that label a turn in ~90ms — jailbreaks, NSFW, stuck-in-a-loop, user frustration.”
- [claimed-docs] “Prefix caching is on for every open source model. No configuration, no cache-write surcharge.”
- [community] “Have been using morph for a while (I am one of the authors of goose) and was surprised when introduced at the boost it gave me (much less it…”
ml-engineerBenefit from prompt/prefix caching that reduces latency or cost on repeated context
weight 1 · round to MorphDeepInfranone0/10The evidence pack contains no mention of prompt caching, prefix caching, or any context-reuse feature that reduces latency/cost on repeated prompts; it only covers OpenAI-compatible API basics, priority/flex service tiers, and dedicated deployments, none of which address caching of repeated context.
Morph docs explicitly state prefix caching is enabled by default for all open-source models with no configuration and no cache-write surcharge, directly addressing latency/cost reduction on repeated context. Missing for 10: independent benchmark or community corroboration of actual latency/cost savings from caching specifically (community evidence covers Fast Apply speed, not caching).
- [claimed-docs] “Prefix caching is on for every open source model. No configuration, no cache-write surcharge.”
developerStream completions token by token over SSE for responsive user experiences
weight 3 · round to DeepInfraDeepInfra positions itself as a drop-in OpenAI-compatible API (same SDK, same code), which implies standard OpenAI SDK features like `stream=True` token-by-token SSE would work unchanged, but no evidence pack item explicitly documents or demonstrates streaming responses, SSE format, or token-by-token behavior. Missing for 10: explicit streaming/SSE documentation or examples, benchmarks on streaming latency, and independent confirmation that stream=True works as expected.
- [claimed-docs] “Point your existing OpenAI SDK to `https://api.deepinfra.com/v1/openai` and your code works without changes. No migration required.”
- [claimed-docs] “The only changes you need to make from your existing OpenAI code: 1. Set `base_url` to `https://api.deepinfra.com/v1/openai` 2. Set `api_…”
- [claimed-docs] “Drop-in OpenAI replacement. Point your existing OpenAI SDK to https://api.deepinfra.com/v1/openai and your code works without changes.”
Morph advertises full OpenAI SDK/API compatibility at api.morphllm.com/v1 (morph-docs-1), which implies standard streaming support, but no evidence explicitly documents SSE/token-by-token streaming, a `stream` parameter, or any latency/responsiveness benchmarks for streamed output. missing for 10: explicit docs or examples showing `stream=true`/SSE usage, first-party or community confirmation of token-by-token streaming behavior, and any measured time-to-first-token metrics.
- [claimed-docs] “Point any OpenAI SDK at `https://api.morphllm.com/v1`. One API key covers the open-weight chat models and the specialized tools”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.morphllm.com/llms.txt # Morph API Documentation > https://docs.morphllm.com > Base URL: https://api…”
Structured tool calling — stories about structured tool calling in this arenaStructured tool calling
Stories about structured tool calling in this arena
Structured
developerEnforce structured outputs against a JSON schema (or grammar) so model responses parse reliably
weight 3 · round drawnDeepInfranone0/10The evidence pack details DeepInfra's OpenAI-compatible API, pricing tiers, and model catalog, but contains no mention of JSON schema enforcement, structured output modes, or grammar-constrained decoding. Missing for 10: any documentation of `response_format`/json_schema support, grammar-based constrained generation, or examples showing reliable JSON parsing guarantees.
Morphnone0/10Morph's docs cover OpenAI-compatible endpoints, Fast Apply, compaction, batch, caching, and MCP integration, but no evidence describes JSON schema/grammar-constrained structured output enforcement for reliable parsing. Missing for 10: any mention of response_format/json_schema support, grammar constraints, or validation guarantees on model outputs.
Tools
ai-native userRely on faithful function/tool calling — including parallel and multi-step tool use — so agent loops run on open models without breaking
weight 3 · round to MorphDeepInfranone0/10The evidence pack only shows generic OpenAI-compatible API claims (base URL swap, chat completions) and unrelated features (priority tiers, GPU deployment, image/video models) but never mentions function/tool calling, parallel tool calls, or multi-step agentic tool use, nor any benchmark/community report on tool-calling fidelity. Missing for 10: explicit documentation of a `tools`/`function_call` parameter, evidence of parallel tool call support, and any hands-on or benchmark confirmation that tool calling works reliably in agent loops.
Morph documents OpenAI-compatible and Anthropic Messages-compatible endpoints and specialized tools like edit_file/Fast Apply meant to plug into agent loops (Claude Code, Codex) with high speed and claimed 98% accuracy, which implies decent tool-call fidelity for open models. However there's no explicit documentation of parallel or multi-step tool-call handling, and a hands-on community report describes the apply/tool behavior as 'completely broken' with unrequested edits, undercutting full confidence in reliability. Missing for 10: explicit parallel tool-call support docs, multi-step agent-loop stability guarantees, and independent verification resolving the reported apply failures.
- [claimed-docs] “Claude Code speaks the Anthropic Messages API, which Morph serves natively at `/v1/messages`.”
- [claimed-docs] “Keep your current Codex model and give it `edit_file` backed by `morph-v3-fast` at 10,500+ tok/s”
- [claimed-docs] “Fast Apply merges just the changed lines at 10,500 tok/s, 98% accuracy.”
- [claimed-docs] “Connect your favorite AI tools to Morph's blazing-fast file editing via Model Context Protocol.”
- [community] “Seems completely broken. I used the provided HTML example on morphllm.com playground. Without editing anything, I pressed apply. Your model …”
- [community] “Does Claude Code have a similar apply model? It does create diffs for you to accept/reject but then I feel like it's always using a find/rep…”
Not comparable on these axes
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableDeepInfranone0/10The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)
Morphn/aMorph is an LLM API/tool-serving platform (fast-apply, reflexes, model routing) that itself exposes an MCP server for other agents (e.g., Claude Code) to consume — it is not an agent host that ingests external MCP servers as tool sources. The story's client-side capability (plugging MCP servers into Morph so it can use their tools) is a category mismatch for this product type; all MCP evidence describes Morph being served TO clients, not consuming servers itself.
- [claimed-docs] “Install the Morph MCP so Claude Code can read it”
- [claimed-docs] “Connect your favorite AI tools to Morph's blazing-fast file editing via Model Context Protocol.”
- [probe] “official MCP server documented at https://docs.morphllm.com/guides/mcp”
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · not comparableDeepInfran/aDeepInfra is a raw inference API/cloud platform (LLMs, vision, embeddings, image/video generation) for developers to build on, not an end-user product that stores 'your data' and surfaces AI-generated insights/suggestions within its own UI. This story applies to data-holding SaaS products, not to an infrastructure/API provider.
- [claimed-docs] “DeepInfra is an AI inference cloud that makes it simple to run the latest machine learning models at scale — LLMs, vision, embeddings, image…”
- [claimed-docs] “Embeddings & Reranking State-of-the-art embedding and reranker models for search and RAG.”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · not comparableDeepInfranone0/10The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)
Morphn/aMorph is a developer-facing API/infrastructure platform (fast-apply, chat models, MCP tools) meant to be embedded into other products or coding agents — it is not itself an end-user product with a built-in assistant UI to delegate tasks to. This axis is a category error for an API/infra offering, not a missing feature.
ai-native userOperate the product with natural-language commands
weight 2 · not comparableDeepInfranone0/10The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na". (na/none harmonized at arena bring-up — see pipeline/scripts/na-harmonize.ts.)
Morphn/aMorph is a backend model-serving/API and MCP-tool provider consumed programmatically by coding agents (Claude Code, Cursor, etc.); it is not itself a user-facing surface where an end user types natural-language commands. The natural-language interface lives in the calling agent, not in Morph, so this axis is a category mismatch for this kind of infrastructure product.
ai-native userTest against a sandbox environment without touching production data
weight 1 · not comparableDeepInfranone0/10The evidence pack describes DeepInfra as a pay-per-token inference API with zero data retention, private dedicated deployments, and GPU clusters, but there is no mention of a distinct sandbox/test environment, test API keys, or any mechanism to separate test traffic from production data — instead it just uses live API keys against production endpoints. missing for 10: sandbox/test environment or mode, staging API keys, documented separation between test and production data flows.
- [claimed-docs] “Need to run your own fine-tuned weights, or require data isolation? Deploy a dedicated instance on A100/H100/H200/B200/B300 with autoscaling…”
- [claimed-docs] “With our zero retention policy your inputs, your outputs, and your user data stay private. DeepInfra is SOC 2 and ISO 27001 certified.”
- [claimed-docs] “You only pay per token — no idle GPU time, no minimums, no seat fees.”
ai-native userDefine rules that trigger actions automatically on events
weight 3 · not comparableDeepInfran/aDeepInfra is an inference API/hosting platform, not an automation/workflow product; it provides no event-trigger or rules-engine capability, and this axis is a category error for its product type.
Morph's 'Reflexes' are classifiers that detect events (jailbreak, frustration, loop) and can gate automatic actions like canary traffic-splitting or full migration between models, which is a narrow form of event-triggered automation. However there's no documented general-purpose rule engine letting users define arbitrary custom rules/actions beyond this migration-gating use case. Missing for 10: a general user-facing rules/automation builder, documentation of broader trigger-action mappings beyond model migration, and independent confirmation of custom Reflex-to-action wiring.
- [claimed-docs] “Move a production agent off Anthropic or OpenAI onto Kimi K3 — a 5% traffic trial or a full migration, gated by Reflexes.”
- [claimed-docs] “A canary keeps your current provider, sends a slice of production traffic to Kimi K3, and compares Reflex results before you switch.”
- [claimed-docs] “A small Reflex trains in about 30 seconds.”
ai-native userSchedule recurring jobs or workflows
weight 2 · not comparableDeepInfran/aDeepInfra is an inference API/GPU hosting platform, not an orchestration or workflow-scheduling product; scheduling recurring jobs is outside its product category (wrong axis) rather than a missing feature.
ai-native userVersion, review, and roll back my automations
weight 1 · not comparableDeepInfran/aDeepInfra is an inference API/GPU cloud provider, not an automation/workflow builder; there is no concept of user-created automations to version, review, or roll back — this axis is a category error for this product type.
Morphnone0/10Morph is an API/tooling platform for fast code editing, model routing, and reflex classifiers — there's no evidence of any versioning, review, or rollback mechanism for 'automations' (e.g., no workflow history, diff review UI for automation configs, or revert capability). Nothing in the evidence pack addresses this axis at all.
ai-native userSelf-host the core product
weight 3 · not comparableDeepInfran/aDeepInfra is a hosted inference cloud service (running models on its own GPU infrastructure); there is no evidence of, nor any product category expectation for, self-hosting the core DeepInfra platform itself. GPU cluster rental (docs-10) lets users run their own workloads on rented hardware, but that is not self-hosting DeepInfra's own product.
Morphnone0/10Morph is presented entirely as a hosted API/SaaS product (api.morphllm.com endpoints, dedicated endpoints as reserved capacity, prefix caching, batch processing) with no mention of on-premises deployment, downloadable server binaries, Docker images, or open-source release of the core service. Evidence pack contains no self-hosting instructions or claims.
- [claimed-docs] “Point any OpenAI SDK at `https://api.morphllm.com/v1`. One API key covers the open-weight chat models and the specialized tools”
- [claimed-docs] “Reserve model capacity by choosing a model and plan. Morph provisions and operates it”
- [probe] “PROBE llms.txt: HTTP 200 at https://docs.morphllm.com/llms.txt # Morph API Documentation > https://docs.morphllm.com > Base URL: https://api…”
- [probe] “PROBE openapi: all candidate paths 404 (https://docs.morphllm.com/openapi.json, https://docs.morphllm.com/swagger.json, https://docs.morphll…”