Jakarta Agentic Artificial Intelligence

<p dir="ltr">The Jakarta Agentic AI project provides a set of <strong>vendor-neutral APIs</strong> that make it <strong>easy and reliable to build, deploy, and run AI agents</strong> on <strong>Jakarta EE runtimes</strong>.&nbsp;</p><p dir="ltr">The Jakarta Agentic AI project:</p><ul><li dir="ltr">Defines common usage patterns and life cycles for AI agents running on Jakarta EE runtimes.</li><li dir="ltr">The API provides a very minimal facade to access more foundational AI capabilities, such as LLMs, without attempting to standardize LLMs. Instead, the API will provide easy, pluggable, and configurable access to existing LLM APIs such as LangChain4j and Spring AI. This API can be created similarly to how Jakarta Persistence provides access to underlying non-standard APIs by unwrapping.</li><li dir="ltr">The API will likely include a mechanism to define agent workflows. This will be done using a fluent Java API (as opposed to XML). The agent workflow will likely be dynamic at runtime rather than strictly defined and static at deployment time. A pluggability mechanism may be provided for YAML and XML.</li><li dir="ltr">The project will aim to utilize Jakarta Config if possible. It may allow implementations to utilize MicroProfile Config.</li><li dir="ltr">The project will not initially seek inclusion into the Jakarta EE platform or any profile. Rather, the project will seek to provide a usable standalone API under the Jakarta EE umbrella that vendors may choose to adopt. In the future, it may make sense to define a Jakarta EE profile for AI in general to which this project could be added. Such a profile could conceivably also include separate specifications to attempt to standardize other important AI concepts such as LLMs and model augmentation/context servers.</li><li dir="ltr">Implementations may provide integrations with OpenTelemetry.</li><li dir="ltr">The project makes a reasonable effort to keep the API potentially usable in runtimes such as Quarkus, Micronaut, and Spring Boot though Jakarta EE compatible runtimes are the clear primary target.</li></ul>