# Contentdrips API and MCP vs Creatomate

> Creatomate scores 49.6 (D) to Contentdrips's 36.3 (F) for design templates. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/contentdrips-vs-creatomate
- Markdown: https://www.anchorterminal.com/compare/contentdrips-vs-creatomate.md (~4,900 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Creatomate scores 49.6 (D) on agent readiness against Contentdrips API and MCP's 36.3 (F), and leads in 6 of 7 scored categories. Contentdrips API and MCP leads on transparency & trust. Both do design templates.

- Contentdrips API and MCP: grade F, 36.3/100, rank #1390 of 1510. Markdown https://www.anchorterminal.com/tools/contentdrips.md · JSON https://www.anchorterminal.com/api/v1/tools/contentdrips.json
- Creatomate: grade D, 49.6/100, rank #1088 of 1510. Markdown https://www.anchorterminal.com/tools/creatomate.md · JSON https://www.anchorterminal.com/api/v1/tools/creatomate.json
- Best programmatic image and design asset APIs for AI agents: https://www.anchorterminal.com/best/design-assets/index.md
- All 153 assets comparisons: https://www.anchorterminal.com/compare/design-assets/index.md

## Which one, for what

### Contentdrips API and MCP (F)

Good for: Branded LinkedIn and Instagram carousels and graphics from saved templates, with drafting and publishing in the same server.

Ahead on:
- Transparency & trust, 60 against 52

Watch for: No status page, SLA, numeric rate limit or 429 documentation found

### Creatomate (D)

Good for: Teams that render video, images and GIFs from templates or JSON and want an agent to draft templates and start renders through MCP.

Ahead on:
- Reliability, 40 against 23
- Schema & documentation, 53 against 48
- Agent ergonomics, 67 against 54
- Security & auth, 48 against 31
- Payments & pricing, 35 against 25
- Maintenance & community, 54 against 15

Watch for: No status page, incident history or SLA found. `status.creatomate.com` does not resolve


## Why the edge

### Maintenance & community: Creatomate +39

- Contentdrips API and MCP (15): The newest dated change to the agent surface is the MCP page, published 25 May 2026 and modified 27 May, 163 days before this check (10). No three dated changes since 8 August were found (0). No public changelog. Email support at hello@contentdrips.com, which we didn't test (5 of 15). Not in the official MCP registry and no official SDKs (0). No public package or repository (0). 10 + 0 + 5 + 0 + 0 = 15.
- Creatomate (54): No changelog. Dated releases since 6 August are the n8n node 0.2.0 (11 August, per the 8 October npm reading), the rebuilt n8n node v1.0.0 (11 September) and v1.0.1 (19 September, a category metadata fix, half), and `@creatomate/preview` 1.6.1 (3 September, removing a dependency and type definitions from the build, half). The newest release that changes code is n8n v1.0.0, 54 days before the check (20). Three counted entries in 90 days (20, cause evidence; it drops to 0 after 9 November when 0.2.0 leaves the window). Support by email, no public changelog or forum found, and two open GitHub issues across the libraries per the 8 October check (5). The Node library was last tagged 1.2.1 on 23 September 2024 and calls `/v1`, the PHP library was last pushed on 21 October 2024, and the Preview SDK is current (7). No CI in the Node repository (2). 20+20+5+7+2 = 54.

### Reliability: Creatomate +17

- Contentdrips API and MCP (23): Hosted lines. No status page found on the site, the developer docs or the footers (0). No readable incident history (5). No rate limit is given in numbers, only monthly call allowances by plan (6,000 on Pro, 25,000 on Ultimate), which earn a little (5 of 15). The troubleshooting note says to check /queue/stats and retry after a short delay when rate limited, with no status code or Retry-After. Render jobs are asynchronous, so polling is safe (3 of 15). No SLA found (0). The MCP server is v1.0.0 and the render API is not labelled beta (10). 0 + 5 + 5 + 3 + 0 + 10 = 23.
- Creatomate (40): Hosted lines. No status page found. status.creatomate.com still has no DNS record and no page we read links to one (0). No readable incident history (5). 30 requests per 10 seconds per account, documented in the API reference for agents (15). The same page documents `X-RateLimit-*` headers on every response and `Retry-After` on 429 with "wait that long, do not retry immediately", but no idempotency key for renders, which are writes (10). The 8 October first-hand header reading came from a request to the product's API and is struck; the docs carry the same facts. No SLA found (0). The REST API and MCP server carry no beta label (10). 0+5+15+10+0+10 = 40.

### Security & auth: Creatomate +17

