API reference
Base URL: https://agentlasso.dev/api/v1 (self-hosted: your own origin + /api/v1).
Authentication
Every request carries your project's API key (from Settings), as either header:
Missing or invalid key: 401 with { "error": "…" }. All errors are JSON with an error message.
If a key leaks, replace it in Settings → Project → Regenerate. The old key stops working immediately, so update your agent, your CI secret and any scripts with the new one.
POST /telemetry
Send a production trace, as flat JSON or OpenTelemetry (OTLP/HTTP JSON), auto-detected, or up to 500 flat traces at once as { "traces": [...] } to import history. Fields, response and status codes: Send traces.
POST /eval-runs
Start a run over your golden tests: every test in the project, one suite, or either narrowed to some capabilities. You get back the test cases to send through your agent.
Request
The run remembers exactly which test cases it was created with; results are matched against those.
Response 201
checks is the normalized list of what will be graded (see Checks reference), including checks from reusable evaluators that apply to the test ("type": "llm_judge" with an evaluator: { id, name }). Use it to tell which test cases need the agent's reply and which only need its tool calls.
POST /eval-run-results
Report what your agent did for each test case. AgentLasso grades every check and returns the result. Results can be reported once per run.
Request
Response 200
ci_passis what your pipeline should act on: exit non-zero when it'sfalse.pass_rateis over graded test cases only. It'snull, andci_passisfalse, when nothing in the run had checks;ci_fail_reasonthen says so.judge_reasoningis a one-line summary of the checks.ai_judgeappears when the run has AI judge checks:{ "judged": 3, "of": 3 }, or{ "judged": 0, "not_graded_reason": "…" }when they couldn't run (for example, no key). Each judge check incheck_resultscarries its verdict'sdetail,evidenceandjudge_model. See AI judge checks.
A complete example script and GitHub Actions workflow: Run golden tests in CI.
POST /sync-cluster (self-hosting)
The background classification job. A scheduler calls it with a shared secret (Authorization: Bearer <LOVABLE_CRON_SECRET>), not a project key. See Self-hosting.