TypeSafe AI

name identifies an endpoint; it is not sent to the model. Producers and predicates using the same URI share its client and configuration. Each endpoint owns one HTTP client, connection pool, and default executor. Reuse the same endpoint URI when its configuration is shared. Camel manages its lifecycle and cancels in-flight requests on stop. Java 21 and later also close the HTTP client explicitly; on Java 17, the JDK reclaims its remaining resources after it becomes unreachable.

Camel components are configured on two separate levels:

The TypeSafe AI component supports the following options which are listed below.

The TypeSafe AI endpoint is configured using URI syntax:

With the following path and query parameters:

Configure credentials through property placeholders or a supported vault:

apiKey is a secret option. baseUrl defaults to https://api.typesafe.ai; the client appends /v1/systemone. A base path can address a proxy. HTTP redirects are not followed. Use HTTPS for the service; HTTP is useful for local testing.

model defaults to jev-latest. Pin a version when tuning thresholds; aliases can change behavior without a route change. The request map may explicitly override the endpoint’s model for that request. The response’s model identifies the model that answered. See available models.

For a fixed set of questions, select state and retain the business message using properties:

No manually registered beans are needed. state is a Simple expression, defaulting to ${body}. For an InputStream, use ${bodyAs(String)}. Only the selected state is sent. Without resultProperty, the response replaces the message body.

Without configured questions, the input body must be a Map<String, Object> with state and a nonempty questions map. An optional model overrides the endpoint default. Each named question is a map with type (noul, choice, or score), optional instructions, and the applicable criteria. Instructions may be omitted or null. Noul criteria and either yes/no description may also be omitted or null, matching the official Python SDK and OpenAPI schema. State, instructions, and descriptions can be text or structured maps/lists. Nested content supports strings, finite numbers, booleans, nulls, lists, and maps with string keys. Convert other objects explicitly before submitting them. The component does not collect exchange headers or properties automatically. Do not send an entire exchange as state.

The output is an org.apache.camel.util.json.JsonObject, which implements Map<String, Object>. It preserves the API’s JSON structure, including additional fields. Nested objects are maps, arrays are lists, and numeric values implement Number; use doubleValue() or longValue() rather than assuming a specific numeric class.

Missing or mismatched answers, invalid numeric ranges, unknown choices, and incomplete probability maps fail the exchange. The selected Choice must have maximal probability; ties are allowed. Probabilities and scores are preserved as returned. Like the official Python SDK, the component does not enforce a probability-sum tolerance or recompute a Score from its returned probabilities, which may have been rounded independently.

Token counts may be missing or null. Missing values remain absent and null values remain null; neither is replaced with zero. Present counts must be nonnegative integers.

This mixed batch makes one HTTP request, with the same state for every question. There is no implicit batching across producer calls or predicates.

With resultProperty=evaluation, the producer stores the response in that exchange property and preserves the input body. It clears the property before each evaluation so failures cannot leave a stale result. The input request map is not mutated.

For category routing, submit one Choice question and route on its choice field. Independent Noul conditions instead preserve Camel Choice’s first-matching-branch semantics.

Producer and language evaluations are synchronous. Each evaluation blocks the calling thread for a remote round trip and may incur token charges. There is no response cache or automatic retry. Loops and Camel redelivery can evaluate again; bound them and account for repeated calls.

requestTimeout bounds the HTTP request and complete response body. Connection, request and overall deadline failures all surface as java.util.concurrent.TimeoutException; an underlying JDK HTTP timeout is retained as the cause. Interruption and timeout cancel the HTTP future, including stalled response bodies. Cancellation cannot guarantee the service stopped processing or consumed no tokens.

An unsuccessful HTTP status raises TypeSafeAiHttpException with status code, request ID and Retry-After where available. Error bodies are omitted because they may contain submitted state. Invalid responses and network failures propagate. Language evaluations preserve the exception in Camel’s cause chain, so ordinary onException clauses can handle it. Failures never silently become a non-match. Endpoint stop cancels in-flight calls and rejects new evaluations until restart.

Only submit data permitted for the configured service. Test model decisions and thresholds against your application; structured output does not establish correctness.