Observation
An observation is one product signal: title, description, and user_sentiment. Create one or more per call viapost_observations (MCP) or the REST API for custom integrations.
Each observation belongs to a project and is keyed by user_id and interaction_id — your strings for the end user and conversation thread, not Correl8 accounts.
Issue
An issue groups related observations into a digest. Issue digest runs asynchronously after observations are created.Tags
Tags are matched server-side from observation content, asynchronously alongside issue digest. Track progress viaprocessing_status.
Sentiment
Every observation requiresuser_sentiment — a five-level label from very negative to very positive. See User sentiment for the scale.
Processing status
On create,processing_status is pending. Tag matching and issue digest run asynchronously; when complete, tags appear and the observation may link to an issue.
If your workspace exceeds the free-tier limit (1,000 processed observations per month), Correl8 keeps ingesting but does not process — status becomes billing_blocked until the period resets or you upgrade.
MCP vs REST
| MCP (default) | REST API | |
|---|---|---|
| Who posts | Your agent | Custom integration |
| Scope | Write-only (post_observations, one or more observations per call) | Same batch payload |