Assets

Import raw bytes as a typed Asset

Byte→typed-Asset rich ingress (Phase 3 of unified-memory-media-substrate.md). The raw binary request body plus its declared Content-Type becomes a typed base Asset (recorded through the sole writer AssetStore.create with a <media>_import verb and an empty derivedFrom, so it is non-replayable by construction), and every decodable Apple-capture side-channel (depth, gain map, ProRAW develop, per-eye spatial views) is preserved as a sibling Asset derivedFrom the base. This is the body-bearing twin of the path-bearing image_import MCP verb; both feed one AssetImportCore, and both return the SAME WireAssetImportResponse envelope: the base Asset, its siblings, and any portable recipe or third-party workflow document embedded in the file.

post/v1/assets/import

Request

  • Base URL: http://localhost:9998
  • URL: http://localhost:9998/v1/assets/import
  • Auth: HTTP bearer

Response

The import envelope — base Asset, side-channel siblings, and anything the file carried

embeddedWorkflowstring nullable

A structured workflow document another tool embedded, as RAW text — deliberately untyped, because reconstruction is the chat agent reading intent, never a foreign-format parser. Absent when the file carries a Piper recipe of its own.

Changes

No recorded changes to this operation across all 1 revision of this API.