Store, retrieve, and list content-addressed assets. Assets are immutable, identified by the CAD3 hash of their metadata.
| Name: | asset |
| Class: | covia.adapter.AssetAdapter |
This adapter provides 5 MCP tool(s) for AI agent integration:
| Tool Name | Description |
|---|---|
| asset_list | List assets in your a/ namespace with pagination. Returns summary info (id, name, type, description) per asset. Use asset_get for full metadata. Filter by type for narrow searches (e.g. type='agent-definition'). |
| asset_pin | Snapshot any resolvable value into your a/ content-addressed store. Idempotent — same value produces the same hash. Use to freeze a venue op or workspace value at a specific version. Returns {path, hash} where path is your DID URL for the pinned asset. |
| asset_content | Retrieve the binary content payload of an asset by any resolvable address. Returned as hex-encoded Blob. Returns {truncated: true, size} if it exceeds maxSize (default 1MB). Use asset_get for metadata. Only assets stored with a content payload have content. |
| asset_store | Store an immutable content-addressed asset in your a/ namespace. The ID is the CAD3 hash — storing identical metadata twice returns the same ID (idempotent). Use for documents, definitions, or data needing a stable tamper-proof identity. For named operations callable via grid_run, prefer covia_write to o/<name> — simpler than store-then-pin. |
| asset_get | Read asset metadata from any resolvable address (a/<hash>, o/<name>, v/ops/..., DID URL). Returns {id, exists, value}. Use asset_content for the binary payload, or covia_read if you just want the raw value without asset semantics. |