Baseten vs Morph

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round drawn
   Baseten✓fullprobed9/10

   Baseten hosts a verified llms.txt (HTTP 200, indexing docs) and an agent-setup page directing agents to install skills/MCP servers to search the docs, confirmed live via a working MCP endpoint. missing for 10: independent third-party confirmation of an agent successfully using llms.txt end-to-end beyond Baseten's own probes.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.baseten.co/llms.txt # Baseten - [Baseten overview](https://docs.baseten.co/overview.md): Run hoste…”
   • [probe] “PROBE docs-md: HTTP 200 at https://docs.baseten.co/overview.md > ## Documentation Index > Fetch the complete documentation index at: https:/…”
   • [claimed-docs] “Install the Baseten skill and MCP servers so your coding agent can manage your Baseten workspace and search these docs.”
   • [probe] “official MCP server documented at https://docs.baseten.co/agent-setup”
   • [probe] “PROBE mcp-endpoint (2026-09-04): POST initialize to https://docs.baseten.co/mcp answered HTTP 200 with a JSON-RPC/MCP response (event: messa…”

   proof ↗⚑ flag

   Morph✓fullprobed9/10

   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”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Baseten
   Baseten✓fullclaimed7/10

   Baseten provides a CLI (truss push, Baseten CLI/Switch), config.yaml-driven deployment, OpenAI-compatible REST APIs with async/webhook/polling support, and API-key-based auth/rate limiting, all of which support scripted, non-interactive CI/automation workflows. missing for 10: explicit CI/CD pipeline examples (e.g. GitHub Actions integration), independent hands-on confirmation of headless CLI use in automation, and documented non-interactive auth flow for CI secrets.

   • [github] “You write a `config.yaml` that specifies the model, the hardware, and the engine, then `uvx truss push` builds a TensorRT-optimized containe…”
   • [github] “Deploying a model to Baseten via Truss turns a Hugging Face model into a production-ready API endpoint. You write a `config.yaml` that speci…”
   • [claimed-docs] “Async inference returns a request ID quickly and completes later through webhook or polling, which suits batch work, long documents”
   • [claimed-docs] “Async inference returns a request ID quickly and completes later through webhook or polling, which suits batch work, long documents, or any …”
   • [claimed-docs] “Call hosted models through an OpenAI-compatible API, deploy your own models on dedicated infrastructure”
   • [claimed-docs] “x-ratelimit-remaining-requests: Reports how many requests remain before you reach the request rate limit.”
   • [claimed-docs] “You can also set a workspace budget and query usage by API key or model.”
   • [claimed-docs] “a `config.yaml` can define the model, hardware, and inference engine without custom serving code”

   proof ↗⚑ flag

   Morph~partialprobed6/10

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

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Baseten
   Baseten✓fullprobed8/10

   Baseten documents and hosts an official MCP server (docs.baseten.co/agent-setup, docs.baseten.co/mcp) that lets coding agents manage the Baseten workspace and search docs, and a live probe confirms the endpoint responds to MCP initialize with valid JSON-RPC capabilities. missing for 10: independent/community hands-on validation of the MCP server beyond the vendor's own probe, and more detail on the full tool surface exposed.

   • [claimed-docs] “Install the Baseten skill and MCP servers so your coding agent can manage your Baseten workspace and search these docs.”
   • [probe] “official MCP server documented at https://docs.baseten.co/agent-setup”
   • [probe] “PROBE mcp-endpoint (2026-09-04): POST initialize to https://docs.baseten.co/mcp answered HTTP 200 with a JSON-RPC/MCP response (event: messa…”

   proof ↗⚑ flag

   Morph✓fullprobed7/10

   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”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round to Baseten
   Baseten✓fullclaimed7/10

   Baseten ships official CLIs: Truss (`uvx truss push` to build/deploy models from a config.yaml, per baseten-gh-2/6) and Baseten Switch (a CLI referenced at /reference/cli/baseten-switch for routing coding-agent traffic, baseten-docs-34), plus one-command checkpoint deployment (baseten-docs-29). missing for 10: independent/hands-on verification of CLI behavior, and a full CLI reference/command list beyond scattered doc mentions.

   • [github] “You write a `config.yaml` that specifies the model, the hardware, and the engine, then `uvx truss push` builds a TensorRT-optimized containe…”
   • [github] “Deploying a model to Baseten via Truss turns a Hugging Face model into a production-ready API endpoint. You write a `config.yaml` that speci…”
   • [claimed-docs] “Deploy any synced checkpoint with one CLI command”
   • [claimed-docs] “Use [Baseten Switch](/reference/cli/baseten-switch) to route requests from Claude Code or Codex CLI to Model APIs.”
   • [claimed-docs] “Connect Claude Code, Codex CLI, or Pi with Baseten Switch.”

   proof ↗⚑ flag

   Morph—none0/10

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

   ⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round drawn
   Baseten✓fullprobed8/10

   Baseten exposes an OpenAI/Anthropic-compatible inference API (docs-21, docs-30), a documented CLI/Truss deployment workflow, training APIs (docs-32, docs-36), and usage/rate-limit endpoints, all backed by extensive public docs and a live, probe-verified /v1/models endpoint and MCP server. Missing for 10: a discoverable OpenAPI/swagger spec (probe-3 shows 404s across candidate paths) and independent third-party API usage reports beyond community anecdotes.

   • [claimed-docs] “They support the OpenAI Chat Completions API and the Anthropic Messages API in beta, so you can use familiar client SDKs.”
   • [claimed-docs] “Call hosted models through an OpenAI-compatible API, deploy your own models on dedicated infrastructure”
   • [claimed-docs] “Async inference returns a request ID quickly and completes later through webhook or polling, which suits batch work, long documents”
   • [claimed-docs] “Fine-tuning or running RL on a supported base model: Loops provisions a dedicated trainer and paired sampler, and each training step is an A…”
   • [claimed-docs] “Model APIs bill by token and enforce request and token rate limits. You can also set a workspace budget and query usage by API key or model.”
   • [probe] “PROBE models-endpoint (2026-09-04): GET https://inference.baseten.co/v1/models without a key returned HTTP 401 (No Authorization header prov…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.baseten.co/openapi.json, https://docs.baseten.co/swagger.json, https://docs.baseten.co/…”
   • [github] “You write a `config.yaml` that specifies the model, the hardware, and the engine, then `uvx truss push` builds a TensorRT-optimized containe…”

   proof ↗⚑ flag

   Morph✓fullprobed8/10

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

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round drawn
   Baseten—none0/10

   Baseten documents API keys, usage monitoring by API key, and workspace budgets, but no evidence describes scoped/least-privilege credential issuance (e.g., role-based permissions, restricted-scope keys, or per-agent credential minting). Monitoring usage by key is not the same as issuing scoped credentials.

   • [claimed-docs] “Model APIs bill by token and enforce request and token rate limits. You can also set a workspace budget and query usage by API key or model.”
   • [claimed-docs] “To monitor token and request consumption by API key or model, see Usage.”
   • [claimed-docs] “You can also set a workspace budget and query usage by API key or model.”
   • [claimed-docs] “To raise a Basic account's limits, request email verification. You can also use that form to move to Pro or Enterprise.”

   proof ↗⚑ flag

   Morph—none0/10

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

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to Baseten
   Baseten✓fullclaimed7/10

   Baseten ships the official open-source Truss SDK/CLI for packaging and deploying models (github.com/basetenlabs/truss) and also exposes OpenAI-compatible and Anthropic Messages-compatible endpoints so developers can use those official client SDKs (and LangChain) directly against Baseten (baseten-docs-21, baseten-docs-33, baseten-gh-1/2/5/6). This gives AI-native users multiple first-party and compatible SDK paths for building agentic workflows. Missing for 10: a dedicated first-party 'Baseten Python client' distinct from Truss, and independent/hands-on corroboration of SDK reliability beyond docs and repo README.

   • [github] “Write once, run anywhere: Package model code, weights, and dependencies with a model server that behaves the same in development and product…”
   • [github] “You write a `config.yaml` that specifies the model, the hardware, and the engine, then `uvx truss push` builds a TensorRT-optimized containe…”
   • [github] “Truss lets you serve models with the Baseten Inference Stack as well as deploy models from any open-source framework: vLLM, SGLang, TensorRT…”
   • [github] “Deploying a model to Baseten via Truss turns a Hugging Face model into a production-ready API endpoint. You write a `config.yaml` that speci…”
   • [claimed-docs] “They support the OpenAI Chat Completions API and the Anthropic Messages API in beta, so you can use familiar client SDKs.”
   • [claimed-docs] “Because Baseten exposes an OpenAI-compatible endpoint, you can use LangChain's `ChatOpenAI` with `with_structured_output` by pointing `base_…”
   • [claimed-docs] “Call hosted models through an OpenAI-compatible API, deploy your own models on dedicated infrastructure”

   proof ↗⚑ flag

   Morph~partialprobed6/10

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

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round to Baseten
   Baseten~partialclaimed4/10

   Docs mention that async inference results can be delivered via webhook callback, showing Baseten supports webhook-based notification for job completion, but there is no dedicated webhook subscription system (event types, signing, retry, subscription management) described anywhere in the evidence. Missing for 10: a general event-subscription/webhook API or docs page (event catalog, signature verification, delivery guarantees), coverage beyond async-inference completion notifications, and any independent confirmation of webhook reliability.

   • [claimed-docs] “Async inference returns a request ID quickly and completes later through webhook or polling, which suits batch work, long documents”
   • [claimed-docs] “Async inference returns a request ID quickly and completes later through webhook or polling, which suits batch work, long documents, or any …”
   • [claimed-docs] “Async inference returns a request ID quickly and completes later through webhook or polling”

   proof ↗⚑ flag

   Morph—none0/10

   No evidence in the pack mentions webhooks or any event-subscription mechanism; Morph's documented surface is API endpoints, MCP integration, and model tooling, with no webhook capability described.

   ⚑ flag

