Read Artifact tags
Scope-local labels follow logical identity without changing content revisions. Inactive manifest entries remain valid targets.
Authorization
BearerAuth Bearer credential resolved to an opaque authenticated Principal by the Server deployment.
In: header
Path Parameters
1 <= length <= 256All readable Artifact families support logical tags on persisted Artifacts.
Value in
- "memory"
- "atomic-memory"
- "experience"
- "skill"
- "handoff"
- "profile"
- "prompt"
- "topic-memory"
1 <= length <= 128Header Parameters
1 <= lengthResponse Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/v1/scopes/string/artifacts/memory/string/tags"{ "scope_id": "string", "target": { "type": "artifact", "family": "memory", "artifact_id": "string" }, "tags": [], "tag_digest": "string"}Replace the current Artifact head PUT
Commit a complete next revision when If-Match identifies the current head. Replacing a Prompt requires current scope.admin authority, including switching to Auto and restoring an earlier revision. Artifact ownership does not authorize Prompt replacement after Scope role revocation. Topic Memory replacement also requires scope.admin and preserves independently versioned tags. Complete title, summary, and detail text replaces the head without semantic generation. Profile replacement uses the same conditional write. To roll back Profile, Prompt, Experience, Skill, Handoff, or Topic Memory, set restored_from_revision and reason. The server checks that the submitted canonical content matches that revision and differs from the current head, then commits a new revision. Atomic Memory replacement rejects both fields; restore Atomic Memory through its restoration flow.
Replace Artifact tags PUT
Scope-local labels follow logical identity without changing content revisions. Inactive manifest entries remain valid targets.

