You could always use LoopLlama with nothing but HTTP and a JSON library, and plenty of teams did. But hand-rolling requests, retries, and event parsing is exactly the kind of glue we built the product to eliminate. So today we're shipping first-party SDKs for TypeScript, Python, and Go.
Typed end to end#
Each SDK mirrors the API with real types: workflows, runs, steps, and events are all typed objects, not untyped dictionaries. Your editor autocompletes the fields, your compiler catches the typos, and the shape of a run is documented by the types themselves.
The fiddly parts, handled#
The SDKs cover the things everyone otherwise reimplements — idempotent submission with job IDs, polling helpers, and an async iterator over a run's event stream so you can write a simple for-loop instead of managing a connection. The REST API remains the source of truth and isn't going anywhere; the SDKs are just the most pleasant way to reach it. All three are open source and generated from the same API description, so they stay in lockstep as the API grows.