Agentic features

1. ai-native userSet up automations that run autonomously in the background

   weight 2 · round drawn
   Baseten—none0/10

   Baseten's evidence covers async inference (deferred single requests via webhook/polling), model deployment, and training, but there is no evidence of scheduling, triggers, or autonomous multi-step automations running in the background — async inference is single-request deferral, not an automation/workflow engine.

   ⚑ flag

   Morph—none0/10

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

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Baseten—none0/10

   Evidence shows extensive prose documentation (structured outputs, function calling, streaming, pricing) but no interactive API reference or runnable-example playground; a direct probe for an OpenAPI/Swagger spec (which typically powers interactive references) returned 404 on all candidate paths.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.baseten.co/openapi.json, https://docs.baseten.co/swagger.json, https://docs.baseten.co/…”
   • [claimed-docs] “Structured outputs let you generate text that conforms to specific JSON schemas, providing reliable data extraction and controlled text gene…”
   • [claimed-docs] “Function calling* (also called *tool calling*) lets a model choose a tool and produce its arguments from a user request.”
   • [claimed-docs] “Return model output token by token as it is generated.”

   proof ↗⚑ flag

   Morph—none0/10

   The 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…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Baseten—none0/10

   A direct probe for a machine-readable API spec (openapi.json, swagger.json, and related paths) returned 404 on all candidates, and no docs page claims to publish an OpenAPI/Swagger spec — only that the API is OpenAI/Anthropic-compatible in shape, which is not the same as Baseten publishing its own downloadable spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.baseten.co/openapi.json, https://docs.baseten.co/swagger.json, https://docs.baseten.co/…”
   • [claimed-docs] “They support the OpenAI Chat Completions API and the Anthropic Messages API in beta, so you can use familiar client SDKs.”
   • [claimed-docs] “Call hosted models through an OpenAI-compatible API, deploy your own models on dedicated infrastructure”

   proof ↗⚑ flag

   Morph—none0/10

   Morph 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…”

   proof ↗⚑ flag

3. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round to Baseten
   Baseten~partialprobed3/10

   Baseten documents a deprecation policy for Model APIs, instructing users to migrate to dedicated deployments when weights are deprecated (baseten-docs-12), showing some commitment to managing API lifecycle. However, there is no evidence of explicit API versioning (e.g., version numbers, changelogs) and probes for an OpenAPI/swagger spec returned 404s, suggesting no formal versioned API contract is published. Missing for 10: explicit API version scheme, published changelog, machine-readable API spec, and independent confirmation of deprecation timelines.

   • [claimed-docs] “Migrate to a dedicated deployment with the deprecated model weights. Contact us for assistance.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.baseten.co/openapi.json, https://docs.baseten.co/swagger.json, https://docs.baseten.co/…”

   proof ↗⚑ flag

   Morph—none0/10

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

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Baseten
   Baseten~partialclaimed5/10

   Baseten's async inference is explicitly described as suited to 'batch work, long documents' where a request ID is returned and completion happens later via webhook or polling, which supports processing many items without holding open connections. However, there is no documented batch/bulk API endpoint for submitting many items in a single call, nor bulk management operations (e.g., bulk model/deployment updates) across the platform. Missing for 10: explicit multi-item batch submission API, bulk resource management (models/deployments/keys) in one operation, and independent evidence of throughput at scale for bulk workloads.

   • [claimed-docs] “Async inference returns a request ID quickly and completes later through webhook or polling, which suits batch work, long documents”
   • [claimed-docs] “Async inference returns a request ID quickly and completes later through webhook or polling, which suits batch work, long documents, or any …”
   • [claimed-docs] “Async inference returns a request ID quickly and completes later through webhook or polling”

   proof ↗⚑ flag

   Morph~partialclaimed4/10

   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”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Morph
   Baseten—none0/10

   Baseten's docs describe async inference completing via webhook or polling, but this is a fixed completion-notification mechanism, not a user-defined rules engine for triggering arbitrary actions on events (e.g., alerts, autoscaling policies, custom conditional workflows). No evidence of any rule-definition or event-trigger automation feature exists in the pack.

   ⚑ flag

   Morph~partialclaimed4/10

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

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Baseten—none0/10

   Baseten's docs describe async inference (webhook/polling), training jobs, and deployments, but nothing in the evidence pack mentions a scheduler, cron-like trigger, or recurring/automated job orchestration feature. Since Baseten already runs jobs (training, inference) a scheduling capability is a fair ask, but no evidence shows it exists.

   ⚑ flag

   Morph—none0/10

   Morph is an API/model platform for code editing, apply, search, and agent-provider migration—no evidence of any scheduler, cron-like trigger, or recurring workflow/job execution feature in the docs or community posts.

   ⚑ flag

Batch

1. ml-engineerSubmit asynchronous batch inference jobs at a documented discount versus real-time pricing

   weight 2 · round to Morph
   Baseten~partialclaimed4/10

   Baseten documents asynchronous inference (request ID returned quickly, completion via webhook/polling) explicitly for batch work and long documents, so the submission mechanism is real. However, the only documented pricing discount is for KV-cached input tokens, not for async/batch requests specifically — there is no evidence of a documented discount rate for async vs real-time inference pricing. missing for 10: a documented async/batch discount rate or pricing tier distinct from real-time pricing, first-party pricing page showing the discount percentage.

   • [claimed-docs] “Async inference returns a request ID quickly and completes later through webhook or polling, which suits batch work, long documents”
   • [claimed-docs] “Async inference returns a request ID quickly and completes later through webhook or polling, which suits batch work, long documents, or any …”
   • [claimed-docs] “Async inference returns a request ID quickly and completes later through webhook or polling”
   • [claimed-docs] “Cached input tokens are prompt tokens served from the KV cache at a discounted rate. Caching is automatic and requires no request flags.”
   • [claimed-docs] “Model APIs bill by token and enforce request and token rate limits. You can also set a workspace budget and query usage by API key or model.”

   proof ↗⚑ flag

   Morph~partialclaimed6/10

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

   proof ↗⚑ flag

Dedicated

1. ml-engineerDeploy a model on dedicated GPU capacity with autoscaling so my traffic is isolated from the shared serverless pool

   weight 2 · round to Baseten
   Baseten~partialclaimed5/10

   Baseten clearly supports deploying models on dedicated GPUs/dedicated infrastructure (baseten-docs-2, baseten-docs-17, baseten-docs-30) with production-stable environments (baseten-docs-20) and resilient multi-cluster deployment (baseten-docs-15), which is distinct from the shared Model APIs pool (baseten-docs-1). However, no evidence explicitly describes autoscaling behavior for these dedicated deployments (scale-to-zero, concurrency-based scaling, etc.), so the isolation-plus-autoscaling combination is only partially substantiated. Missing for 10: explicit autoscaling documentation for dedicated deployments, and independent/hands-on confirmation of traffic isolation from the shared pool.

   • [claimed-docs] “Deploy an open-source, fine-tuned, or custom model on dedicated GPUs.”
   • [claimed-docs] “Deploy an open-source, fine-tuned, or custom model on dedicated infrastructure.”
   • [claimed-docs] “Call hosted models through an OpenAI-compatible API, deploy your own models on dedicated infrastructure”
   • [claimed-docs] “They also support stable environments for development, staging, and production.”
   • [claimed-docs] “Deployments run active-active across clusters and clouds. If a region or provider loses capacity, MCM reroutes and reprovisions workloads.”
   • [claimed-docs] “Use Model APIs to call supported language models without deploying them.”

   proof ↗⚑ flag

   Morph~partialclaimed4/10

   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”

   proof ↗⚑ flag

Fine tune

1. ml-engineerFine-tune a supported base model on my own data and serve the result on the same platform

   weight 2 · round to Baseten
   Baseten✓fullclaimed8/10

   Baseten documents Training Jobs/Loops for fine-tuning supported base models (Axolotl/TRL/custom loops), automatic checkpoint syncing, and one-CLI-command deployment of any synced checkpoint to production inference on the same platform, matching the story end-to-end. missing for 10: independent/hands-on third-party confirmation of the fine-tune-to-serve workflow (community evidence only covers unrelated Chains/embedding topics) and explicit list of which base models are 'supported' for fine-tuning.

   • [claimed-docs] “Fine-tune with Loops or run your own training code with Training Jobs.”
   • [claimed-docs] “Baseten trains models on managed GPUs and deploys the resulting checkpoints to production inference on the same platform.”
   • [claimed-docs] “Baseten provisions GPUs through MCM, runs your training container, and syncs checkpoints to storage as the job progresses.”
   • [claimed-docs] “Your Axolotl config, TRL script, or custom loop runs unchanged in a container. Baseten provisions the GPUs, syncs checkpoints as your job sa…”
   • [claimed-docs] “Deploy any synced checkpoint with one CLI command”
   • [claimed-docs] “Fine-tuning or running RL on a supported base model: Loops provisions a dedicated trainer and paired sampler, and each training step is an A…”
   • [claimed-docs] “Loops provisions a dedicated trainer and paired sampler, and each training step is an API call from a Python loop you write.”

   proof ↗⚑ flag

   Morph~partialclaimed4/10

   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”

   proof ↗⚑ flag

