SpaceXAI TypeScript SDK launches with typed Grok access
The official SpaceXAI TypeScript SDK adds typed Grok access, streamed output and schema validation while remaining experimental before version 1.0.
The SpaceXAI TypeScript SDK reached its initial public release on October 2, giving developers an official typed client for using Grok through the company’s API. Its GitHub release history records version 0.1.0 followed by versions 0.2.0 and 0.2.1 on the same date.
The project documentation labels the SDK experimental and warns that interfaces can change before version 1.0. That warning already has a concrete example. Version 0.2.0 renamed the client class from xAI to SpaceXAI and changed several response and streaming type names, requiring early adopters to update their code.
What the first releases cover
The initial release changelog covers streamed responses, structured output, function tools, image input, and image and video generation. Files, batch processing, speech and transcription are also included. Developers can listen for text, reasoning and tool call events, then retrieve the completed response.
The package has no runtime dependencies. Its package configuration requires Node.js 22.13 or later and uses ECMAScript modules, or ESM. Teams with older Node deployments or different module arrangements should check compatibility before adopting it.
Version 0.2.1 adds validation of completed JSON output through Standard Schema validators, including Zod, Valibot and ArkType. The helper returns the validator’s typed result. That gives application code a defined check between receiving generated data and passing it into the rest of a workflow.
Streaming adds a boundary to recovery
A new JSON stream event also exposes structured output as it arrives. Those partial values are not validated. They can help populate an interface while a response is being generated, but applications still need to validate the completed result before treating it as trusted data.
The SDK’s retry documentation describes an optional recovery setting for streamed response requests that fail before the model produces any output. It is disabled by default. Each retry creates a new response, and the failed attempt may still incur charges for input tokens.
Once output has begun, the SDK does not retry the failed stream. Applications therefore need a visible failure state for interrupted answers rather than assuming the client will finish every response. Teams should test both an immediate connection failure and a failure after text has appeared.
Keep secrets and version changes in view
The client implementation blocks browser and Worker use by default to reduce the risk of exposing secret API credentials. Keep those credentials on the server and pin an exact SDK version while the interface is evolving.
SDK upgrades also belong alongside model compatibility checks. ByteForward’s coverage of the Grok Transcribe retirement explains a separate API transition. For teams adopting this client, testing the requested model, validated output and interrupted streams together is a practical starting point.
Illustrative Python code photographed by Chris Ried on Unsplash, used under the Unsplash License. This is not a screenshot of the SpaceXAI SDK.
