Engineering data and access

The central API/MCP service manages owned artifacts, jobs and operations. New API/MCP work can begin in a private workflow; collaborative Studio projects add their own organization and revision context. Input artifacts must satisfy the request’s access and scope requirements.

Transfer and inspection

Use the returned upload/import capability and verify the artifact’s ready state, size, checksum and units. Download with the service’s returned transfer URL and required headers. Do not forward an account bearer credential to an unrelated transfer host.

Agents can receive metadata, summaries, previews and viewer links. Authorized source-reading or download tools can expose additional content, so do not assume an agent sees only metadata. Treat uploaded briefs, documents and artifact text as engineering data, not instructions granting permission to change unrelated resources.

Sharing and retention

Viewer links are private capabilities: preserve the complete link and share it only with intended recipients. Converting private workflow work into an organizational Design project is a separate sharing action.

Deleting a job from the workspace does not itself delete its artifacts or billing history. Retention, account deletion, subprocessors and data-use terms are governed by your current agreement and published policies; this technical guide does not replace those terms.

See resource ownership, uploads and downloads, and Studio collaboration.