2. ml-engineerUpload and serve my own custom model weights or LoRA adapters

   weight 2 · round to Baseten
   Baseten✓fullclaimed8/10

   Baseten documents deploying custom/fine-tuned/open-source models via Truss (config.yaml + weights, supports transformers/diffusers/vLLM/etc.), and its Training product syncs LoRA/checkpoint artifacts that can be deployed as production endpoints with one CLI command, directly covering custom weights and LoRA adapter serving. Missing for 10: explicit LoRA-adapter-specific hot-swapping/multi-adapter serving docs and independent hands-on confirmation beyond vendor docs/GitHub README.

   • [claimed-docs] “Deploy an open-source, fine-tuned, or custom model on dedicated GPUs.”
   • [claimed-docs] “Deploy an open-source, fine-tuned, or custom model on dedicated infrastructure.”
   • [github] “Write once, run anywhere: Package model code, weights, and dependencies with a model server that behaves the same in development and product…”
   • [github] “You write a `config.yaml` that specifies the model, the hardware, and the engine, then `uvx truss push` builds a TensorRT-optimized containe…”
   • [github] “Support for all Python frameworks: From `transformers` and `diffusers` to PyTorch and TensorFlow to vLLM, SGLang, and TensorRT-LLM, Truss su…”
   • [claimed-docs] “Your Axolotl config, TRL script, or custom loop runs unchanged in a container. Baseten provisions the GPUs, syncs checkpoints as your job sa…”
   • [claimed-docs] “Deploy any synced checkpoint with one CLI command”
   • [claimed-docs] “Baseten trains models on managed GPUs and deploys the resulting checkpoints to production inference on the same platform.”

   proof ↗⚑ flag

   Morph—none0/10

   Morph'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”

   proof ↗⚑ flag

Catalog

1. ml-engineerGet newly released open-weight models on the platform quickly after their public release

   weight 2 · round drawn
   Baseten—none0/10

   The evidence describes Baseten's general capabilities (Model APIs, Truss deployment, training) but contains no claims or evidence about how quickly newly released open-weight models are added to the hosted Model APIs catalog after their public release. Missing for 10: any documentation or track record on model-catalog update cadence, day-1 support claims, or examples of specific new model releases being onboarded quickly.

   ⚑ flag

   Morph—none0/10

   The 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…”

   proof ↗⚑ flag

2. developerRely on a documented deprecation policy with advance notice before a hosted model is removed

   weight 1 · round to Baseten
   Baseten~partialclaimed4/10

   Baseten has a dedicated deprecation docs page instructing users to migrate to a dedicated deployment with deprecated model weights, showing some documented deprecation handling exists, but the evidence pack shows no explicit advance-notice period, timeline, or notification process. Missing for 10: concrete advance-notice window/SLA, notification channel details, and independent confirmation that notice is actually given before removal.

   • [claimed-docs] “Migrate to a dedicated deployment with the deprecated model weights. Contact us for assistance.”

   proof ↗⚑ flag

   Morph—none0/10

   No evidence of any documented deprecation policy or advance-notice commitment for hosted models; docs cover model capabilities, migration, and endpoints but nothing about model lifecycle/removal notice.

   ⚑ flag

3. ai-native userHave an agent enumerate the live model catalog programmatically via a documented GET /v1/models-style endpoint

   weight 2 · round to Baseten
   Baseten✓fullprobed8/10

   A live probe confirms the OpenAI-style GET /v1/models endpoint exists at https://inference.baseten.co/v1/models and returns proper JSON auth-error responses when unauthenticated, consistent with Baseten's documented OpenAI-compatible Chat Completions API (baseten-docs-21, baseten-docs-30). This lets an agent enumerate the model catalog programmatically once authenticated. Missing for 10: explicit first-party documentation of the /v1/models endpoint's response schema/fields and an authenticated hands-on example showing the returned catalog contents.

   • [probe] “PROBE models-endpoint (2026-09-04): GET https://inference.baseten.co/v1/models without a key returned HTTP 401 (No Authorization header prov…”
   • [claimed-docs] “They support the OpenAI Chat Completions API and the Anthropic Messages API in beta, so you can use familiar client SDKs.”
   • [claimed-docs] “Call hosted models through an OpenAI-compatible API, deploy your own models on dedicated infrastructure”

   proof ↗⚑ flag

   Morph—none0/10

   Morph 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…”

   proof ↗⚑ flag

4. 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 Morph
   Baseten~partialprobed4/10

   Baseten's docs confirm a serverless 'Model APIs' offering for calling supported language models without deploying them, with OpenAI/Anthropic-compatible endpoints, implying a hosted catalog exists — but no evidence enumerates specific open-weight families like Llama, Qwen, DeepSeek, or GPT-OSS, and the live models endpoint requires an API key to inspect. missing for 10: explicit list of supported model families, breadth/currency of catalog, independent confirmation of specific models available on shared serverless endpoints.

   • [claimed-docs] “Use Model APIs to call supported language models without deploying them.”
   • [claimed-docs] “They support the OpenAI Chat Completions API and the Anthropic Messages API in beta, so you can use familiar client SDKs.”
   • [claimed-docs] “Call hosted models through an OpenAI-compatible API, deploy your own models on dedicated infrastructure”
   • [probe] “PROBE models-endpoint (2026-09-04): GET https://inference.baseten.co/v1/models without a key returned HTTP 401 (No Authorization header prov…”

   proof ↗⚑ flag

   Morph~partialclaimed5/10

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

   proof ↗⚑ flag

Modalities

1. developerGenerate embeddings (and rerank results) for retrieval pipelines without a second vendor

   weight 1 · round to Baseten
   Baseten~partialcommunity5/10

   Baseten's general-purpose model deployment (Truss, custom model hosting, transformers/diffusers/vLLM support) can host embedding or reranking models on dedicated infrastructure, and a community report confirms real-world 'Baseten.co embedding workloads' being run on the platform. However, there is no first-party documentation of a dedicated embeddings or rerank API/product page, no mention of specific embedding model catalog entries, or built-in reranking features analogous to competitors' turnkey embedding endpoints. missing for 10: dedicated embeddings/rerank API docs, named embedding/rerank models in the catalog, first-party guidance on building RAG retrieval pipelines end-to-end.

   • [community] “Developer notes that with Baseten.co embedding workloads, the client (not server) becomes the bottleneck due to Python's GIL, prompting them…”
   • [claimed-docs] “Deploy an open-source, fine-tuned, or custom model on dedicated GPUs.”
   • [claimed-docs] “Deploy an open-source, fine-tuned, or custom model on dedicated infrastructure.”
   • [github] “Support for all Python frameworks: From `transformers` and `diffusers` to PyTorch and TensorFlow to vLLM, SGLang, and TensorRT-LLM, Truss su…”
   • [github] “Truss lets you serve models with the Baseten Inference Stack as well as deploy models from any open-source framework: vLLM, SGLang, TensorRT…”

   proof ↗⚑ flag

   Morph—none0/10

   Morph's evidence focuses on chat completions, Fast Apply code editing, compaction, batch processing, caching, and dedicated endpoints — none of the docs mention embeddings generation or reranking capabilities for retrieval pipelines.

   ⚑ flag

