Request
Workspace/tenant identifier. All data is scoped to this workspace.
User or agent who created this artifact.
One of:
chat_turn, tool_call, tool_result, document, note, meeting_transcript, email, calendar_event, attachmentThe artifact content. Stored as-is — no rewriting or summarizing.
ISO 8601 datetime. When the artifact was created. Defaults to current time.
Access control for this artifact.
Prevents duplicate ingestion. Same key + workspace = same artifact returned.
Session grouping identifier.
Thread grouping identifier.
Response
UUID of the stored artifact.
SHA-256 hash of the raw payload.
Whether text extraction, chunking, and embedding completed inline.
false when async indexing is enabled.Example
Response
Artifact Types
| Type | Description |
|---|---|
chat_turn | A single conversation message (user or assistant) |
tool_call | An agent’s invocation of an external tool |
tool_result | The result returned by a tool |
document | A document (policy, runbook, report, etc.) |
note | A free-form note |
meeting_transcript | Meeting transcript or summary |
email | An email message |
calendar_event | A calendar entry |
attachment | A file attachment (binary content via blob_pointer) |
Notes
- Artifacts are immutable — once ingested, they cannot be modified. Use feedback to flag artifacts as wrong or outdated.
- The raw payload is stored losslessly with a SHA-256 content hash for verification.
- When
ASYNC_INDEXING=true, indexing (text extraction, chunking, embedding) happens in a background worker. Use artifact status to check progress.