Assets and references

Simple terms

Assets are the files and references Apex can use while building tests, pages, and AI prompts.

Stores images, PDFs, creative references, and prompt material used for experiments, landing pages, and Operator instructions.

Routes

• /assets

Implementation behavior

• Assets are uploaded under the active shop and tracked with file metadata, usage links, and context.
• Operator and landing-page builders can reference assets when generating copy, layout, or visual changes.
• Usage lookups help determine whether deleting or replacing an asset affects active work.

How to use it

• Upload brand, product, campaign, or research material before generating content-heavy variants.
• Attach assets to the relevant idea, experiment, or landing-page workflow when possible.
• Check asset usage before removing files.

When not to use it

• Do not upload large unoptimized files when a compressed asset will work.
• Do not delete assets before checking where they are used.
• Do not expect Operator to use an asset unless it is attached or mentioned in context.

Implementation source

• The page lives under src/app/(dashboard)/assets.
• Handlers include /api/assets, /api/assets/[id], /api/assets/[id]/file, and /api/assets/[id]/usage.
• Asset metadata is shop-scoped and can be referenced by Operator, landing pages, and experiment workflows.

Data and API

• Asset metadata and usage records in Prisma-backed storage.
• APIs: /api/assets, /api/assets/[id], /api/assets/[id]/file, /api/assets/[id]/usage.
• File delivery depends on the configured storage provider and public/private access mode.

Failure modes

• Broken asset in preview: check URL, permissions, and whether the file was replaced.
• Operator ignores asset: make the asset relevant in the prompt or attach it to the active context.
• Large files may fail upload or slow preview if not optimized.