Question 1

Should I even bother with this package, or is it deprecated?

Accepted Answer

Effectively superseded. The README says do not start new projects with typesafe_sdk and that 0.4.1 is the final release of this package line. New development is directed at system_one_sdk, which carries the semantic question API, prepared evaluations, typed answers, batching, telemetry, runtime controls, OTP integration, testing support, and decision tooling developed here.

Question 2

Is system_one_sdk a drop-in rename, or a different shape?

Accepted Answer

Not a rename. Functionality is split by responsibility: system_one_sdk owns the provider-neutral System One programming model and the higher-level Elixir/BEAM APIs, while typesafe_api_sdk owns TypeSafe authentication, endpoint and model configuration, generated wire operations, and TypeSafe response handling. system_one_sdk ships a built-in TypeSafe provider so app code need not assemble the layers by hand.

Question 3

If I am already on 0.4.1, do I get cut off, and what happens to the code I wrote?

Accepted Answer

No. 0.4.1 remains available as the final release for existing users; only new development moved. The repository also keeps historical implementation details, guides, examples, and release history in place for reference, which is what makes the migration to the successor possible. This project is MIT-licensed.

Question 4

Is the successor really provider-neutral, or is it renamed TypeSafe code?

Accepted Answer

The successor is described as provider-neutral, and the split is the evidence: all TypeSafe-specific concerns — auth, endpoints, model configuration, generated wire operations, response handling — live in typesafe_api_sdk behind that abstraction. Which other providers system_one_sdk actually supports is not documented in this README; you would have to read that repository to find out.

Question 5

What are the two successor packages, and what owns what?

Accepted Answer

The functionality is split by responsibility: system_one_sdk is the provider-neutral application SDK and programming model, while typesafe_api_sdk owns TypeSafe authentication, endpoint and model configuration, generated wire operations and response handling. system_one_sdk has a built-in TypeSafe provider backed by typesafe_api_sdk.

Question 6

What is the current release of the successor package?

Accepted Answer

system_one_sdk's current release is 0.5.0, while TypeSafeSDK 0.4.1 is the final release of this package line. The README says not to start new projects with typesafe_sdk.

Question 7

Is this an Elixir and BEAM library?

Accepted Answer

Yes. It is an Elixir SDK, and system_one_sdk owns the higher-level Elixir and BEAM APIs and the provider-neutral System One programming model that the README points existing users to for migration.

TypeSafeSDK

About this project

Highlights

Questions about this entry

Reactions & coverage

From the Jev guides

From the Jev AI model community