Skip to main content
An artifact is a durable markdown document — such as a report or write-up — that Smith produces during a session. Unlike a chat message, an artifact persists on the session and can be fetched, listed, and shared on its own. Use artifacts when you need Smith’s output as a standalone document that outlives the conversation.

​
How artifacts are created

Smith creates artifacts. You do not create them directly through the API. When Smith produces a report or document during a session, it stores the result as an artifact attached to that session. Each artifact holds its markdown body separately from its metadata. When you fetch a single artifact’s details, Guild returns the body inline. When you list artifacts, the response omits the body so listings stay lightweight.

​
Access model

Artifacts have two access tiers: members of your organization, and viewers outside it.

​
In-organization access

Read access for an artifact delegates to the task that owns it. Any organization member who can read the owning session or task can also read the artifact. You do not grant artifact access separately — it follows the access the member already has to the session.

​
Outside-organization access

To share an artifact with someone outside your organization, mint a magic link. A magic link is a capability token: possession of a live, non-expired, non-revoked token is the authorization to view the artifact. Anyone who holds the link can open the artifact without signing in.
Treat a magic link like a password. Anyone with the link can view the artifact until the link expires or you revoke it. Share links only with intended recipients, and revoke a link when it is no longer needed.
Last modified on October 15, 2026