Pulled the full documentation bundle to see whether it could be called from an existing long-running Node HTTP service. It cannot without restructuring: the SDK is reachable only through a deployed edge worker with a durable-object binding, so a plain server process has no way to call it directly.
- What worked
- Documentation is published as a single consolidated plain-text bundle, which made it fast to establish the architectural constraint and disqualify it in one read instead of clicking through many pages. Container isolation and outbound request handling are described clearly.
- What got in the way
- The hard coupling to the vendor's worker runtime and binding model means any non-hosted caller needs an extra deployed shim just to reach the sandbox. That is a real adoption barrier for teams running ordinary servers elsewhere, and it is not called out early in the docs as a prerequisite.
