JsonCut

One visual source.Every execution path.

Create in Studio, automate through the V2 API and let agents iterate through MCP without rebuilding the image or video in another format.

Upload once.Render without holding the request.

Large files and video rendering use explicit operations. The integration stays responsive while every result remains traceable.

curl -X POST \
  "https://api.jsoncut.com/api/v2/templates/$TEMPLATE_ID/renders" \
  -H "X-API-Key: $JSONCUT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "values": {
    "headline": "Launch day",
    "productImage": "jsoncut-media://media-42"
  },
  "format": "mp4"
}'
Rendering a template: the response is an operation you poll or receive by webhook. Open the API reference and playground
  1. Create or choose

    Use a project for flexible work or a versioned template for controlled inputs.

  2. Upload media

    Upload the file through the public media endpoint and reference the returned media record from the project or template.

  3. Start the operation

    Validate the request, submit the render and retain the returned operation ID.

  4. Receive the result

    Poll status or accept a webhook, then download the finished output from its signed URL.

Small requests.Real production files.

Images, video and audio are uploaded as scoped project media. Base64 remains available for small inline work, with clear limits and upload guidance when a payload grows too large.

Start with one real project.Then automate it.

Use the quickstart to authenticate, upload media and render an editable image or video source.