Skip to main content

​
How it works

After each agent job completes, your code sends a POST request to Muster with the results. That’s it. 
Your agent finishes a job
        ↓
POST /api/v1/jobs/{job_id}/quality   ← plain HTTPS, no auth
        ↓
Muster stores the signal
        ↓
Dashboard updates in real time
No SDK to install. No new dependencies for your security team to audit. No secrets to manage.

​
The one endpoint

POST https://app.getmuster.io/api/v1/jobs/{job_id}/quality
Content-Type: application/json

{
  "agent_id": "your-agent-name",
  "job_id": "unique-job-id",
  "overall_passed": true,
  "token_input": 1247,
  "token_output": 312,
  "model": "gpt-4o",
  "latency_ms": 1840,
  "checks": [
    {
      "check_id": "output_not_empty",
      "severity": "HIGH",
      "passed": true
    }
  ]
}
The quality endpoint requires no authentication. This is intentional — agents should never need to manage API keys or tokens. Rate limit: 1,000 requests/minute per agent.

​
Integration options

Python snippet

5-line fire-and-forget pattern. No pip required.

HTTP webhook

For n8n, Flowise, Dify — any tool with an HTTP node.

muster-sdk (optional)

pip package for convenience. Not required.

cURL / any language

Works from bash, Node.js, Java, Go — anywhere.

​
Security considerations

  • No inbound access required — agents only make outbound HTTPS calls
  • No SDK dependency — nothing to audit, nothing to patch
  • No secrets in agent code — the quality endpoint is public
  • Air-gapped option — deploy Muster inside your own network for zero external calls