Radeon RX 9070 XT vs AMD Instinct MI355X

Agent access

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

   weight 2 · round to Radeon RX 9070 XT
   Radeon RX 9070 XT✓fullprobed8/10

   A direct probe confirms rocm.docs.amd.com/llms.txt returns HTTP 200 with structured content pointing to sub-project docs, giving an agent a genuine machine-readable entry point into the Radeon/ROCm software docs relevant to this GPU. Missing for 10: no evidence of llms.txt coverage at finer granularity (e.g., per-page) and no OpenAPI/agent API surface (which 404s), so agentic doc access is present but not comprehensive.

   • [probe] “PROBE llms.txt: HTTP 200 at https://rocm.docs.amd.com/llms.txt # ROCm documentation > Note: ROCm documentation is split across multiple pro…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://rocm.docs.amd.com/openapi.json, https://rocm.docs.amd.com/swagger.json, https://rocm.docs.am…”
   • [claimed-docs] “PyTorch on Windows updated with ROCm 7.2.1 on AMD Radeon graphics products and AMD Ryzen AI processors.”

   proof ↗⚑ flag

   AMD Instinct MI355X✓fullprobed7/10

   A live llms.txt file was confirmed at rocm.docs.amd.com/llms.txt with a 200 response, providing an agent-readable entry point into ROCm documentation, and the runtime probe confirms the docs surface is crawlable without a browser. Missing for 10: no evidence of per-page markdown/.md variants (404 on that probe), no OpenAPI/agent tool spec, and no confirmation that agent-oriented docs cover the MI355X product pages themselves rather than just ROCm software.

   • [probe] “PROBE llms.txt: HTTP 200 at https://rocm.docs.amd.com/llms.txt # ROCm documentation > Note: ROCm documentation is split across multiple pro…”
   • [probe] “PROBE runtime (recorded 2026-09-15): the ROCm documentation at rocm.docs.amd.com answered a keyless curl naming ROCm — the MI355X's entire d…”
   • [probe] “PROBE docs-md: HTTP 404 at https://rocm.docs.amd.com/en/latest/.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://rocm.docs.amd.com/openapi.json, https://rocm.docs.amd.com/swagger.json, https://rocm.docs.am…”

   proof ↗⚑ flag

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

   weight 2 · round to AMD Instinct MI355X
   Radeon RX 9070 XT~partialclaimed4/10

   Evidence shows ROCm/Linux support with PyTorch, vLLM, and Llama.cpp for compute workloads (amd-rx-9070-xt-docs-2, -10, -11), which implies the GPU can be used for automated inference/training pipelines without a display, but there is no explicit documentation of headless operation, Docker/CI runner support, or automation-specific tooling. Missing for 10: explicit headless-mode docs, CI/container integration guides, and any hands-on evidence of running in automated pipelines.

   • [claimed-docs] “Radeon™ GPUs (9000 & select 7000 Series) Linux® PyTorch, TensorFlow, JAX, ONNX”
   • [claimed-docs] “**vLLM**: Full support.”
   • [claimed-docs] “**Llama.cpp**: Supported for efficient inference.”
   • [claimed-docs] “OS Support Windows 10 - 64-Bit Edition , Windows 11 - 64-Bit Edition , Linux x86 64-Bit”

   proof ↗⚑ flag

   AMD Instinct MI355X~partialclaimed6/10

   ROCm/Instinct docs show clear headless-automation building blocks — AMD Container Toolkit for Docker, GPU Operator for Kubernetes, Spur job scheduler (Slurm-compatible), and Cluster/ROCm Validation Suites for automated testing — all of which support running GPU workloads without a UI in CI/cluster pipelines. Missing for 10: no first-party CI pipeline example (e.g., GitHub Actions/GitLab runner config) or independent hands-on report confirming headless CI use in practice.

   • [claimed-docs] “GPU Operator Deploy and manage Instinct GPUs in Kubernetes clusters.”
   • [claimed-docs] “Spur AI-native job scheduler, drop-in compatible with Slurm, with GPU-first scheduling and Raft-based state.”
   • [claimed-docs] “Cluster Validation Suite Test scripts that validate AMD AI clusters end to end.”
   • [claimed-docs] “AMD Container Toolkit Integrate Instinct GPUs with Docker and container runtimes.”
   • [claimed-docs] “ROCm Validation Suite System validation and hardware diagnostics.”

   proof ↗⚑ flag