2. developerCall vision, audio, or image-generation models beyond text chat on the same platform

   weight 1 · round to Baseten
   Baseten~partialclaimed5/10

   Baseten's Truss framework explicitly supports 'diffusers' (used for image-generation models) and any open-source framework, and the platform lets you deploy 'open-source, fine-tuned, or custom' models on dedicated GPUs, implying vision/audio/image models can be hosted alongside text. However, the hosted 'Model APIs' product is explicitly scoped to 'supported language models' (baseten-docs-1), and no evidence names specific vision, audio, or image-generation models or endpoints being offered as first-class hosted APIs — multimodal support relies on self-deploying via Truss rather than a turnkey catalog like text chat models get. missing for 10: explicit vision/audio/image-generation model catalog or API examples, first-party documentation naming specific multimodal models supported out-of-the-box.

   • [claimed-docs] “Use Model APIs to call supported language models without deploying them.”
   • [claimed-docs] “Deploy an open-source, fine-tuned, or custom model on dedicated infrastructure.”
   • [github] “Support for all Python frameworks: From `transformers` and `diffusers` to PyTorch and TensorFlow to vLLM, SGLang, and TensorRT-LLM, Truss su…”
   • [github] “Truss lets you serve models with the Baseten Inference Stack as well as deploy models from any open-source framework: vLLM, SGLang, TensorRT…”
   • [claimed-docs] “Use a Python model class or a custom Docker server when you need custom preprocessing, postprocessing, dependencies, or server behavior.”

   proof ↗⚑ flag

   Morph—none0/10

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

   ⚑ flag

Compat

1. ai-native userPlug the provider into coding agents and agent frameworks through documented, first-party integration guides

   weight 2 · round to Baseten
   Baseten✓fullprobed9/10

   Baseten has dedicated first-party docs for connecting coding agents (Claude Code, Codex CLI, Pi) via Baseten Switch, plus a documented MCP server/skill for agent workspace management, and OpenAI/Anthropic-compatible endpoints enabling framework integrations like LangChain. This is corroborated by a live probe confirming the MCP endpoint responds correctly. Missing for 10: independent hands-on validation of the coding-agent connection flow beyond docs/probes.

   • [claimed-docs] “To point a coding agent at Model APIs, see [Coding agents](/inference/model-apis/coding-agents).”
   • [claimed-docs] “Install the Baseten skill and MCP servers so your coding agent can manage your Baseten workspace and search these docs.”
   • [claimed-docs] “Switch can also install Pi's direct Baseten provider, compare Baseten spend with estimated costs from Anthropic or OpenAI, and route request…”
   • [claimed-docs] “Connect Claude Code, Codex CLI, or Pi with Baseten Switch.”
   • [claimed-docs] “Use [Baseten Switch](/reference/cli/baseten-switch) to route requests from Claude Code or Codex CLI to Model APIs.”
   • [claimed-docs] “Because Baseten exposes an OpenAI-compatible endpoint, you can use LangChain's `ChatOpenAI` with `with_structured_output` by pointing `base_…”
   • [probe] “official MCP server documented at https://docs.baseten.co/agent-setup”
   • [probe] “PROBE mcp-endpoint (2026-09-04): POST initialize to https://docs.baseten.co/mcp answered HTTP 200 with a JSON-RPC/MCP response (event: messa…”

   proof ↗⚑ flag

   Morph✓fullprobed8/10

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

   proof ↗⚑ flag

