SDKs
Three official client libraries, one for each ecosystem we hear most often from customers building on Simulix. All three are generated by Stainless from the OpenAPI 3.1 spec so the SDK matches the API exactly — no hand-rolled drift, no two-source-of-truth bugs.
api.simulix.com/v1/* is the documented integration surface today — see Quickstart for the curl + raw-HTTP path. For early access notifications, drop a note at founders@simulix.com.The three targets
Idiomatic Python client with full type stubs (PEP 561). Pairs with the Camel-AI agent framework used in the platform itself.
Targets Python 3.10+. Published to PyPI as `simulix`.
Type-safe TypeScript / JavaScript client. Works in Node 20+, Bun, Deno, and Cloudflare Workers. Mirrors the OpenAPI 3.1 spec exactly.
Published to npm as `@simulix/sdk`.
Idiomatic Go client with context-aware request cancellation and structured error types. Pairs with the `errors.As` pattern.
Targets Go 1.22+. Published as `github.com/simulix/sdk-go`.
Why Stainless
Generated SDKs stay true to the API by construction. Every endpoint, every parameter, every error type comes from the OpenAPI 3.1 spec at api.simulix.com/v1/openapi.json. When a new endpoint ships, the SDK ships with it. There is no hand-authored client that can drift.
Stainless is also the SDK generator behind Anthropic, OpenAI, and Cloudflare's official clients — same generator, same idiomatic patterns, same retry + idempotency + polling helpers you'd expect from those.
Integration today
Until the SDKs publish, the REST API is the integration surface:
- Quickstart — get your first simulation back in five minutes with curl.
- API reference — full endpoint contract, request and response shapes, error codes.
- Idempotency — the SDK pattern you'd want, replicated by hand: send an
Idempotency-Keyon every POST. - Webhooks — verify signatures yourself with
HMAC-SHA256while the SDK is in flight.