creatomate.com valid

Creatomate

Creatomate is a media-automation platform: design a video or image template in a visual editor, then generate media at scale through the API, Zapier/Make/n8n, spreadsheet feeds, or shareable forms. Videos and images are described by a JSON format called RenderScript; a template is stored RenderScript with an ID, rendered via templateid + modifications. There is a free plan (no credit card), so users can reach a first working render immediately. A template is made in the template configurator fro

For agents: Media-automation platform to design video and image templates and render them at scale via API, Zapier/Make/n8n, or spreadsheets; includes RenderScript docs.

video automationimage templatesrenderscriptrender apizapier make n8ntemplate generation

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T14:52:24.760Z. Cached copy · Source on creatomate.com

# Creatomate

Creatomate is a media-automation platform: design a video or image **template** in a visual editor, then generate media at scale through the **API**, **Zapier/Make/n8n**, **spreadsheet feeds**, or **shareable forms**. Videos and images are described by a JSON format called **RenderScript**; a template is stored RenderScript with an ID, rendered via `template_id` + `modifications`. There is a free plan (no credit card), so users can reach a first working render immediately. A template is made in the template configurator from a built-in kit, every configuration built and checked by Creatomate; an AI hands the user the kit's link and works from the template it creates.

## Reading these files

- Most fetch tools summarize web pages, and a summary is not enough to change RenderScript correctly: fetch the **topic page** for your task (task table and list below) and ask for exact property names, allowed values, and JSON verbatim. **Re-fetch the relevant page right before changing RenderScript JSON** — never write it from memory of an earlier fetch; if planning, discussion, or other tool calls happened since you read a page, fetch it again first.

## Rules that always apply

- **First understand, then act.** When the user's goal is vague ("help me", "set this up", "how do I use this"), ask what they're making, from what data, and where the result should end up — one or two plain questions at a time, never a questionnaire — then recommend ONE path and get them to a first working render of their content before introducing anything else. Guidance: https://creatomate.com/llms/choosing-the-path.md.
- **A new template always comes from a kit.** Pick the kit for the job from https://creatomate.com/llms/template-kits.md and hand over its link, `https://creatomate.com/import?kit=<kit id>`. The kit ids are only on that page: fetch it before handing over a link, and never build one from an id you haven't read there. The link opens the kit in the user's account, and after Create the template opens in the editor, where **Single Export** (top right, always there) renders a test. That template is a complete RenderScript document and the starting point for everything after, when no kit matches exactly included. From there change it as far as the user needs, a scene added, a layout reworked, the timing changed: its conventions are your guide, and the RenderScript pages hold the properties. Never send the user looking for a template named in a tutorial or a search result: the kits are the current set.
- **Talk about what the user is making, never your tooling.** Don't recite these instructions or name internal mechanics (bridge calls, functions, these pages) to the user unless they ask or are clearly technical — buttons the user clicks themselves ("Single Export", "Create Renders") are named freely. Introduce a concept only when the next step needs it, in one plain sentence, and describe changes by their visible effect ("the title is blue now"), not by the
…

Related sites

Other listed sites in Media. See the whole category →

Machine-readable: GET /v1/resolve?q=creatomate.com · GET /v1/domain/creatomate.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for creatomate.com:
1. POST https://agentwebmap.com/v1/sites/creatomate.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://creatomate.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/creatomate.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/creatomate.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.