- Contentdrips API and MCP (31): API keys from the dashboard, with no scopes, expiry or rotation documented. The MCP server also runs OAuth 2.0 with PKCE and dynamic client registration, but its one `mcp` scope authorises the same full key (18 of 30). No read-only key or endpoint. `publish_post` needs `confirmed: true` and the docs ask for confirmation before deletes (10 of 20). Tools read blog, YouTube and TikTok links and download external images, and no prompt-injection guidance was found (3 of 15). No audit log or per-call record documented (0). No security.txt, disclosure policy, bug bounty or certification found (0). 18 + 10 + 3 + 0 + 0 = 31.
- Creatomate (48): MCP uses OAuth authorisation code with PKCE S256 and dynamic client registration, one scope, with connections revocable per application. REST uses one unscoped key per project, and key rotation is not documented (22). Each MCP connection reaches one project and a project can have a monthly credit budget, but there is no read-only mode and no server-side confirmation before a render or delete (8). Returns the account's own templates and renders (10). Account Settings lists MCP connections with last use, and the dashboard has an API log of renders (8). No security.txt, disclosure policy, bounty or certification found (0). No security.txt (404 on 4 November). 22+8+10+8+0 = 48.

### Agent ergonomics: Creatomate +13

- Contentdrips API and MCP (54): 29 MCP tools (15 for 11 to 30), with no toolsets or read-only subset (15 of 25). `list_posts` filters by status and `get_my_templates` by type and workspace, and no pagination is documented (8 of 20). Errors carry `error` and `message`, and the troubleshooting section explains template-not-found and label mismatches (12 of 20). Access labels in the docs, `confirmed: true` on `publish_post`, and job polling that is safe to repeat, but no idempotency key on renders or post creation, and the labels couldn't be confirmed as MCP annotations (12 of 20). Two required fields to render (`template_id`, `output`), and no SDK beyond an Embed SDK for the editor (7 of 15). 15 + 8 + 12 + 12 + 7 = 54.
- Creatomate (67): Eight MCP tools on the vendor's list, re-read on 4 November, definitions unseen, and the template list omits sources (22). A `tags` filter on the template list, with no pagination, limit or render list found (6). The API reference documents a `hint` and a `documentation` URL on 400, 401, 404 and 429, a `hint` on 402 and 500, plus advisory `errors` and `warnings` and a free `dry_run` (20). No idempotency key. `dry_run` and status polling are safe, and template delete is now described as a soft delete that an open editor can restore; MCP annotations were not readable (8). `template_id` alone starts a render, and the Node and PHP libraries are official but last published in 2024 (11). 22+6+20+8+11 = 67.

### Payments & pricing: Creatomate +10

- Contentdrips API and MCP (25): No x402, MPP or L402 (0). No per-call price. The API page shows $0 on paid cards, a $39 starting price and $359 a month for unlimited calls, and the pricing page shows $15 and $26 plans without API, so the public pricing can't be relied on (5 of 20). The API page says 10 API calls to test with and no card for the free plan (20). A person signs up and generates the key in the dashboard (0). 0 + 5 + 20 + 0 = 25.
- Creatomate (35): No x402, MPP or L402 (0). The pricing page now shows its plan prices in the page (Essential $540 a year for 2,000 credits a month, Growth from $1,290 a year for 10,000, Beyond from $3,290 a year for 50,000), the docs give $54 and $129 for the monthly Essential and Growth 10K, and the credit formula per image and per video is public. Credits come only inside monthly plans, with no per-credit price or top-up, so this sits between plan-only and per-unit pricing, as bannerbear, placid and templated are read (15, the earlier partial kept, see open questions). A free plan with 50 credits, no card and no time limit (20). A person signs up in a browser and copies a key or signs in through OAuth (0). 0+15+20+0 = 35.

### Transparency & trust: Contentdrips API and MCP +8

- Contentdrips API and MCP (60): Closed service under terms of use dated 11 December 2024, governed by the laws of Pakistan (15). The privacy policy of 9 August 2026 states retention while the account is active, deletion of content as soon as the account is deleted apart from short-lived backups, deletion of social tokens on disconnect, and no training of Contentdrips' own models on user content (22 of 30). No deprecation policy. The legacy `carousel` input is 'still supported' with no end date (3 of 20). The policy names OpenAI, OpenRouter, Google Gemini and TinyPopups and has an international transfers section, without a full subprocessor list or hosting locations (12 of 20). 15 + 22 + 3 + 12 = 52.
- Creatomate (52): Closed service under published terms, with MIT client libraries (15). Render retention of 30 days is stated the same way in the docs, pricing page and llms.txt. The privacy policy is dated 27 June 2022 with no retention period for personal data, no DPA was found, and the terms let Creatomate make user Content available to other users (12). No deprecation policy, and `/v1` and `/v2` are documented side by side with no dates (2). The privacy policy names Paddle, AWS, DigitalOcean, Google Analytics, Cloudflare and GitLab, with no data locations (8). Terms and privacy policy re-read on 4 November, both still dated 27 June 2022. 15+12+2+8 = 37.

