AgentForge4j API Surfaces (latest stable, 0.1.0)

The API reference is split into three independently-generated surfaces, stitched here:

• Core API (aggregate) — the named modules that export public API.
• MCP integration — agentforge4j-mcp (classpath-mode module).
• Spring Boot starter — agentforge4j-spring-boot-starter (classpath-mode module).

Why the split

Most of the framework is built as named JPMS modules and is documented together in the aggregate. Two public modules — agentforge4j-mcp and agentforge4j-spring-boot-starter — are intentionally unnamed (no module descriptor), so Javadoc cannot place them in the same modular aggregate; they are documented separately and linked above. This is a documentation-generation constraint only; it changes nothing about the modules at runtime.

Provider modules that only register a service-provider implementation and export no package (for example the OpenAI, Claude, and Bedrock providers) carry no public API, so they are intentionally absent from the aggregate — the surface is complete by design.

Modules in the aggregate

• agentforge4j.bootstrap
• agentforge4j.config.loader
• agentforge4j.core
• agentforge4j.llm
• agentforge4j.llm.api
• agentforge4j.llm.fake
• agentforge4j.runtime
• agentforge4j.schema
• agentforge4j.testkit
• agentforge4j.tools.http
• agentforge4j.util