Scalar Research designed
Scalar is a strong candidate for the GPUaaS rendered OpenAPI reference because it has a Docusaurus plugin, an OpenAPI-first API reference, and a modern API client/playground posture. It should be compared directly against Stoplight Elements using the same synced OpenAPI artifact.
Current Finding
| Area | Assessment |
|---|---|
| Docusaurus integration | Strong fit; Scalar documents an @scalar/docusaurus plugin with route configuration |
| OpenAPI input | Good fit; plugin configuration can point to an OpenAPI URL and can handle multiple sources |
| Developer UX | Strong candidate for a polished embedded reference and API client experience |
| GPUaaS playground | Still needs GPUaaS-owned environment, credential, tenant/project, idempotency, rate-limit, and audit controls |
| AsyncAPI/events | Does not remove the need for an event-reference plan |
| Risk | Plugin configuration is marked WIP/beta in Scalar docs, so test against our exact Docusaurus/pnpm stack before adoption |
Evidence From Vendor/Open-Source References
- Scalar documents an API Reference plugin for Docusaurus.
- The Docusaurus integration shows installation through
@scalar/docusaurusand route/plugin configuration. - Scalar documents single and multiple API reference configuration.
- Scalar's GitHub README describes the project as open source with first-class OpenAPI/Swagger support and lists Docusaurus among integrations.
- Scalar configuration includes authentication-related options, custom fetch, slug customization, document selection callbacks, and MCP configuration.
Pilot Shape
Recommendation
Run Scalar and Stoplight pilots side by side before selecting the renderer:
- Add a non-production Scalar route after the current REST Reference Pilot proves the portal route shape.
- Feed it the synced REST contract or generated compatibility copy, not a hand-edited spec.
- Keep live calls mock-only or disabled until security review.
- Test Docusaurus 3.10.1, pnpm, TypeScript config, route generation, bundle size, and sidebar behavior.
- Evaluate auth/header/idempotency behavior against GPUaaS playground rules.
- Keep AsyncAPI/event rendering as a separate decision.
Comparison With Stoplight
| Question | Stoplight Elements | Scalar |
|---|---|---|
| Product familiarity | Strong; already in GPUaaS API/product workflow | Lower, but modern developer UX |
| Docusaurus route plugin | Embedding likely through React/Web Component | Dedicated Docusaurus plugin |
| Try It / client posture | Interactive API console | API client/playground posture appears stronger |
| Multiple references | Elements alone is narrower than full dev portal | Plugin supports multiple sources |
| Adoption risk | Familiar tool, but portal integration still needs pilot | Better Docusaurus fit, but beta/WIP plugin config needs validation |
External References
Canonical sources