Skip to main content
This guide takes a product server from zero to one Sikaru-managed agent run. The example defines a support agent with a local CRM tool, sends a user request, and records the completed Experience so Sikaru can learn from production outcomes, failures, feedback, and eval evidence over time.

Prerequisites

  • A Sikaru project.
  • A project-scoped API key stored on your server.
  • Python 3.10+ or Node.js 18+.
Do not expose SIKARU_API_KEY in browser bundles, mobile apps, or customer-controlled code.

1. Install the SDK

2. Configure the server environment

Optional override for non-production environments:

3. Create a project client

4. Declare a product-owned tool

Local tools run in your process. Sikaru sees the declared capability name and the returned result, not your internal credentials.

5. Run the agent

respond(...) starts a managed run, streams events back to the SDK, executes local tools when requested, records the final experience, and returns the final output.

What happens next

After the first run, Sikaru has a managed run record and a captured Experience. As you add more traces, feedback, corrections, and eval rubrics, Sikaru can identify recurring misses and propose reviewed improvements.

Stream and resume runs

Use lower-level run control when your app needs event-by-event rendering or recovery.

Record your own executions

Use Experience when your product already ran the agent behavior itself.