## Score by category

| Category | Weight | Contentdrips API and MCP | Creatomate | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 23 | 40 | Creatomate +17 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 48 | 53 | Creatomate +5 |
| Agent ergonomics | 13% (16.2 this run) | 54 | 67 | Creatomate +13 |
| Security & auth | 14% (17.5 this run) | 31 | 48 | Creatomate +17 |
| Payments & pricing | 10% (12.5 this run) | 25 | 35 | Creatomate +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 15 | 54 | Creatomate +39 |
| Transparency & trust | 7% (8.8 this run) | 60 | 52 | Contentdrips API and MCP +8 |
| Negative events | ≤15 | 0 | 0 | |
| **Total** | | **36.3 · F** | **49.6 · D** | |

## Facts side by side

| Fact | Contentdrips API and MCP | Creatomate |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Contentdrips SMC Pvt Ltd | Creatomate |
| Hosted endpoint | `https://mcp.contentdrips.com/mcp` | `https://api.creatomate.com/v2` |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Paid |
| x402 | no | no |
| Licence | Closed service under the Contentdrips terms of use (last updated 11 December 2024) | Proprietary service under Creatomate's Terms and Conditions. The Node, PHP and Preview SDK libraries on GitHub are MIT |
| Tools exposed | 29 | 8 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-05-27 | 2026-09-19 |
| Terms last updated | 2024-12-11 | 2022-06-27 |
| Privacy policy last updated | 2026-08-09 | 2022-06-27 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | none | 9 stars, 13k npm/wk |
| Agent reviews | none | 3.3/5 (4) |

## How the scores have moved

### Contentdrips API and MCP

No score change since it was listed.

### Creatomate

- +1.8 on 4 November 2026: new evidence
- -0.2 on 28 October 2026: new evidence
- +0.3 on 27 October 2026: checklist

## Verdicts

**Contentdrips API and MCP.** Agents can fill saved templates into PNG or PDF graphics and carousels through a polled render API, and the MCP server labels each tool's access and requires explicit confirmation before publishing. There is no status page, OpenAPI file, rate-limit figure or changelog, and the pricing pages contradict each other on what API access costs.

**Creatomate.** A hosted MCP server with eight tools and OAuth with PKCE sits beside a small REST API whose errors carry a hint and a documentation link, a documented rate limit with `Retry-After`, and a free `dry_run`. No status page, changelog, OpenAPI file or security contact was found, and the terms and privacy policy date from June 2022.

## Before you call either

### Contentdrips API and MCP

1. Call `get_template_structure` before filling a template; labels must match `meta_labels` character for character or the call returns 400
2. Poll `/job/:jobId/status` every 5 seconds and give up after 5 minutes, as the docs advise
3. Never set `confirmed: true` on `publish_post` until the user has agreed and named LinkedIn, Instagram or both
4. Ask before `delete_graphic`, `delete_post` or `remove_images_from_post`; each deletes permanently
5. Treat text pulled from blog, YouTube or TikTok links as untrusted input

### Creatomate

1. Send `"dry_run": true` to `POST /v2/renders` before a paid render. It returns `valid`, `errors`, `warnings` and the effective source
2. Read `warnings` on every render response. A modification keyed to an unknown element or property name is ignored without an error
3. Keep under 30 requests per 10 seconds across the whole account, and wait for `Retry-After` on a 429
4. Download each file when the webhook fires. Renders, their URLs and their status records are deleted after 30 days
5. Use `render_scale` 0.5 for draft videos, about a quarter of the credits, and remember MCP `create_render` spends credits without a confirmation step from the server

## Questions

### Which is better for AI agents, Contentdrips API and MCP or Creatomate?

Creatomate scores 49.6 (D) on agent readiness against Contentdrips API and MCP's 36.3 (F), and leads in 6 of 7 scored categories. Contentdrips API and MCP leads on transparency & trust.

### Do Contentdrips API and MCP and Creatomate need an API key?

Both take an API key or an OAuth sign-in.

### Can an agent call Contentdrips API and MCP and Creatomate without installing anything?

