Add richer validation to your fields You use the fluent builder for limits, nested objects, arrays, optional fields, and richer descriptions. Validation becomes part of the program instead of cleanup after it. java academy academy/topics/fluent-fields-validation website/content-src/academy/course.mjs academy Add richer validation to your fields
Unit 2 · Make AI outputs predictable

Add richer validation to your fields

You use the fluent builder for limits, nested objects, arrays, optional fields, and richer descriptions. Validation becomes part of the program instead of cleanup after it.

f()8 focused minutesNot started
Unit example (nearest native match)

See the idea in context

var sig = Ax.s("email:string -> priority:class \"high, normal, low\"");
  1. Reject empty input

    min(1) makes the text requirement executable.

  2. Bound the score

    The output must stay between zero and one.

  3. Build one signature

    build() finishes the reusable input and output contract.

Run itIn your own project
// Gradle (build.gradle):
implementation 'dev.axllm:ax:22.0.4'
// Maven (pom.xml):
<dependency>
  <groupId>dev.axllm</groupId>
  <artifactId>ax</artifactId>
  <version>22.0.4</version>
</dependency>

import dev.axllm.ax.Ax;

var llm = Ax.ai("openai", Map.of("apiKey", System.getenv("OPENAI_API_KEY")));
var classify = Ax.ax("review:string -> sentiment:class \"positive, negative, neutral\"");

Set OPENAI_APIKEY in your environment before running provider-backed code.

In the ax repo

From a clone of the ax repo:

npm run example -- java src/examples/java/generation/StructuredGenerationExample.java
Active practice

Show that you can use it

Answer 2 in a row to learn this · attempt 1
Keep exploring

Source-backed follow-up