Skip to main content

​
How agent data gets into Muster

There are three integration paths. Most customers use OTel and platform connectors for full coverage from day one, then add the SDK to their most critical agents.

​
Layer 1 — OTel (primary for coded agents)

For any agent you can configure, OTel is the recommended path. Set three env vars and Muster receives traces, infers quality checks, and tracks costs automatically.
Muster’s check inference engine runs on every execution — it infers relevant checks from the agent name, output structure, historical patterns, and Claude Haiku fallback. No check code required. → Full OTel setup guide

​
Layer 2 — Platform connectors (for no-code tools)

For platforms where you can’t set env vars — visual workflow tools and managed AI services. Elitery deploys and manages all connectors. Same check inference engine applies.

​
Layer 3 — SDK (for critical agents)

The SDK adds precise, business-rule checks on top of OTel/connector coverage. Use it for agents where inferred checks aren’t enough — financial calculations, compliance decisions, external writes.
→ SDK integration guide

​
Check inference — how inferred signals work

When OTel or a connector submits an execution, Muster infers quality checks automatically in four layers:
  1. Name matching — agent name → check category (financial, legal, risk, support)
  2. Schema analysis — output field names → check types (numeric, decision, required fields)
  3. Historical patterns — after 50+ executions, distribution-based checks
  4. LLM fallback — Claude generates check suggestions from agent name + output structure
Inferred checks are good enough for monitoring and trend detection. For agents where you need exact validation with specific expected values — add the SDK.