Embabel
Spring-Boot-based JVM agent framework (Kotlin, first-class Java interop) by Spring crea…
Spring-Boot-based JVM agent framework (Kotlin, first-class Java interop) by Spring creator Rod Johnson, using Goal-Oriented Action Planning (GOAP) from game AI for agent planning. ~3K+ GitHub stars in its first year, created by Rod Johnson (Spring founder); a credible enterprise-JVM agent platform with a distinctive planning model. SDK ad
Roadmap
Status
SDK / Library
Pattern
JVM (Java / Kotlin)
Runtime
Not yet published
SDK version
Readiness
What “Roadmap” means for Embabel
On the integration roadmap. The platform-side spine for this framework's pattern is already shipped — what remains is the per-framework adapter. Selecting it in the dashboard opens the “Get notified” path rather than creating an actor.
How it attaches
SDK / Library.
Install the io.entpoind:actor-embabel package and call witness.attach() once during agent initialisation.
Install the Trustvice adapter package from npm, PyPI, or cargo and call witness.attach(agent) in your application.
- 1
Install the adapter
Add io.entpoind:actor-embabel to your project from the relevant registry. Use the install command your runtime expects.
- 2
Issue a workspace API key
Generate a twk_-prefixed key in the dashboard under Settings → API Keys, scoped to the workspace and environment this agent's data should land in.
- 3
Attach the witness
Call witness.attach(agent) once when you initialise your Embabel agent. The adapter registers the framework callbacks, handles retries, and performs the workspace handshake.
- 4
Verify
Trigger one agent run. The dashboard's Witness page shows the canonical record within ~1 second of the agent emitting it.
import { witness } from "io.entpoind:actor-embabel";
// Initialise your Embabel agent as usual, then attach the witness once.
witness.attach(agent, {
workspaceKey: process.env.TRUSTVICE_KEY,
});
await agent.run("Summarise yesterday's incidents");Embabel is on the roadmap. The steps above describe how the integration works on the SDK / Library pattern — whose platform-side spine is already shipped — but the Embabel-specific adapter isn't generally available yet. Tell us you're running it and we move it up the queue.
Coverage
Coverage pending.
The captured-event list is published once the Embabel adapter ships. Every adapter normalises into the same canonical Witness record, so the dashboard, queries, exports, and lens evaluations are identical regardless of which events a given runtime emits.
The full pattern guide
SDK / Library — end to end.
Every framework on this pattern shares the same platform-side spine, endpoints, and gotchas. The pattern guide covers them in full.
Read the SDK / Library guideNeed help landing Embabel?
Talk to the integration team.
We help you land the integration end to end — including the parts that live in your environment.
Request integration help
Trustvice 360Declare as regras. Deixe cada execução ser verificada.
Agentes, evidências, governação, comércio e divulgação estão no Trustvice 360. Registe-se grátis e abra todas as suítes a partir de um só painel.