3. ai-native userUse an official CLI

   weight 2 · round to AMD Instinct MI355X
   Radeon RX 9070 XT—none0/10

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

   ⚑ flag

   AMD Instinct MI355X~partialclaimed5/10

   AMD ships official CLI tooling in its ecosystem — AMD SMI for GPU management and Spur, explicitly described as an 'AI-native job scheduler' with Slurm-compatible CLI — but these are infrastructure/ops CLIs rather than a CLI aimed at AI-native development or agentic workflows. Missing for 10: evidence of a CLI specifically designed for AI-agent/dev workflows (e.g., code generation, model interaction, agent orchestration) and independent hands-on confirmation of these CLIs' AI-native usability.

   • [claimed-docs] “AMD SMI Unified user-space tool to manage and monitor GPUs and drivers.”
   • [claimed-docs] “Spur AI-native job scheduler, drop-in compatible with Slurm, with GPU-first scheduling and Raft-based state.”
   • [claimed-docs] “AMD Container Toolkit Integrate Instinct GPUs with Docker and container runtimes.”

   proof ↗⚑ flag

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

   weight 3 · round drawn
   Radeon RX 9070 XT~partialprobed4/10

   AMD documents a public software stack (ROCm) with APIs/libraries (HIP, PyTorch/TensorFlow/JAX/ONNX/vLLM/llama.cpp integration) that let developers programmatically drive the GPU for AI workloads, and llms.txt is served for documentation discovery. However, there is no dedicated machine-callable REST/OpenAPI interface — the openapi probe returned 404 on all candidate paths — so an AI agent cannot invoke a structured public API directly, only use ROCm's compiled libraries/frameworks. Missing for 10: a documented REST/OpenAPI or similarly agent-consumable API endpoint, independent confirmation of programmatic control beyond framework bindings.

   • [claimed-docs] “PyTorch on Windows updated with ROCm 7.2.1 on AMD Radeon graphics products and AMD Ryzen AI processors.”
   • [claimed-docs] “Radeon™ GPUs (9000 & select 7000 Series) Linux® PyTorch, TensorFlow, JAX, ONNX”
   • [claimed-docs] “**vLLM**: Full support.”
   • [claimed-docs] “**Llama.cpp**: Supported for efficient inference.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://rocm.docs.amd.com/llms.txt # ROCm documentation > Note: ROCm documentation is split across multiple pro…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://rocm.docs.amd.com/openapi.json, https://rocm.docs.amd.com/swagger.json, https://rocm.docs.am…”

   proof ↗⚑ flag

   AMD Instinct MI355X~partialprobed4/10

   AMD documents extensive low-level APIs for driving the GPU (HIP runtime, ROCm libraries, AMD SMI, metrics exporter) and even exposes an llms.txt for machine consumption, but there is no unified, documented public API (e.g., OpenAPI/REST spec) that an AI-native agent could call to drive the product — probes for openapi.json/swagger.json all 404. missing for 10: a formal public API spec/SDK reference for agentic automation, evidence of programmatic/agent-driven control beyond developer-level HIP/ROCm libraries, independent confirmation of agent usage.

   • [claimed-docs] “HIP C++ Learn the HIP programming model.”
   • [claimed-docs] “AMD SMI Unified user-space tool to manage and monitor GPUs and drivers.”
   • [claimed-docs] “Device Metrics Exporter Prometheus-format GPU metrics for HPC and AI environments.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://rocm.docs.amd.com/llms.txt # ROCm documentation > Note: ROCm documentation is split across multiple pro…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://rocm.docs.amd.com/openapi.json, https://rocm.docs.amd.com/swagger.json, https://rocm.docs.am…”

   proof ↗⚑ flag

