Experience is Sikaru’s agent trajectory abstraction. It captures the episode-level data that continual learning and agent eval systems need: messages, tool calls, tool results, telemetry events, outcomes, corrections, failures, and rewards.
Sikaru Experience is compatible with the broader agent trajectory ecosystem:
- Harbor ATIF trajectories can be uploaded to Sikaru.
- Sikaru trajectories can export to Harbor ATIF v1.7.
- OpenInference spans can be uploaded directly.
- OTLP resource spans can be normalized into the same trace stream.
- Native Sikaru Experience payloads, Harbor ATIF, and OpenInference-compatible traces all feed the same issue mining, eval seed, and improvement evidence loop.
Experience and traces write to POST /v1/trace-streams.
Why Experience matters
Managed agents improve when Sikaru can connect what happened to whether it was good. A single Experience can carry:
This is the evidence Sikaru uses to find repeated failures, select or create eval cases, and propose reviewed behavior updates.
Record a product-run experience
UseExperience when your product already executed the agent behavior itself.
- Python
- TypeScript
Add corrections and failures
Corrections and failures make the continual learning loop actionable. Use corrections when a user, operator, evaluator, or policy reviewer identifies the better behavior. Use failures when a run produced a known miss, exception, policy issue, timeout, or rejected answer.- Python
- TypeScript
Build a Sikaru trajectory from existing messages
Use this path when another agent framework already produced messages and tool calls.Upload OpenInference-compatible traces
OpenInference spans are useful for migrations, low-level instrumentation, and existing tracing pipelines.- Python
- TypeScript
- Python
- TypeScript
Upload OTLP and Harbor ATIF
The Python SDK has helpers for direct OpenTelemetry OTLP resource spans and Harbor ATIF trajectories.Metadata for evals and mining
Attach stable metadata that helps Sikaru group, search, and explain issues.Treat outcomes, corrections, and failures as product facts. Sikaru uses them as evidence for issue mining, eval seed selection, regression checks, and reviewed improvements.