How is QM trying to differentiate from HarnessRouter.ai, which launched on Launch YC about 10 days ago? https://www.ycombinator.com/launches/RpL-harnessrouter-b

How is QM trying to differentiate from HarnessRouter.ai, which launched on Launch YC about 10 days ago? https://www.ycombinator.com/launches/RpL-harnessrouter-bring-the-world-s-best-ai-agents-into-your-app-with-one-api https://www.ycombinator.com/launches/RpL-harnessrouter-bring... Both seem to provide a unified interface across different harnesses/models. HarnessRouter exposes that as a developer API for embedding agent-powered features into products, with Task / Run / Session / Streaming / File / Artifact / Renderer contracts, plus tracing around harness/model behavior over time. Is the main distinction that QM is a company workspace, while HarnessRouter is an embeddable harness layer for product teams and enterprises?