5. ai-native userBuild against official SDKs

   weight 2 · round to AMD Instinct MI355X
   Radeon RX 9070 XT✓fullprobed7/10

   AMD provides official ROCm SDK documentation for the RX 9070 XT enabling development with PyTorch, TensorFlow, JAX, ONNX, vLLM, and llama.cpp on both Windows and Linux, with an llms.txt confirming machine-readable docs availability. Missing for 10: independent hands-on developer confirmation of SDK stability/completeness, and no evidence of API/openapi endpoints for programmatic integration.

   • [claimed-docs] “PyTorch on Windows updated with ROCm 7.2.1 on AMD Radeon graphics products and AMD Ryzen AI processors.”
   • [claimed-docs] “Radeon™ GPUs (9000 & select 7000 Series) Linux® PyTorch, TensorFlow, JAX, ONNX”
   • [claimed-docs] “Radeon™ GPUs (9000 & select 7000 Series) Windows® PyTorch”
   • [claimed-docs] “**vLLM**: Full support.”
   • [claimed-docs] “**Llama.cpp**: Supported for efficient inference.”
   • [claimed-docs] “The same ROCm™ stack that powers your desktop development on RDNA™ architecture GPUs also supports AMD Instinct™ accelerators on CDNA™ archi…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://rocm.docs.amd.com/llms.txt # ROCm documentation > Note: ROCm documentation is split across multiple pro…”

   proof ↗⚑ flag

   AMD Instinct MI355X✓fullprobed8/10

   AMD ships extensive official ROCm SDK documentation covering HIP runtime, OpenMP, math/communication libraries, container toolkit, framework integrations (vLLM, SGLang), and cluster/scheduling tools, with docs confirmed live and crawlable. This is a strong official SDK ecosystem AI-native developers can build against, though it lacks an OpenAPI/programmatic API spec and independent third-party validation of SDK quality beyond skepticism about software support. Missing for 10: machine-readable API spec (openapi probe 404s), independent hands-on developer corroboration of SDK usability.

   • [claimed-docs] “The foundational libraries, runtimes, and tools for GPU computing on AMD hardware — math and compute libraries, communication primitives, HI…”
   • [claimed-docs] “Full-stack documentation and recipes to deploy AI workloads on AMD GPUs using popular ROCm-enabled frameworks.”
   • [claimed-docs] “Inference * [vLLM](https://rocm.docs.amd.com/projects/ai-ecosystem/en/latest/inference/vllm.html) * [SGLang](https://rocm.docs.amd.com/…”
   • [claimed-docs] “HIP C++ Learn the HIP programming model.”
   • [claimed-docs] “OpenMP Explore the OpenMP programming model.”
   • [claimed-docs] “AMD Container Toolkit Integrate Instinct GPUs with Docker and container runtimes.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://rocm.docs.amd.com/llms.txt # ROCm documentation > Note: ROCm documentation is split across multiple pro…”
   • [probe] “PROBE runtime (recorded 2026-09-15): the ROCm documentation at rocm.docs.amd.com answered a keyless curl naming ROCm — the MI355X's entire d…”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round drawn
   Radeon RX 9070 XT—none0/10

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

   ⚑ flag

   AMD Instinct MI355X—none0/10

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

   ⚑ flag

2. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round drawn
   Radeon RX 9070 XT—none0/10

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

   ⚑ flag

   AMD Instinct MI355X—none0/10

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

   ⚑ flag

3. ai-native userOperate the product with natural-language commands

   weight 2 · round drawn
   Radeon RX 9070 XT—none0/10

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

   ⚑ flag

   AMD Instinct MI355X—none0/10

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

   ⚑ flag

Inference stack

1. ai-native userThis GPU has a documented LLM inference story — low-precision formats (FP8/FP4) and supported serving stacks (TensorRT-LLM, vLLM, ROCm, llama.cpp) for this part

   weight 3 · round to AMD Instinct MI355X
   Radeon RX 9070 XT~partialclaimed5/10

   ROCm docs explicitly document serving-stack support for this Radeon line (vLLM 'Full support', llama.cpp 'Supported for efficient inference', plus PyTorch/TensorFlow/JAX/ONNX), but there is no mention of low-precision FP8/FP4 inference formats for the RX 9070 XT, and TensorRT-LLM is an NVIDIA-only stack so is not applicable here. Missing for 10: explicit FP8/FP4 quantization support documentation for this card, independent hands-on benchmarks confirming these serving stacks actually run well on RX 9070 XT.

   • [claimed-docs] “**vLLM**: Full support.”
   • [claimed-docs] “**Llama.cpp**: Supported for efficient inference.”
   • [claimed-docs] “Radeon™ GPUs (9000 & select 7000 Series) Linux® PyTorch, TensorFlow, JAX, ONNX”
   • [claimed-docs] “Radeon™ GPUs (9000 & select 7000 Series) Windows® PyTorch”

   proof ↗⚑ flag

   AMD Instinct MI355X~partialclaimed6/10

   Docs confirm ROCm-based inference stack support for vLLM and SGLang, plus explicit MXFP6/MXFP4 low-precision datatype support and large HBM3E memory for LLM inference. However, the story also asks about TensorRT-LLM and llama.cpp support, and explicit FP8 support, none of which appear in the evidence pack. missing for 10: TensorRT-LLM support evidence, llama.cpp support evidence, explicit FP8 precision documentation, independent benchmarks validating inference throughput on these stacks.

   • [claimed-docs] “Inference * [vLLM](https://rocm.docs.amd.com/projects/ai-ecosystem/en/latest/inference/vllm.html) * [SGLang](https://rocm.docs.amd.com/…”
   • [claimed-docs] “AMD Instinct™ MI355X GPUs deliver leadership AI and HPC performance enabling high density infrastructures with 288GB HBM3E memory, 8TB/s ban…”
   • [claimed-docs] “The foundational libraries, runtimes, and tools for GPU computing on AMD hardware — math and compute libraries, communication primitives, HI…”
   • [claimed-docs] “Full-stack documentation and recipes to deploy AI workloads on AMD GPUs using popular ROCm-enabled frameworks.”

   proof ↗⚑ flag

Tensor specs

1. ml engineerSize training and inference from published tensor throughput — TFLOPS or TOPS with precision and sparsity stated, not a bare marketing number

   weight 3 · round drawn
   Radeon RX 9070 XT—none0/10

   The evidence pack covers ROCm software support, framework compatibility, and general features, but contains no published TFLOPS/TOPS figures for the RX 9070 XT with precision (FP16/FP32/INT8) or sparsity stated. Missing for 10: any tensor throughput numbers, precision breakdown, sparsity conditions, or comparison to a baseline needed for training/inference sizing.

   • [claimed-docs] “OS Support Windows 10 - 64-Bit Edition , Windows 11 - 64-Bit Edition , Linux x86 64-Bit”
   • [claimed-docs] “AV1 Decode Yes AV1 Encode Yes”

   proof ↗⚑ flag

   AMD Instinct MI355X—none0/10

   The evidence includes only bare marketing multipliers (e.g., 'Up to 2.2X AI performance') and mentions of supported datatypes (MXFP6/MXFP4) without any published absolute TFLOPS/TOPS figures broken out by precision (FP8/FP6/FP4/BF16) or with/without sparsity — exactly the kind of unqualified claim the story asks to avoid. Community sources discuss architectural comparisons qualitatively but never cite AMD's actual per-precision throughput spec table.

   • [claimed-docs] “Up to 2.2X the AI performance vs. competitive accelerators1”
   • [claimed-docs] “AMD Instinct™ MI355X GPUs deliver leadership AI and HPC performance enabling high density infrastructures with 288GB HBM3E memory, 8TB/s ban…”
   • [community] “Compared to Nvidia's B200 SMs, CDNA 4 CUs have half the per-clock throughput across many 16-bit/8-bit data types; AMD still relies on a bigg…”

   proof ↗⚑ flag

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

   weight 2 · round to AMD Instinct MI355X
   Radeon RX 9070 XT—none0/10

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

   ⚑ flag

   AMD Instinct MI355X~partialclaimed4/10

   The ROCm/Instinct docs point to inference frameworks (vLLM, SGLang) that natively support batched/continuous-batch inference, implying MI355X can process many requests or items in bulk, and GPU partitioning/cluster tooling suggest large-scale parallel job handling. However, there is no direct documentation of a bulk-operation API, batch job submission interface, or AI-native bulk-processing workflow specific to MI355X itself — it's inferred through third-party software rather than demonstrated first-party capability. Missing for 10: explicit bulk/batch API documentation, benchmarked throughput for batch workloads, and independent verification of batch processing at scale.

   • [claimed-docs] “Inference * [vLLM](https://rocm.docs.amd.com/projects/ai-ecosystem/en/latest/inference/vllm.html) * [SGLang](https://rocm.docs.amd.com/…”
   • [claimed-docs] “Full-stack documentation and recipes to deploy AI workloads on AMD GPUs using popular ROCm-enabled frameworks.”
   • [claimed-docs] “GPU Partitioning Split compute units and memory to partition a single GPU.”

   proof ↗⚑ flag

2. ai-native userSchedule recurring jobs or workflows

   weight 2 · round to AMD Instinct MI355X
   Radeon RX 9070 XT—none0/10

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

   ⚑ flag

   AMD Instinct MI355X~partialclaimed4/10

   AMD ships 'Spur', described as an AI-native, Slurm-compatible job scheduler with GPU-first scheduling for Instinct clusters, which implies workflow/job scheduling capability, but the evidence never explicitly confirms recurring/cron-style job scheduling or automation-depth features. Missing for 10: documentation on recurring/cron scheduling semantics, workflow orchestration examples, and independent/hands-on validation of Spur's scheduling capabilities.

   • [claimed-docs] “Spur AI-native job scheduler, drop-in compatible with Slurm, with GPU-first scheduling and Raft-based state.”

   proof ↗⚑ flag

Media engines

1. creatorHardware media engines and creator-app acceleration are documented — AV1/HEVC encoders, and professional or ISV-certified driver support where the vendor claims it

   weight 2 · round to Radeon RX 9070 XT
   Radeon RX 9070 XT~partialclaimed4/10

   AMD's product page explicitly documents AV1 encode/decode support for the RX 9070 XT, which is relevant to creator workflows, but there is no mention of HEVC encode/decode support, no ISV-certified professional driver program (that's typically reserved for Radeon Pro cards), and no explicit creator-app acceleration claims (e.g., Premiere, DaVinci Resolve, OBS integration). Missing for 10: HEVC encoder/decoder documentation, ISV/professional certification claims, named creator-app acceleration partnerships or benchmarks.

   • [claimed-docs] “AV1 Decode Yes AV1 Encode Yes”

   proof ↗⚑ flag

   AMD Instinct MI355X—none0/10

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

   ⚑ flag

Scale out

1. ml engineerTrain and serve at datacenter scale on this part — documented high-bandwidth interconnect (NVLink, Infinity Fabric), multi-GPU systems, and rack-scale deployment

   weight 3 · round to AMD Instinct MI355X
   Radeon RX 9070 XT—none0/10

   The evidence only shows ROCm software compatibility and a vague note that the same stack 'also supports' Instinct/CDNA datacenter accelerators, but nothing documents NVLink/Infinity Fabric interconnect, multi-GPU scaling, or rack-scale deployment for the RX 9070 XT itself, which is a single consumer desktop card without such interconnects. missing for 10: any documentation of multi-GPU interconnect (NVLink/Infinity Fabric) for this card, multi-GPU system support, rack-scale deployment guidance.

   • [claimed-docs] “The same ROCm™ stack that powers your desktop development on RDNA™ architecture GPUs also supports AMD Instinct™ accelerators on CDNA™ archi…”
   • [claimed-docs] “This unified platform creates a seamless migration path, allowing you to develop applications locally and deploy them at scale with confiden…”

   proof ↗⚑ flag

   AMD Instinct MI355X~partialcommunity5/10

   Evidence documents rack-scale deployment tooling (Kubernetes GPU Operator, Container Toolkit, Cluster Validation Suite, Spur scheduler, SR-IOV, AMD SMI) and high memory bandwidth (8TB/s HBM3E), supporting datacenter-scale operations, but no citation explicitly documents the GPU-to-GPU interconnect fabric (e.g., Infinity Fabric link topology or scale-up fabric analogous to NVLink) that the story specifically calls out. Community sources focus on compute/memory comparisons, not interconnect topology, so this axis is only partially evidenced. Missing for 10: explicit Infinity Fabric/interconnect bandwidth specs and multi-GPU topology documentation, independent multi-node training benchmarks confirming interconnect scaling.

   • [claimed-docs] “GPU Operator Deploy and manage Instinct GPUs in Kubernetes clusters.”
   • [claimed-docs] “Spur AI-native job scheduler, drop-in compatible with Slurm, with GPU-first scheduling and Raft-based state.”
   • [claimed-docs] “Cluster Validation Suite Test scripts that validate AMD AI clusters end to end.”
   • [claimed-docs] “AMD Container Toolkit Integrate Instinct GPUs with Docker and container runtimes.”
   • [claimed-docs] “SR-IOV Yes”
   • [claimed-docs] “AMD Instinct™ MI355X GPUs deliver leadership AI and HPC performance enabling high density infrastructures with 288GB HBM3E memory, 8TB/s ban…”
   • [community] “MI355X's HBM3E subsystem gives it 288GB capacity at 8 TB/s vs Nvidia B200's 180GB at 7.7 TB/s, maintaining AMD's memory capacity/bandwidth l…”

   proof ↗⚑ flag

Linux support

1. developerLinux is a first-class citizen for this GPU — documented Linux driver releases and independent Linux testing of this part

   weight 2 · round drawn
   Radeon RX 9070 XT~partialclaimed6/10

   AMD's official docs explicitly list Linux x86-64 as a supported OS and provide detailed ROCm Linux documentation for PyTorch/TensorFlow/JAX/ONNX, vLLM, and llama.cpp on Radeon 9000-series GPUs, showing genuine first-class Linux driver/software support. However, the pack lacks independent hands-on Linux testing or benchmarks of the RX 9070 XT specifically (the only community citation is a general Windows-oriented performance review, not Linux-focused). Missing for 10: independent/third-party Linux driver stability or performance testing of this specific card, and any community confirmation of ROCm functionality on this GPU outside vendor docs.

   • [claimed-docs] “Radeon™ GPUs (9000 & select 7000 Series) Linux® PyTorch, TensorFlow, JAX, ONNX”
   • [claimed-docs] “OS Support Windows 10 - 64-Bit Edition , Windows 11 - 64-Bit Edition , Linux x86 64-Bit”
   • [claimed-docs] “**vLLM**: Full support.”
   • [claimed-docs] “**Llama.cpp**: Supported for efficient inference.”
   • [claimed-docs] “As a primarily open-source ecosystem, ROCm™ gives you the freedom to inspect, customize, and tailor the software stack to your specific need…”

   proof ↗⚑ flag

   AMD Instinct MI355X~partialcommunity6/10

   ROCm's entire documented stack (HIP, container toolkit, Kubernetes GPU operator, AMD SMI, cluster validation) is Linux-native and independent hands-on benchmarking (chipsandcheese architecture deep-dive, HN wafer.ai comparisons) treats MI355X as a real, testable part. However, no evidence cites explicit Linux kernel driver release notes/versioning or independent Linux-specific driver validation reports. Missing for 10: explicit Linux driver release notes/changelog, independent third-party Linux driver-level testing (not just architecture/benchmark commentary), confirmation that cited benchmarks ran on Linux.

   • [claimed-docs] “The foundational libraries, runtimes, and tools for GPU computing on AMD hardware — math and compute libraries, communication primitives, HI…”
   • [claimed-docs] “HIP C++ Learn the HIP programming model.”
   • [claimed-docs] “AMD Container Toolkit Integrate Instinct GPUs with Docker and container runtimes.”
   • [claimed-docs] “GPU Operator Deploy and manage Instinct GPUs in Kubernetes clusters.”
   • [community] “Compared to Nvidia's B200 SMs, CDNA 4 CUs have half the per-clock throughput across many 16-bit/8-bit data types; AMD still relies on a bigg…”
   • [community] “On every row the B300 beat the MI355X in a wafer.ai comparison; critics say the price comparison (MI355X at $2.5/hr) is unrealistic since no…”

   proof ↗⚑ flag

Open drivers

1. developerRun this GPU on an open driver — open-source kernel modules or upstream Linux support documented by the vendor

   weight 2 · round to Radeon RX 9070 XT
   Radeon RX 9070 XT~partialclaimed6/10

   AMD documents ROCm as a primarily open-source stack with Linux support and lists RX 9000-series compatibility, and Linux x86 64-bit OS support is confirmed, but there is no explicit vendor documentation of open-source kernel driver components (e.g., amdgpu upstream kernel module) specific to RX 9070 XT or a clear statement of which parts of the stack are closed-source firmware/blobs. missing for 10: explicit vendor confirmation of upstream open-source kernel module support for this specific GPU, independent/hands-on corroboration of open driver functioning on mainline Linux kernels.

   • [claimed-docs] “As a primarily open-source ecosystem, ROCm™ gives you the freedom to inspect, customize, and tailor the software stack to your specific need…”
   • [claimed-docs] “OS Support Windows 10 - 64-Bit Edition , Windows 11 - 64-Bit Edition , Linux x86 64-Bit”
   • [claimed-docs] “Radeon™ GPUs (9000 & select 7000 Series) Linux® PyTorch, TensorFlow, JAX, ONNX”

   proof ↗⚑ flag

   AMD Instinct MI355X—none0/10

   The evidence pack extensively documents ROCm's open-source user-space stack (libraries, runtimes, tools, monitoring, Kubernetes operator) but never mentions the amdgpu kernel driver, its open-source licensing, or upstream Linux kernel inclusion — the specific claim this story asks about is absent. Missing for 10: any vendor documentation of open-source kernel modules, upstream kernel driver support, or distro-inclusion status for the MI355X.

   ⚑ flag

4k gaming

1. gamerThis card drives high-refresh 4K gaming — vendor performance claims corroborated by independent game benchmarks

   weight 3 · round to Radeon RX 9070 XT
   Radeon RX 9070 XT~partialcommunity3/10

   Only one independent source (TechPowerUp) confirms the RX 9070 XT delivers competitive raster/ray-tracing performance versus similarly priced NVIDIA cards, but it doesn't specifically address 4K high-refresh benchmarks or vendor FPS claims. Missing for 10: explicit vendor 4K/144Hz+ performance claims, detailed independent 4K benchmark numbers across multiple games, and confirmation of sustained high-refresh framerates.

   • [community] “The RX 9070 XT offers competitive performance with similarly priced NVIDIA options in both raster and ray tracing, at a starting price of $6…”

   proof ↗⚑ flag

   AMD Instinct MI355X—none0/10

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

   ⚑ flag

Upscaling

1. gamerAI upscaling and frame generation are supported on this card — the DLSS or FSR generation is documented for this part, with broad game support

   weight 2 · round to Radeon RX 9070 XT
   Radeon RX 9070 XT~partialcommunity5/10

   AMD's product page confirms FSR ("Redstone") support on the RX 9070 XT, and third-party review corroborates strong raster/ray-tracing performance, but the evidence pack lacks detail on frame-generation specifics or a documented list of supported games. missing for 10: explicit frame-generation (FSR 3/4) feature naming, game compatibility list/count, independent hands-on upscaling benchmarks.

   • [claimed-docs] “AMD FSR™ "Redstone"”
   • [community] “The RX 9070 XT offers competitive performance with similarly priced NVIDIA options in both raster and ray tracing, at a starting price of $6…”

   proof ↗⚑ flag

   AMD Instinct MI355X—none0/10

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

   ⚑ flag

Llm memory

1. ai-native userRun a 70B-class quantized LLM on this GPU — published VRAM capacity and memory bandwidth that make local or single-node inference practical

   weight 3 · round to AMD Instinct MI355X
   Radeon RX 9070 XT—none0/10

   The evidence pack never states the RX 9070 XT's actual VRAM capacity or memory bandwidth; the one VRAM figure mentioned ("up to 48GB") is a generic Radeon workstation-GPU claim, not this card's spec, and there is no claim or benchmark showing a 70B-class quantized model running on this GPU. Software support (ROCm, vLLM, llama.cpp) is documented but doesn't substitute for the missing capacity/bandwidth evidence needed to judge practicality for 70B inference.

   • [claimed-docs] “**vLLM**: Full support.”
   • [claimed-docs] “**Llama.cpp**: Supported for efficient inference.”
   • [claimed-docs] “A local workstation equipped with a Radeon™ GPU, featuring up to 48GB of VRAM, offers a secure and economical alternative to relying solely …”

   proof ↗⚑ flag

   AMD Instinct MI355X✓fullcommunity8/10

   AMD publishes 288GB HBM3E capacity and 8TB/s bandwidth for MI355X, far exceeding what's needed for 70B-class quantized inference, and documents vLLM/SGLang inference stacks for deployment; independent analysis corroborates the memory capacity/bandwidth lead over competing accelerators. Missing for 10: no direct hands-on benchmark or published throughput numbers specifically for a 70B model at a given quantization on this GPU.

   • [claimed-docs] “AMD Instinct™ MI355X GPUs deliver leadership AI and HPC performance enabling high density infrastructures with 288GB HBM3E memory, 8TB/s ban…”
   • [claimed-docs] “Inference * [vLLM](https://rocm.docs.amd.com/projects/ai-ecosystem/en/latest/inference/vllm.html) * [SGLang](https://rocm.docs.amd.com/…”
   • [community] “MI355X's HBM3E subsystem gives it 288GB capacity at 8 TB/s vs Nvidia B200's 180GB at 7.7 TB/s, maintaining AMD's memory capacity/bandwidth l…”

   proof ↗⚑ flag

Memory spec

1. ml engineerMemory specs are published in full for this exact part — capacity, memory type, bus width, and bandwidth

   weight 2 · round to AMD Instinct MI355X
   Radeon RX 9070 XT—none0/10

   Evidence pack contains no VRAM capacity, memory type (GDDR6), bus width, or bandwidth figures for the RX 9070 XT—only ROCm software ecosystem claims and generic product page snippets unrelated to memory specs.

   ⚑ flag

   AMD Instinct MI355X~partialcommunity6/10

   AMD's official product page confirms capacity (288GB), memory type (HBM3E), and bandwidth (8TB/s) for the MI355X, corroborated independently by chipsandcheese's comparison data. However, no evidence anywhere states the memory bus width. missing for 10: published bus width (bits) for the HBM3E memory subsystem.

   • [claimed-docs] “AMD Instinct™ MI355X GPUs deliver leadership AI and HPC performance enabling high density infrastructures with 288GB HBM3E memory, 8TB/s ban…”
   • [community] “MI355X's HBM3E subsystem gives it 288GB capacity at 8 TB/s vs Nvidia B200's 180GB at 7.7 TB/s, maintaining AMD's memory capacity/bandwidth l…”

   proof ↗⚑ flag

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

   weight 2 · round to Radeon RX 9070 XT
   Radeon RX 9070 XT~partialprobed5/10

   AMD's ROCm docs claim the stack is a 'primarily open-source ecosystem' giving users freedom to inspect and customize the software, and this is corroborated by an accessible llms.txt docs endpoint, but this is the accompanying software stack, not the GPU's actual hardware/firmware source, and 'primarily' implies some closed-source components remain undisclosed. Missing for 10: explicit repository/license pointer for the actual open-sourced source code, confirmation of what portions (drivers, firmware) are closed, and independent hands-on verification of source availability.

   • [claimed-docs] “As a primarily open-source ecosystem, ROCm™ gives you the freedom to inspect, customize, and tailor the software stack to your specific need…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://rocm.docs.amd.com/llms.txt # ROCm documentation > Note: ROCm documentation is split across multiple pro…”

   proof ↗⚑ flag

   AMD Instinct MI355X—none0/10

   The evidence pack describes ROCm documentation, libraries, and tools but never states an open-source license or provides a link to source code repositories; no license terms are mentioned anywhere in the pack.

   ⚑ flag

2. ai-native userSelf-host the core product

   weight 3 · round to AMD Instinct MI355X
   Radeon RX 9070 XT✓fullclaimed7/10

   As a discrete GPU, the RX 9070 XT is inherently self-hosted hardware; AMD's docs explicitly position a local Radeon workstation as a secure, economical alternative to cloud-based AI solutions, backed by open ROCm stack support for PyTorch/TensorFlow/JAX/ONNX/vLLM/llama.cpp on both Windows and Linux. Missing for 10: independent hands-on validation of a fully self-hosted AI stack setup, and more detailed first-party self-hosting/deployment guides beyond general ROCm docs.

   • [claimed-docs] “A local workstation equipped with a Radeon™ GPU, featuring up to 48GB of VRAM, offers a secure and economical alternative to relying solely …”
   • [claimed-docs] “This unified platform creates a seamless migration path, allowing you to develop applications locally and deploy them at scale with confiden…”
   • [claimed-docs] “The same ROCm™ stack that powers your desktop development on RDNA™ architecture GPUs also supports AMD Instinct™ accelerators on CDNA™ archi…”
   • [claimed-docs] “Radeon™ GPUs (9000 & select 7000 Series) Linux® PyTorch, TensorFlow, JAX, ONNX”
   • [claimed-docs] “**vLLM**: Full support.”
   • [claimed-docs] “**Llama.cpp**: Supported for efficient inference.”

   proof ↗⚑ flag

   AMD Instinct MI355X✓fullcommunity9/10

   The MI355X is sold as on-prem hardware, and AMD provides a full deployment stack for self-hosting: ROCm runtime/libraries, GPU Operator for Kubernetes, AMD Container Toolkit for Docker, Cluster Validation Suite, Device Metrics Exporter, and the Spur scheduler, all documented for running the GPU in a customer-owned datacenter. Community commentary corroborates real-world self-hosted comparisons (e.g., wafer.ai benchmarks) confirming the hardware is deployed and operated independently by third parties. Missing for 10: independent hands-on report specifically walking through a full self-host bring-up (rather than benchmark-only) confirming ease of deployment.

   • [claimed-docs] “GPU Operator Deploy and manage Instinct GPUs in Kubernetes clusters.”
   • [claimed-docs] “AMD Container Toolkit Integrate Instinct GPUs with Docker and container runtimes.”
   • [claimed-docs] “Cluster Validation Suite Test scripts that validate AMD AI clusters end to end.”
   • [claimed-docs] “Device Metrics Exporter Prometheus-format GPU metrics for HPC and AI environments.”
   • [claimed-docs] “Spur AI-native job scheduler, drop-in compatible with Slurm, with GPU-first scheduling and Raft-based state.”
   • [community] “On every row the B300 beat the MI355X in a wafer.ai comparison; critics say the price comparison (MI355X at $2.5/hr) is unrealistic since no…”

   proof ↗⚑ flag

Efficiency

1. ml engineerSustained workloads are power-efficient on this part — documented power envelopes with independent performance-per-watt testing

   weight 2 · round drawn
   Radeon RX 9070 XT—none0/10

   Evidence covers ROCm software support, framework compatibility, and general GPU features, but there is no documented power envelope data or independent performance-per-watt testing for sustained ML workloads on this card. missing for 10: TDP/power envelope specs for sustained ML loads, independent perf-per-watt benchmarks, thermal/power throttling behavior under long-running compute jobs.

   ⚑ flag

   AMD Instinct MI355X—none0/10

   The evidence pack lacks any documented TDP/power envelope specs or independent performance-per-watt benchmarking for the MI355X; community sources focus on raw throughput and memory bandwidth comparisons (chipsandcheese, wafer.ai) but never normalize for power draw. Missing for 10: official power envelope/TDP documentation, independent perf-per-watt benchmarks, sustained-workload thermal/power test data.

   • [community] “Compared to Nvidia's B200 SMs, CDNA 4 CUs have half the per-clock throughput across many 16-bit/8-bit data types; AMD still relies on a bigg…”
   • [community] “MI355X's HBM3E subsystem gives it 288GB capacity at 8 TB/s vs Nvidia B200's 180GB at 7.7 TB/s, maintaining AMD's memory capacity/bandwidth l…”
   • [community] “On every row the B300 beat the MI355X in a wafer.ai comparison; critics say the price comparison (MI355X at $2.5/hr) is unrealistic since no…”

   proof ↗⚑ flag

Psu planning

1. gamerSpec a build around published board power — TDP/TGP, connector requirements, and cooling guidance for this exact card

   weight 2 · round drawn
   Radeon RX 9070 XT—none0/10

   The evidence pack covers ROCm/software ecosystem support, AMD Software features, and general performance comparison, but contains no mention of TDP/TGP figures, PCIe power connector requirements, or cooling/case guidance for the RX 9070 XT. This is a fair axis for a discrete GPU, but nothing in the pack substantiates it.

   ⚑ flag

   AMD Instinct MI355X—none0/10

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

   ⚑ flag

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

   weight 3 · round drawn
   Radeon RX 9070 XT—none0/10

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

   ⚑ flag

   AMD Instinct MI355X—none0/10

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

   ⚑ flag

Compute stack

1. developerShip GPU-compute workloads on the vendor's toolchain — CUDA or ROCm/HIP documentation lists this part as a supported target

   weight 3 · round to AMD Instinct MI355X
   Radeon RX 9070 XT✓fullclaimed8/10

   ROCm documentation explicitly lists RX 9000 series (including 9070 XT) as a supported target on both Windows and Linux, with PyTorch, TensorFlow, JAX, ONNX, vLLM, and Llama.cpp support, plus a stated migration path to AMD Instinct datacenter GPUs. missing for 10: independent hands-on developer corroboration of ROCm workflows on this specific card beyond vendor docs, and no mention of CUDA compatibility layer maturity/limitations.

   • [claimed-docs] “PyTorch on Windows updated with ROCm 7.2.1 on AMD Radeon graphics products and AMD Ryzen AI processors.”
   • [claimed-docs] “Radeon™ GPUs (9000 & select 7000 Series) Linux® PyTorch, TensorFlow, JAX, ONNX”
   • [claimed-docs] “Radeon™ GPUs (9000 & select 7000 Series) Windows® PyTorch”
   • [claimed-docs] “**vLLM**: Full support.”
   • [claimed-docs] “**Llama.cpp**: Supported for efficient inference.”
   • [claimed-docs] “The same ROCm™ stack that powers your desktop development on RDNA™ architecture GPUs also supports AMD Instinct™ accelerators on CDNA™ archi…”

   proof ↗⚑ flag

   AMD Instinct MI355X✓fullprobed9/10

   ROCm documentation explicitly covers HIP runtime, libraries, frameworks, and inference stacks (vLLM, SGLang) targeting Instinct GPUs, and Instinct-specific docs list HIP C++, OpenMP, and other toolchain components for the MI355X line, confirming it as a supported ROCm/HIP target. missing for 10: no explicit MI355X-named code sample or compatibility matrix entry pinpointing this exact SKU rather than the Instinct family generally.

   • [claimed-docs] “The foundational libraries, runtimes, and tools for GPU computing on AMD hardware — math and compute libraries, communication primitives, HI…”
   • [claimed-docs] “Inference * [vLLM](https://rocm.docs.amd.com/projects/ai-ecosystem/en/latest/inference/vllm.html) * [SGLang](https://rocm.docs.amd.com/…”
   • [claimed-docs] “HIP C++ Learn the HIP programming model.”
   • [claimed-docs] “OpenMP Explore the OpenMP programming model.”
   • [probe] “PROBE runtime (recorded 2026-09-15): the ROCm documentation at rocm.docs.amd.com answered a keyless curl naming ROCm — the MI355X's entire d…”

   proof ↗⚑ flag

Frameworks

1. ml engineerPyTorch and mainstream ML frameworks run on this GPU through officially documented builds and support matrices

   weight 2 · round drawn
   Radeon RX 9070 XT✓fullclaimed8/10

   AMD's official ROCm docs explicitly list RX 9000 series support for PyTorch (Windows and Linux), TensorFlow, JAX, ONNX, vLLM, and Llama.cpp, with a documented support matrix and OS support (Windows/Linux) confirmed on AMD's product page. Missing for 10: independent hands-on confirmation of install success/version compatibility and no community corroboration of real-world PyTorch training/inference workflows on this specific card.

   • [claimed-docs] “PyTorch on Windows updated with ROCm 7.2.1 on AMD Radeon graphics products and AMD Ryzen AI processors.”
   • [claimed-docs] “Radeon™ GPUs (9000 & select 7000 Series) Linux® PyTorch, TensorFlow, JAX, ONNX”
   • [claimed-docs] “Radeon™ GPUs (9000 & select 7000 Series) Windows® PyTorch”
   • [claimed-docs] “**vLLM**: Full support.”
   • [claimed-docs] “**Llama.cpp**: Supported for efficient inference.”
   • [claimed-docs] “OS Support Windows 10 - 64-Bit Edition , Windows 11 - 64-Bit Edition , Linux x86 64-Bit”

   proof ↗⚑ flag

   AMD Instinct MI355X✓fullprobed8/10

   AMD documents ROCm-enabled framework support with specific recipes for PyTorch-adjacent ML stacks and inference frameworks (vLLM, SGLang) tied to Instinct GPUs, backed by a live, crawlable documentation surface. Missing for 10: an explicit official PyTorch build/support-matrix page or version-compatibility table directly citing PyTorch, and independent hands-on confirmation of PyTorch working smoothly on MI355X specifically (only general software-support skepticism exists in community commentary).

   • [claimed-docs] “Full-stack documentation and recipes to deploy AI workloads on AMD GPUs using popular ROCm-enabled frameworks.”
   • [claimed-docs] “Inference * [vLLM](https://rocm.docs.amd.com/projects/ai-ecosystem/en/latest/inference/vllm.html) * [SGLang](https://rocm.docs.amd.com/…”
   • [claimed-docs] “The foundational libraries, runtimes, and tools for GPU computing on AMD hardware — math and compute libraries, communication primitives, HI…”
   • [probe] “PROBE runtime (recorded 2026-09-15): the ROCm documentation at rocm.docs.amd.com answered a keyless curl naming ROCm — the MI355X's entire d…”
   • [community] “On the MI355X (288GB HBM3E) and MI325X announcement, a commenter noted AMD's pricing looks good vs Nvidia H100/B100 at around $15k, but expr…”

   proof ↗⚑ flag