Agents can now save the PDF an MCP render produces
render_markdown and render_template now return a short-lived download URL an agent can curl to disk, plus a get_render_download_url tool that re-issues one for any render you own.
Rendering a PDF over MCP and saving it to disk used to be two different
things. render_markdown and render_template returned the bytes only as an
embedded base64 resource, which MCP clients keep out of the model's context —
so an agent that had just rendered (and paid for) a PDF still could not write
the file, and a model sometimes recreated a fake one instead.
Both billed render tools now return a downloadUrl: a signed link that
downloads the PDF with no credential of its own. Saving the render is a plain
curl -o document.pdf '<url>' in the agent's shell, and the result also
carries a resource_link so clients that support the MCP attachment spec can
offer it directly. The embedded blob is still there for clients that show
attachments.
The URL is deliberately short-lived — 15 minutes — because these links end up
in chat transcripts, shared conversations, shell history and provider logs.
Access itself is not time-limited: the new free get_render_download_url tool
mints a fresh link for any render artifact you own until its normal 7-day
retention expires.
Nothing changes for REST or CLI callers. GET /api/v1/artifacts/:id/pdf with
an API key behaves exactly as before; the signed-token path is simply a third
way in, scoped to one artifact and one file.