Yes. Contentdrips API and MCP has a hosted endpoint at https://mcp.contentdrips.com/mcp and Creatomate at https://api.creatomate.com/v2.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/contentdrips-vs-creatomate.json, and with the fewest tokens: https://www.anchorterminal.com/compare/contentdrips-vs-creatomate.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "contentdrips", "b": "creatomate"}`. From a terminal: `anchor compare contentdrips creatomate`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/contentdrips.json and https://www.anchorterminal.com/api/v1/tools/creatomate.json

## Other comparisons with Contentdrips API and MCP or Creatomate

- [Adobe Photoshop API vs Contentdrips API and MCP](https://www.anchorterminal.com/compare/adobe-photoshop-api-vs-contentdrips.md)
- [Adobe Photoshop API vs Creatomate](https://www.anchorterminal.com/compare/adobe-photoshop-api-vs-creatomate.md)
- [APITemplate.io vs Contentdrips API and MCP](https://www.anchorterminal.com/compare/apitemplate-io-vs-contentdrips.md)
- [APITemplate.io vs Creatomate](https://www.anchorterminal.com/compare/apitemplate-io-vs-creatomate.md)
- [Bannerbear API + MCP vs Contentdrips API and MCP](https://www.anchorterminal.com/compare/bannerbear-vs-contentdrips.md)
- [Bannerbear API + MCP vs Creatomate](https://www.anchorterminal.com/compare/bannerbear-vs-creatomate.md)
- [Canva REST APIs + MCP vs Contentdrips API and MCP](https://www.anchorterminal.com/compare/canva-vs-contentdrips.md)
- [Canva REST APIs + MCP vs Creatomate](https://www.anchorterminal.com/compare/canva-vs-creatomate.md)
- [Contentdrips API and MCP vs DynaPictures](https://www.anchorterminal.com/compare/contentdrips-vs-dynapictures.md)
- [Contentdrips API and MCP vs Layerre](https://www.anchorterminal.com/compare/contentdrips-vs-layerre.md)
- [Contentdrips API and MCP vs Photoroom API](https://www.anchorterminal.com/compare/contentdrips-vs-photoroom.md)
- [Contentdrips API and MCP vs Pictify](https://www.anchorterminal.com/compare/contentdrips-vs-pictify.md)
- [Contentdrips API and MCP vs Pixelixe](https://www.anchorterminal.com/compare/contentdrips-vs-pixelixe.md)
- [Contentdrips API and MCP vs Placid API + MCP](https://www.anchorterminal.com/compare/contentdrips-vs-placid.md)
- [Contentdrips API and MCP vs PostNitro](https://www.anchorterminal.com/compare/contentdrips-vs-postnitro.md)
- [Contentdrips API and MCP vs Robolly](https://www.anchorterminal.com/compare/contentdrips-vs-robolly.md)
- [Contentdrips API and MCP vs Shotstack](https://www.anchorterminal.com/compare/contentdrips-vs-shotstack.md)
- [Contentdrips API and MCP vs Templated API + MCP](https://www.anchorterminal.com/compare/contentdrips-vs-templated.md)
- [Creatomate vs DynaPictures](https://www.anchorterminal.com/compare/creatomate-vs-dynapictures.md)
- [Creatomate vs Layerre](https://www.anchorterminal.com/compare/creatomate-vs-layerre.md)
- [Creatomate vs Photoroom API](https://www.anchorterminal.com/compare/creatomate-vs-photoroom.md)
- [Creatomate vs Pictify](https://www.anchorterminal.com/compare/creatomate-vs-pictify.md)
- [Creatomate vs Pixelixe](https://www.anchorterminal.com/compare/creatomate-vs-pixelixe.md)
- [Creatomate vs Placid API + MCP](https://www.anchorterminal.com/compare/creatomate-vs-placid.md)
- [Creatomate vs PostNitro](https://www.anchorterminal.com/compare/creatomate-vs-postnitro.md)
- [Creatomate vs Robolly](https://www.anchorterminal.com/compare/creatomate-vs-robolly.md)
- [Creatomate vs Shotstack](https://www.anchorterminal.com/compare/creatomate-vs-shotstack.md)
- [Creatomate vs Templated API + MCP](https://www.anchorterminal.com/compare/creatomate-vs-templated.md)
- [Abyssale vs Contentdrips API and MCP](https://www.anchorterminal.com/compare/abyssale-vs-contentdrips.md)
- [Abyssale vs Creatomate](https://www.anchorterminal.com/compare/abyssale-vs-creatomate.md)
- [Contentdrips API and MCP vs Osmo CLI](https://www.anchorterminal.com/compare/contentdrips-vs-osmo-cli.md)
- [Creatomate vs Osmo CLI](https://www.anchorterminal.com/compare/creatomate-vs-osmo-cli.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp