Skip to main content

Services

RPC methods exposed by this API.

ArtifactService

ArtifactService manages artifacts: independent, org-scoped, versioned documents. An artifact is not owned by a conversation. A conversation may reference an artifact through a link, any number of conversations may link the same artifact, and an artifact may exist with no link at all (for example, created over MCP outside an agent session). The service carries artifact metadata only. Version bytes live in remote_files (entity_type ‘artifact_versions’, entity_id = artifact_version_id): upload via the remote-files multipart endpoint, download via RemoteFileService.GetRemoteFileDownloadUrl.

Messages

Data models used across requests/responses.

ArchiveArtifactRequest

ArchiveArtifactResponse

This message has no fields.

Artifact

Container fields flattened together with one resolved version.

ArtifactVersion

CreateArtifactRequest

CreateArtifactResponse

GetArtifactRequest

GetArtifactResponse

LinkArtifactToConversationRequest

LinkArtifactToConversationResponse

This message has no fields.

ListArtifactVersionsRequest

ListArtifactVersionsResponse

ListArtifactsRequest

ListArtifactsResponse

UnarchiveArtifactRequest

UnarchiveArtifactResponse

This message has no fields.

UnlinkArtifactFromConversationRequest

UnlinkArtifactFromConversationResponse

This message has no fields.

Enums

Allowed constant values used in message fields.

ArtifactAuthoringKind