get items
Everything known about up to 25 items: url, description, tags, fields, starred and hidden state, comments, provenance, lineage, group, technical data, and understanding (which reads each item has stored; understanding.next names each missing read’s tool, cost and refs, beside the cloud processing left). A ref nothing answers to comes back in unresolved, refs past 25 in truncated, and a part that could not be read in degraded; none of the three fails the call. Free.
Authorizations
An API key (es_live_…) from Settings, under API keys, or an OAuth access token.
Headers
Retry a paid dispatch safely: the same key returns the job already dispatched instead of charging again.
The workspace this one call acts in, when it is not the default: for a key or a connected agent, one of the workspaces the user allowed it.
Body
25 a time; the rest come back named in truncated.
1An item ref, item id, or the job id that made it.
Only these parts, each one a read of its own. All of them by default.
labels, lineage, comments, group, understanding concise is the item alone: what it is, its file, technical, description, tags and fields. detailed (the default) adds every part around it.
concise, detailed 