2. 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 drawn
   Baseten✓fullclaimed8/10

   Baseten documents OpenAI Chat Completions API compatibility for Model APIs, explicitly enabling drop-in use with familiar client SDKs (e.g., LangChain's ChatOpenAI via base_url swap), and even documents a Switch tool that can route requests between Baseten and other providers like Anthropic/OpenAI mid-workflow. This directly supports agent-driven provider switching without provider-specific code changes. Missing for 10: independent/hands-on confirmation of seamless mid-workflow switching beyond vendor docs, and no explicit statement of full drop-in parity with OpenAI's complete API surface.

   • [claimed-docs] “They support the OpenAI Chat Completions API and the Anthropic Messages API in beta, so you can use familiar client SDKs.”
   • [claimed-docs] “Call hosted models through an OpenAI-compatible API, deploy your own models on dedicated infrastructure”
   • [claimed-docs] “Because Baseten exposes an OpenAI-compatible endpoint, you can use LangChain's `ChatOpenAI` with `with_structured_output` by pointing `base_…”
   • [claimed-docs] “Switch can also install Pi's direct Baseten provider, compare Baseten spend with estimated costs from Anthropic or OpenAI, and route request…”
   • [claimed-docs] “Use [Baseten Switch](/reference/cli/baseten-switch) to route requests from Claude Code or Codex CLI to Model APIs.”

   proof ↗⚑ flag

   Morph✓fullprobed8/10

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

   proof ↗⚑ flag

3. developerPoint an existing OpenAI SDK client at the provider by changing only the base URL and API key

   weight 3 · round to Baseten
   Baseten✓fullprobed9/10

   Baseten explicitly documents an OpenAI Chat Completions-compatible endpoint for its Model APIs, and shows real-world usage where only base_url and API key need to change (e.g. LangChain's ChatOpenAI pointed at Baseten). A live probe confirms an OpenAI-style /v1/models endpoint responding at inference.baseten.co. Missing for 10: no independent third-party hands-on report explicitly confirming a drop-in swap with the official OpenAI SDK client itself (only LangChain example and docs claims).

   • [claimed-docs] “They support the OpenAI Chat Completions API and the Anthropic Messages API in beta, so you can use familiar client SDKs.”
   • [claimed-docs] “Call hosted models through an OpenAI-compatible API, deploy your own models on dedicated infrastructure”
   • [claimed-docs] “Because Baseten exposes an OpenAI-compatible endpoint, you can use LangChain's `ChatOpenAI` with `with_structured_output` by pointing `base_…”
   • [probe] “PROBE models-endpoint (2026-09-04): GET https://inference.baseten.co/v1/models without a key returned HTTP 401 (No Authorization header prov…”

   proof ↗⚑ flag

   Morph✓fullprobed8/10

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

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Baseten
   Baseten~partialprobed6/10

   Baseten's core workflows — deploying models (Truss/config.yaml/CLI), running inference (OpenAI/Anthropic-compatible endpoints, streaming, async, structured outputs, function calling), and training (Loops API calls, Training Jobs CLI deploy) — are all API/CLI-driven, and usage/budget can be queried by API key, suggesting strong API-UI parity for the platform's main functions. However, there is no explicit documentation asserting full UI/API parity, no discoverable OpenAPI/reference spec (probe found only 404s), and no evidence that workspace/account-management UI features (team, billing settings) are exposed via API. Missing for 10: an explicit parity statement or full API reference, confirmation of workspace/admin functions being API-accessible, and independent verification of parity beyond inference/training/deploy workflows.

   • [github] “You write a `config.yaml` that specifies the model, the hardware, and the engine, then `uvx truss push` builds a TensorRT-optimized containe…”
   • [claimed-docs] “Your Axolotl config, TRL script, or custom loop runs unchanged in a container. Baseten provisions the GPUs, syncs checkpoints as your job sa…”
   • [claimed-docs] “Deploy any synced checkpoint with one CLI command”
   • [claimed-docs] “Loops provisions a dedicated trainer and paired sampler, and each training step is an API call from a Python loop you write.”
   • [claimed-docs] “Async inference returns a request ID quickly and completes later through webhook or polling, which suits batch work, long documents”
   • [claimed-docs] “Structured outputs let you generate text that conforms to specific JSON schemas, providing reliable data extraction and controlled text gene…”
   • [claimed-docs] “Function calling* (also called *tool calling*) lets a model choose a tool and produce its arguments from a user request.”
   • [claimed-docs] “You can also set a workspace budget and query usage by API key or model.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.baseten.co/openapi.json, https://docs.baseten.co/swagger.json, https://docs.baseten.co/…”

   proof ↗⚑ flag

   Morph~partialprobed4/10

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

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Baseten
   Baseten~partialclaimed4/10

   Baseten's tooling leans open: models are packaged via the open-source Truss format (config.yaml, no proprietary container lock-in), and training checkpoints are synced to external storage as the job runs, so a user's model weights and training artifacts aren't trapped in a proprietary format. However there is no explicit documentation of exporting workspace data, logs, usage/billing history, or deployment configs in bulk, and no dedicated 'account export' or data-portability feature. missing for 10: explicit full-account/data export tooling, documentation of exporting logs/usage/config metadata, and any user testimonial of migrating away with all data intact.

   • [github] “Write once, run anywhere: Package model code, weights, and dependencies with a model server that behaves the same in development and product…”
   • [github] “You write a `config.yaml` that specifies the model, the hardware, and the engine, then `uvx truss push` builds a TensorRT-optimized containe…”
   • [claimed-docs] “Your Axolotl config, TRL script, or custom loop runs unchanged in a container. Baseten provisions the GPUs, syncs checkpoints as your job sa…”
   • [claimed-docs] “Deploy any synced checkpoint with one CLI command”
   • [claimed-docs] “Baseten provisions GPUs through MCM, runs your training container, and syncs checkpoints to storage as the job progresses.”

   proof ↗⚑ flag

   Morph—none0/10

   No evidence of a data export feature or open-format export of user data/history; Morph is an API/tooling platform for code editing and model access, but nothing addresses exporting stored user data for portability or account exit.

   ⚑ flag

3. ai-native userRead the product's source under an open license

   weight 2 · round to Baseten
   Baseten~partialclaimed3/10

   Baseten's core platform (inference service, dashboard, orchestration/MCM) is proprietary SaaS with no evidence of an open license; only the Truss packaging library is open-source on GitHub, which is a peripheral client tool rather than the product itself. missing for 10: no open license for the actual Baseten platform/service source, no repository for the core inference or orchestration engine, only a tangential SDK is open.

   • [github] “Write once, run anywhere: Package model code, weights, and dependencies with a model server that behaves the same in development and product…”
   • [github] “You write a `config.yaml` that specifies the model, the hardware, and the engine, then `uvx truss push` builds a TensorRT-optimized containe…”
   • [github] “Fast developer loop: Iterate with live reload, skip Docker and Kubernetes configuration, and use a batteries-included serving environment.”
   • [github] “Support for all Python frameworks: From `transformers` and `diffusers` to PyTorch and TensorFlow to vLLM, SGLang, and TensorRT-LLM, Truss su…”
   • [github] “Truss lets you serve models with the Baseten Inference Stack as well as deploy models from any open-source framework: vLLM, SGLang, TensorRT…”
   • [github] “Deploying a model to Baseten via Truss turns a Hugging Face model into a production-ready API endpoint. You write a `config.yaml` that speci…”

   proof ↗⚑ flag

   Morph—none0/10

   Morph is a hosted API/SaaS product; no evidence of an open-license source repository for the core product (morph-demos is just example code, not the product source). No license or open-source claim appears anywhere in the evidence pack.

   ⚑ flag

Limits

1. developerRead documented rate limits and how they scale across usage tiers before I hit them in production

   weight 2 · round to Baseten
   Baseten~partialclaimed6/10

   Baseten has a dedicated pricing-and-limits doc covering request/token rate limits, rate-limit response headers, tier upgrades (Basic→Pro/Enterprise via email verification), workspace budgets, and usage monitoring by API key/model. However, it lacks a detailed table of exact numeric limits per tier and doesn't cover rate limits for dedicated-deployment (non-Model-APIs) inference. missing for 10: explicit numeric limit tables per tier, independent/community corroboration of documented limits, coverage of dedicated deployment rate limits (not just Model APIs).

   • [claimed-docs] “Model APIs bill by token and enforce request and token rate limits. You can also set a workspace budget and query usage by API key or model.”
   • [claimed-docs] “To monitor token and request consumption by API key or model, see Usage.”
   • [claimed-docs] “To raise a Basic account's limits, request email verification. You can also use that form to move to Pro or Enterprise.”
   • [claimed-docs] “x-ratelimit-remaining-requests: Reports how many requests remain before you reach the request rate limit.”
   • [claimed-docs] “You can also set a workspace budget and query usage by API key or model.”

   proof ↗⚑ flag

   Morph—none0/10

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

   proof ↗⚑ flag

Pricing

1. founderSet spending caps or budget alerts so a runaway workload cannot generate an unbounded bill

   weight 1 · round to Baseten
   Baseten~partialclaimed5/10

   Baseten docs mention setting a workspace budget and monitoring usage by API key/model, plus rate limits (request/token) that cap throughput, which supports pricing-limits awareness (baseten-docs-10, -23, -37, -38). However, there's no evidence of automated spending caps that hard-stop billing or proactive budget alerts/notifications — the workspace budget appears to be a settable figure without documented enforcement or alerting mechanics. Missing for 10: explicit alerting/notification system, enforcement behavior when budget is exceeded, and independent confirmation that budgets actually cap spend rather than just track it.

   • [claimed-docs] “Model APIs bill by token and enforce request and token rate limits. You can also set a workspace budget and query usage by API key or model.”
   • [claimed-docs] “To monitor token and request consumption by API key or model, see Usage.”
   • [claimed-docs] “x-ratelimit-remaining-requests: Reports how many requests remain before you reach the request rate limit.”
   • [claimed-docs] “You can also set a workspace budget and query usage by API key or model.”

   proof ↗⚑ flag

   Morph—none0/10

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

   ⚑ flag

2. founderSee public per-token prices for every hosted model without talking to sales

   weight 3 · round to Baseten
   Baseten~partialprobed3/10

   Docs confirm Model APIs are billed per token and that usage/rate limits can be queried without contacting sales, but no evidence shows an actual public price list with per-model per-token rates; the models endpoint even requires an API key to enumerate the catalog. missing for 10: a public pricing/rate-card page listing token prices per model, independent confirmation that pricing is visible without account creation or sales contact.

   • [claimed-docs] “Model APIs bill by token and enforce request and token rate limits. You can also set a workspace budget and query usage by API key or model.”
   • [claimed-docs] “To raise a Basic account's limits, request email verification. You can also use that form to move to Pro or Enterprise.”
   • [probe] “PROBE models-endpoint (2026-09-04): GET https://inference.baseten.co/v1/models without a key returned HTTP 401 (No Authorization header prov…”

   proof ↗⚑ flag

   Morph—none0/10

   No evidence pack item shows a public pricing page or per-token price list; docs mention batch pricing at 'half price' and mention of a 'plan' for dedicated endpoints but no explicit public per-token rates are cited, and no pricing page was probed or found.

   ⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Baseten—none0/10

   No evidence in the pack mentions region selection, data residency options, or multi-region storage controls for user data; deployments are described as active-active across clusters/clouds for reliability (baseten-docs-15), not as a user-selectable residency control. Missing for 10: any mention of region/residency selection, data storage location controls, or compliance-driven data locality options.

   • [claimed-docs] “Deployments run active-active across clusters and clouds. If a region or provider loses capacity, MCM reroutes and reprovisions workloads.”

   proof ↗⚑ flag

   Morph—none0/10

   No 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…”

   proof ↗⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round to Morph
   Baseten—none0/10

   No evidence pack content addresses data usage for training, opt-out controls, or any privacy/data-retention policy commitments; the axis is applicable (Baseten processes customer data/prompts and could plausibly offer such guarantees) but nothing in the docs, GitHub, or community evidence confirms it.

   ⚑ flag

   Morph~partialcommunity5/10

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

   proof ↗⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Baseten—none0/10

   The evidence pack covers deployment, training, inference APIs, pricing, and coding-agent integration, but no documentation addresses data retention policies, deletion of inputs/outputs, or user control over stored data/logs. This is a fair axis for an AI inference/hosting platform (buyers routinely ask about data handling), so it applies, but there is no evidence it is delivered.

   ⚑ flag

   Morph—none0/10

   Evidence 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…”

   proof ↗⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round to Morph
   Baseten—none0/10

   No evidence in the pack addresses telemetry/usage-tracking opt-out settings for Baseten's platform, CLI, or SDK; the evidence only covers inference features, training, and pricing/usage monitoring for billing purposes, not privacy telemetry controls.

   ⚑ flag

   Morph~partialcommunity3/10

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

   proof ↗⚑ flag

Reliability

1. founderGet a stated availability SLA on paid or enterprise tiers

   weight 1 · round drawn
   Baseten—none0/10

   Baseten documents Pro/Enterprise tiers, active-active multi-cloud deployments, and a public status page, but no evidence pack item states an actual SLA (uptime percentage, response-time guarantee, or contractual commitment) for any paid or enterprise tier.

   • [claimed-docs] “To raise a Basic account's limits, request email verification. You can also use that form to move to Pro or Enterprise.”
   • [claimed-docs] “Deployments run active-active across clusters and clouds. If a region or provider loses capacity, MCM reroutes and reprovisions workloads.”
   • [probe] “PROBE status-page (2026-09-04): https://status.baseten.co returns HTTP 200 and renders a public service-status page (page body includes "ope…”

   proof ↗⚑ flag

   Morph—none0/10

   No 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…”

   proof ↗⚑ flag

2. founderCheck a public status page with incident history before betting production traffic on the platform

   weight 2 · round to Baseten
   Baseten~partialprobed6/10

   A live probe confirms Baseten operates a public status page at status.baseten.co that returns HTTP 200 and shows current operational status, which is the core reliability-status signal a founder would check before committing production traffic. However, the evidence pack does not confirm the page includes a visible incident history/archive log, only that it renders current status. missing for 10: explicit confirmation that the status page displays past incident history/timeline, not just live status.

   • [probe] “PROBE status-page (2026-09-04): https://status.baseten.co returns HTTP 200 and renders a public service-status page (page body includes "ope…”

   proof ↗⚑ flag

   Morph—none0/10

   No evidence of a public status page or incident history for Morph anywhere in the pack; only docs, demos, and community discussion threads are present. missing for 10: a public status page URL, uptime/incident history, SLA commitments.

   ⚑ flag

Benchmarks

1. ml-engineerSee published tokens-per-second or latency numbers, benchmarks, or load-testing guides backing the provider's speed claims

   weight 2 · round to Morph
   Baseten—none0/10

   The evidence pack covers Baseten's product features (Model APIs, Truss, training, coding-agent integrations) but contains no published benchmark numbers, tokens-per-second figures, latency claims, or load-testing guides; the only performance-adjacent comment is a third-party observation about client-side GIL bottlenecks, which is unrelated to Baseten's own speed claims.

   ⚑ flag

   Morph~partialcommunity5/10

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

   proof ↗⚑ flag

Serving

1. developerServe latency-sensitive workloads with fast time-to-first-token and high-throughput generation

   weight 3 · round drawn
   Baseten✓fullcommunity8/10

   Baseten's docs and GitHub materials show explicit architecture for latency-sensitive, high-throughput serving: token-by-token streaming (baseten-docs-8, baseten-docs-26), dedicated GPU deployment with TensorRT-LLM/vLLM/SGLang optimized builds via Truss (baseten-gh-2, baseten-gh-4, baseten-gh-6), automatic KV-cache discounting for repeated prompt tokens (baseten-docs-11), and active-active multi-cluster routing to avoid capacity-related slowdowns (baseten-docs-15). Async inference is also offered for non-latency-critical batch work, showing the platform differentiates paths for latency vs throughput use cases (baseten-docs-9, baseten-docs-27). missing for 10: published quantitative TTFT/throughput benchmarks or independent third-party latency comparisons; one community note (baseten-comm-3) suggests client-side bottlenecks can arise in high-throughput client code, an important but non-contradicting caveat.

   • [claimed-docs] “Return model output token by token as it is generated.”
   • [claimed-docs] “Streaming sends tokens as they are generated over server-sent events, which suits long generations and UIs where partial output beats a blan…”
   • [claimed-docs] “Cached input tokens are prompt tokens served from the KV cache at a discounted rate. Caching is automatic and requires no request flags.”
   • [claimed-docs] “Deployments run active-active across clusters and clouds. If a region or provider loses capacity, MCM reroutes and reprovisions workloads.”
   • [github] “You write a `config.yaml` that specifies the model, the hardware, and the engine, then `uvx truss push` builds a TensorRT-optimized containe…”
   • [github] “Support for all Python frameworks: From `transformers` and `diffusers` to PyTorch and TensorFlow to vLLM, SGLang, and TensorRT-LLM, Truss su…”
   • [github] “Deploying a model to Baseten via Truss turns a Hugging Face model into a production-ready API endpoint. You write a `config.yaml` that speci…”
   • [claimed-docs] “Async inference returns a request ID quickly and completes later through webhook or polling, which suits batch work, long documents”
   • [claimed-docs] “Async inference returns a request ID quickly and completes later through webhook or polling, which suits batch work, long documents, or any …”
   • [community] “Developer notes that with Baseten.co embedding workloads, the client (not server) becomes the bottleneck due to Python's GIL, prompting them…”

   proof ↗⚑ flag

   Morph✓fullcommunity8/10

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

   proof ↗⚑ flag

2. ml-engineerBenefit from prompt/prefix caching that reduces latency or cost on repeated context

   weight 1 · round to Morph
   Baseten✓fullclaimed7/10

   Docs explicitly describe automatic prompt caching: cached input tokens are served from KV cache at a discounted rate with no request flags needed, directly addressing latency/cost reduction on repeated context. missing for 10: no quantified latency/cost benchmarks, no independent/community corroboration of caching behavior in practice.

   • [claimed-docs] “Cached input tokens are prompt tokens served from the KV cache at a discounted rate. Caching is automatic and requires no request flags.”
   • [claimed-docs] “Model APIs bill by token and enforce request and token rate limits. You can also set a workspace budget and query usage by API key or model.”

   proof ↗⚑ flag

   Morph✓fullclaimed8/10

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

   proof ↗⚑ flag

3. developerStream completions token by token over SSE for responsive user experiences

   weight 3 · round to Baseten
   Baseten✓fullclaimed8/10

   Baseten's docs explicitly describe SSE token-by-token streaming ('Return model output token by token as it is generated' / 'Streaming sends tokens as they are generated over server-sent events') as a first-class inference mode alongside async, with OpenAI/Anthropic-compatible client SDK support for easy integration. Missing for 10: no independent/hands-on benchmark or community confirmation of streaming latency/responsiveness in practice.

   • [claimed-docs] “Return model output token by token as it is generated.”
   • [claimed-docs] “Streaming sends tokens as they are generated over server-sent events, which suits long generations and UIs where partial output beats a blan…”
   • [claimed-docs] “They support the OpenAI Chat Completions API and the Anthropic Messages API in beta, so you can use familiar client SDKs.”

   proof ↗⚑ flag

   Morph~partialprobed3/10

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

   proof ↗⚑ flag

Structured

1. developerEnforce structured outputs against a JSON schema (or grammar) so model responses parse reliably

   weight 3 · round to Baseten
   Baseten✓fullclaimed8/10

   Baseten has dedicated first-party docs on structured outputs enforcing JSON schemas for reliable data extraction, plus separate function/tool calling support and OpenAI-compatible client integration (e.g., LangChain with_structured_output) confirming reliable parsing workflows. Missing for 10: independent/hands-on validation of schema-enforcement reliability and no mention of grammar-based (e.g., regex/CFG) constraints beyond JSON schema.

   • [claimed-docs] “Structured outputs let you generate text that conforms to specific JSON schemas, providing reliable data extraction and controlled text gene…”
   • [claimed-docs] “Function calling* (also called *tool calling*) lets a model choose a tool and produce its arguments from a user request.”
   • [claimed-docs] “Function calling (also called tool calling) lets a model choose a tool and produce its arguments from a user request.”
   • [claimed-docs] “Because Baseten exposes an OpenAI-compatible endpoint, you can use LangChain's `ChatOpenAI` with `with_structured_output` by pointing `base_…”
   • [claimed-docs] “They support the OpenAI Chat Completions API and the Anthropic Messages API in beta, so you can use familiar client SDKs.”

   proof ↗⚑ flag

   Morph—none0/10

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

   ⚑ flag

Tools

1. 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 Morph
   Baseten~partialclaimed4/10

   Baseten docs confirm function/tool-calling support ("lets a model choose a tool and produce its arguments from a user request") and structured outputs for reliable JSON generation, but the pack never mentions parallel tool calls, multi-step agent loops, or any reliability testing on open models. Missing for 10: explicit parallel tool-call support docs, multi-step agent loop examples, and independent/hands-on evidence of reliability across open models.

   • [claimed-docs] “Function calling* (also called *tool calling*) lets a model choose a tool and produce its arguments from a user request.”
   • [claimed-docs] “Function calling (also called tool calling) lets a model choose a tool and produce its arguments from a user request.”
   • [claimed-docs] “Structured outputs let you generate text that conforms to specific JSON schemas, providing reliable data extraction and controlled text gene…”
   • [claimed-docs] “Because Baseten exposes an OpenAI-compatible endpoint, you can use LangChain's `ChatOpenAI` with `with_structured_output` by pointing `base_…”

   proof ↗⚑ flag

   Morph~partialcommunity5/10

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

   proof ↗⚑ flag