metadata— a structured JSON object on the presentation, set through the API. Use it to attach whatever your workflow needs (client, stage, campaign, tags…) and build your own dashboard or card views on top of the API without waiting for Slideless to grow those fields.AGENT.md— a markdown briefing shipped inside the deck bundle, at its root. It travels with the content and is versioned with it: an agent can read what a deck is, what data it contains, and how to present it — before downloading or rendering anything.
Metadata
Any plain JSON object up to 16k serialized, opaque to the server. It comes back on every presentation read (get and list), so external dashboards can render cards from a singleGET /api/v1/presentations call.
Set it at creation (the upload-session commit accepts metadata) or later:
--set does exactly that for you). The same PATCH also
retitles a deck without pushing a new version: { "title": "New name" }.
MCP agents use slideless_update_presentation; the object is visible in
slideless_get_presentation and slideless_list_presentations.
AGENT.md
Put a file named exactlyAGENT.md (case-sensitive) at the root of your
bundle and push. The server detects it at commit and flags the deck
(hasAgentDoc on the presentation and on each version), so an agent knows
upfront whether a briefing exists without opening the manifest. A
downloads/ folder is flagged the same way (hasDownloads, see
Attachments): a deck that carries files should
say in its briefing what each file is and which page it belongs to, since the
files are handed out, never rendered.
Writing one is the deck creator’s responsibility. A good briefing tells
an agent what a human would need to know before presenting: what the deck
is, who it is for, what each page covers, where the data lives, what may be
edited and what must not.
Reading it back:
slideless_get_agent_doc. The dashboard shows the briefing
on the deck’s dashboard page (the Deck details panel, one click from the
deck’s own page), and slideless push prints a
reminder when a bundle ships none.
Because AGENT.md is an ordinary bundle file, every share link also serves
it publicly at /v/{secret}/AGENT.md — an agent handed only a viewer URL
can fetch the briefing directly. Do not put anything in it you would not
put in the deck itself.