Artifacts

The event log stays lightweight because it never embeds file bytes. Whenever media enters the conversation — an image you attach to an input, a PDF a tool produces, a chart the model generates — the bytes are stored as an artifact (art_…) and the event carries a media_ref block pointing at it:

{ "type": "media_ref", "artifact_id": "art_z3jehcyd5n6a2bfgik7mv4qtrw" }

In the dashboard, artifacts appear as downloadable attachment chips on the conversation timeline; rendering your own timeline means resolving each media_ref with the two endpoints on this page.

export BASE="$OMNARA_API/orgs/$ORG/projects/$PROJ"
export AGENT="agt_v4qtrwz3jehcyd5n6a2bfgik7m"

Get artifact metadata

Fetch the descriptor first when you need to decide how to render or whether to download:

curl "$BASE/agents/$AGENT/artifacts/art_z3jehcyd5n6a2bfgik7mv4qtrw" \
  -H "Authorization: Bearer $OMNARA_TOKEN"

{
  "id": "art_z3jehcyd5n6a2bfgik7mv4qtrw",
  "org_id": "org_k7mv4qtrwz3jehcyd5n6a2bfgi",
  "project_id": "proj_7mv4qtrwz3jehcyd5n6a2bfgik",
  "agent_id": "agt_v4qtrwz3jehcyd5n6a2bfgik7m",
  "content_type": "application/pdf",
  "filename": "eu-ai-act-summary.pdf",
  "digest": "sha256:9f2ab8…",
  "size_bytes": 482133,
  "created_at": "2026-08-03T19:15:40Z"
}

digest is a content hash — useful for caching and deduplication on your side: if you’ve already stored that digest, skip the download.

Full schema and playground: Get artifact.

Download the content

The content endpoint returns the raw bytes with the artifact’s content type:

curl -o eu-ai-act-summary.pdf \
  "$BASE/agents/$AGENT/artifacts/art_z3jehcyd5n6a2bfgik7mv4qtrw/content" \
  -H "Authorization: Bearer $OMNARA_TOKEN"

Content is immutable — the same artifact ID always yields the same bytes, so responses are safe to cache indefinitely.

Full schema and playground: Get artifact content.

Where artifacts come from

Source	What happens
Inline `media` block on an input	Persisted as an artifact; the stored event shows a `media_ref`.
Inline `media` block on a custom tool result	Same conversion — submission accepts bytes, the timeline stores a reference.
Built-in tools that fetch or produce files	The tool result references the artifact.
Model output with media	The `model_output` event references it.

There’s no endpoint to create an artifact directly — they exist only as a side effect of the conversation, which keeps every artifact traceable to the event that introduced it.

Streaming events

Where media_ref blocks appear in each event kind

Sending input

Attach files to your messages

Get started

Agents

Inputs & events

Tools

Machines

Organization

Integrations

Examples

Get artifact metadata

Download the content

Where artifacts come from

Next

Streaming events

Sending input

​Get artifact metadata

​Download the content

​Where artifacts come from

​Next

Streaming events

Sending input

Get artifact metadata

Download the content

Where artifacts come from

Next