The TypeSafeClient that calls the TypeSafe API over HTTP: DefaultTypeSafeClient and its Builder, plus the HttpTransport SPI it sends through. Depends only on typesafe-java-client and typesafe-java-codec; needs one transport (typesafe-java-client-http-jdk or -okhttp) and one codec (typesafe-java-codec-jackson2 or -jackson3) at run time, discovered via ServiceLoader.

Artifacts using TypeSafe Client HTTP (3)
Sort by:Popular▼

HttpTransport SPI implementation backed by java.net.http. Depends only on typesafe-java-client-http; discovered via ServiceLoader.
Last Release on Oct 6, 2026
HttpTransport SPI implementation backed by OkHttp. Depends only on typesafe-java-client-http (plus OkHttp itself); discovered via ServiceLoader.
Last Release on Oct 6, 2026
A TypeSafeClient that evaluates in-process on ONNX Runtime instead of calling the TypeSafe API: Laya (a ModernBERT decision model), Clef-flash (Qwen3.5-9B + joint schema head) or Qwen2.5 (next-token logits), read from a local model ...
Last Release on Oct 6, 2026
  • Prev
  • 1
  • Next