Placid integration
Placid creative automation API: render a designed template into an image, a multi page PDF or a short video by overriding its named layers with text, pictures and QR codes, follow the generation until it is finished, merge PDFs, deliver the result straight to object storage, and manage the templates of the account. Rendering is queued by default, an item starting as queued and becoming finished or error. Requests authenticate with a bearer token.
Say what should happen.
The workflow builds itself.
Common Placid use cases
- organising templates with tags
- cleaning up documents after delivery
- cleaning up videos after publication
- producing a designed one page report
- waiting for a video before publishing it
- removing a template that is no longer used
- discovering which layers a template exposes
- binding several rendered pages into one file
- provisioning a template variant per customer
- waiting for a queued image before posting it
What you can do with Placid
Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.
Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.
Template, 5 operations
create_templateCreate templatePOSTCreates a Placid template or duplicates an existing one.delete_templateDelete templateDELETEDeletes a Placid template.get_templateGet templateGETReads one Placid template and the layers it exposes.list_templatesList templatesGETLists Placid templates with optional collection, name and tag filters.update_templateUpdate templatePATCHUpdates the title, tags or stored data of a Placid template.
Pdf, 4 operations
create_pdfCreate pdfPOSTRenders a Placid PDF whose pages each come from a template.delete_pdfDelete pdfDELETEDeletes a rendered Placid PDF.get_pdfGet pdfGETChecks whether a Placid PDF is rendered and reads its link.merge_pdfsMerge pdfsPOSTMerges PDFs into one Placid document.
Image, 3 operations
create_imageCreate imagePOSTRenders a Placid template into an image with the layers you override.delete_imageDelete imageDELETEDeletes a rendered Placid image.get_imageGet imageGETChecks whether a Placid image is rendered and reads its link.
Video, 3 operations
create_videoCreate videoPOSTRenders a Placid video from a sequence of template based clips.delete_videoDelete videoDELETEDeletes a rendered Placid video.get_videoGet videoGETChecks whether a Placid video is rendered and reads its link.
Use Placid from Claude Code, Cursor or Codex
Connect Placid in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Placid operations become tools the client can call, next to every other integration you connected.
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"
[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"{
"mcpServers": {
"livecontext": {
"type": "http",
"url": "https://livecontext.ai/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}How to connect Placid
- Create your workspace
Sign up free. Nothing to install.
- Connect Placid once
Add your Placid connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
- Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.
Placid integration FAQ
What can you do with the Placid integration?
LiveContext exposes 15 operations on Placid, covering template, pdf, image and video. Common uses include organising templates with tags, cleaning up documents after delivery and cleaning up videos after publication.
