Errors - Agnost AI

Most Agnost API errors return a JSON body with an error string:

{
  "error": "Invalid request body"
}

Common errors

Symptom	Likely cause	Fix
No events appear	Wrong org ID or endpoint	Confirm org ID in Settings -> Organization and use `https://api.agnost.ai` or `https://otel.agnost.ai/v1/traces`.
401/403 on dashboard API	Missing JWT/API key or wrong org scope	Use `Authorization: Bearer <jwt>` or `x-api-key` plus the right `x-org-id`.
400 on ingestion	Missing required field or invalid UUID	Validate `session_id`, `event_id`, and `user_data.user_id`.
OTel traces missing	Header not attached or exporter endpoint is wrong	Set `OTEL_EXPORTER_OTLP_HEADERS=X-Agnost-Org-ID=<your-org-id>` and use `/v1/traces` when the SDK expects a trace URL.
Tool inputs missing	Input capture disabled or framework did not export content	Check SDK config and framework telemetry settings.

Send one test event.
Open Raw logs in the Agnost dashboard.
Confirm the event has the expected org ID, user ID, session/conversation ID, and agent/tool name.
Check Tools or Conversations depending on the integration.
If using OpenTelemetry, confirm your app can reach otel.agnost.ai.