Skip to main content

OpenAPI Design Center

/openapi-designer routes to OpenAPIDesignCenter, the consolidated spec studio.

Core Views​

The studio supports a multi-view flow (home, build, code, preview, data, generator, split) so teams can move from design to runtime without context-switching.

Production Behaviors​

  • Load existing specs from typed ThorAPI services
  • Create/update specs in-app (no manual file surgery required)
  • Import files through POST /v1/openapi/import
  • Edit OpenAPI components (schemas, responses, parameters, request bodies, security, etc.)
  • Persist local studio session state (active view, selected spec, component tab, editor format)
  • Convert between YAML and JSON
  • Detect inline object-schema hotspots before they become generation pain

Agent + App Bootstrap from Spec​

The studio includes an agent/application wizard path that can:

  • create application records
  • create agent records
  • bind them to a selected spec
  • set heartbeat and autonomy settings for schema/table generation workflows

Why This Matters​

OpenAPI design is no longer separate from operations. In production, the same surface supports:

  • design fidelity
  • generation readiness
  • agent bootstrapping
  • downstream workflow integration
  1. Import or create spec in /openapi-designer.
  2. Normalize core components and paths in Build view.
  3. Validate/edit in Code view (YAML or JSON).
  4. Review generated shape and metadata in Preview/Generator views.
  5. Launch an application/agent from the same context when needed.

Then continue in Workflow Studio to operationalize the new surface.