The new OpenAPI live docs need no extra build-time tooling — start Langhuan and you can read the interface contract, auth method, and request examples. Developers can understand resource boundaries in the browser first, then carry the same contract back into their own code.
Start integration from the contract
The Scalar browser shows the OpenAPI doc generated by the real runtime, avoiding “docs say one thing, the API does another.” The doc includes:
- request and response structures for resources like workspace, knowledge base, document, and job;
- Bearer auth examples and call entry points that correspond to the API Keys page;
- parameter notes for core flows like document ingestion, status queries, retrieval, and deletion;
- error responses and workspace-isolation constraints, reducing the risk of treating implementation details as a public contract.
Management capability takes shape
This phase also rounds out more management APIs, converges the externally exposed surface, and unifies document status, deletion behavior, and resource isolation behind the same HTTP boundary. The API Keys page can now jump straight to the live docs, so a first integration doesn’t require hunting through the repo for an entry point.
An entry point for automated clients
The REST API suits scripts, background services, and admin consoles; MCP over HTTP continues to offer the same set of knowledge-base capabilities aimed at tool calls. The two share the workspace contract, making it easy to graduate an exploratory request into a stable automated flow.