Skip to main content
Docs

Search guides and API endpoints, for example “Idempotency-Key” or “submit job”.

    Concepts

    Artifacts

    Where results and uploaded files live, how to download single records, and how long they are kept.

    Updated October 1, 2026

    On this page

    An artifact is a stored file set with an id like art-…: a job's result zip, a workflow step's output, or a file you uploaded. Artifacts make up your library, which you can browse in the app or list with List your artifacts.

    Inside an artifact

    A result artifact is a zip with a manifest: its ports (named outputs, such as poses or structure, each with a data kind and format) and the records in each port (one file per molecule, pose, or table). Get an artifact returns the manifest.

    Download artifact zip or one record member gets the whole zip, or with ?record= a single record. Download single records where you can: they are faster and smaller.

    A job's status carries its result's result_artifact_id; a workflow run's artifacts are listed per step by List artifacts for a workflow run.

    Using an artifact as an input

    Anywhere a job payload or workflow input takes a file, you can pass an artifact instead of the file's contents:

    {"$artifact": {"id": "art-…", "port": "structure"}}

    That reuses earlier results without downloading and re-uploading them, and it is how you pass large files into a workflow run.

    Uploading files

    Upload a CogniChem-compatible library artifact accepts:

    • A single file: a protein structure (PDB), molecules (SDF or SMILES), or a kinetic mechanism (Cantera YAML or CHEMKIN). Set data_kind and data_format; the file's port is named for its kind (structure, molecules, mechanism).
    • A CogniChem result zip, for example one you downloaded earlier.

    Check your space first with Get artifact storage usage; an upload that doesn't fit is refused.

    Storage and retention

    Each plan has a storage quota and keeps artifacts for a set number of days; see Plans and limits. The clock starts when the job finishes (for a workflow's artifacts, when the run ends). Expired artifacts are deleted, so download anything you want to keep.

    When your storage is full, uploads are refused and workflow runs pause until you free space; delete artifacts you no longer need with Delete an artifact. Workflow estimates warn when you pass 80% of your quota.