zeromind.inspect
What worlds or assets found via zeromind.search say they are, from their metadata. Pass SEVERAL guids at once: a whole shortlist is one call, not five. It carries no content bytes; an asset's read is the command that starts reading its implementation in the engine's bash (zm ls-tree @<guid>, then zm grep / zm show / zm log), which is how you tell whether it does the job before you install it. AN ASSET answers with guid, name, assetType (plus type_guid when the type is somebody's own, which is the only way to name one), summary — what the thing is, in prose — description and readme, the author's own words and more of them than a search hit carries, tags, schema/provides_schema, about (what its own metadata says it HAS: the components a bundle spawns with, whether its rig is a humanoid one), the world it lives in with that world's title and licence, its owner (with owner_bot when that account is an agent's), counts of what other people did with it, votes, created/updated, and latest — the version an install pins, and the day it was written; issues when something stands open against it; and read, the zm command that starts reading its code. An asset with a preview image also answers with preview_description (what the preview shows, in words) and returns the thumbnail itself as an image block beside this JSON, at most 4 per call: images names the guid each image block belongs to, in order, and images_omitted names the guids left out and why. A WORLD answers with title, summary, description, owner, license, visibility, the branch a read resolves to and the others it has, counts, votes, dates, and published: what it publishes, in the order its own listing ranks it, each with its own summary. A field with nothing in it is absent rather than empty. results matches the guids by position; one that is private, deleted, or of the other scope is reported against that guid and does not fail the rest.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| guid | Yes | One guid, or several separated by commas ('a,b,c'), from search hits. Up to 100 per call. | |
| sort | No | view=published only: hot | top | popular | new. | |
| view | No | How much to return per guid. ASSETS: 'overview' (default) = everything that decides reuse, and 'detail' is the same answer; 'similar' = the assets nearest this one in the index, each projected as a search hit with its `similarity`, for when the hit was close but not right. WORLDS: 'overview' (default) = the world and what it publishes, in one call; 'summary' = the world alone, without its shelf; 'published' (alias 'contents') = just the listing, which is what `assetType`/`sort`/`limit` narrow. | |
| limit | No | How many entries per guid for the list-shaped views (world published, asset similar). Not a cap on how many guids you may pass — that is 100. | |
| scope | No | What these guids ARE: 'assets' (default) or 'worlds'. The same two values zeromind.search takes. | |
| assetType | No | view=published only: narrow a world's listing to one or more asset types. Builtin types by name, anything else by its type guid. |