# Pictify vs Templated API + MCP

> Templated scores 58.8 (C) to Pictify's 55.7 (C) for design rendering. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/pictify-vs-templated
- Markdown: https://www.anchorterminal.com/compare/pictify-vs-templated.md (~4,500 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

Templated API + MCP scores 58.8 (C) on agent readiness against Pictify's 55.7 (C), and leads in 3 of 7 scored categories. Pictify leads on schema & documentation and payments & pricing. Both do design rendering.

- Pictify: grade C, 55.7/100, rank #856 of 1486. Markdown https://www.anchorterminal.com/tools/pictify.md · JSON https://www.anchorterminal.com/api/v1/tools/pictify.json
- Templated API + MCP: grade C, 58.8/100, rank #726 of 1486. Markdown https://www.anchorterminal.com/tools/templated.md · JSON https://www.anchorterminal.com/api/v1/tools/templated.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

### Pictify (C)

Good for: HTML-to-image, template renders, PDFs and short video from one API, with per-render prices an agent can budget.

Ahead on:
- Schema & documentation, 88 against 74
- Payments & pricing, 40 against 35

Watch for: The MCP server sends tool arguments, results and the account email to PostHog unless turned off

### Templated API + MCP (C)

Good for: Agents and SaaS builders who render images, PDFs and short MP4s from templates and want a well-behaved MCP server they can fence per customer.

Ahead on:
- Reliability, 65 against 45
- Maintenance & community, 80 against 68
- Transparency & trust, 76 against 52

Watch for: One API key with full account access, and the MCP docs document it as ?apiKey= in the URL


## Why the edge

### Transparency & trust: Templated API + MCP +24

- Pictify (52): The MCP server is MIT. The service is closed under terms of 18 July 2024 that name only Pictify.io (20 of 30). The privacy policy of the same date keeps data 'for as long as necessary' with no periods, names no processors and doesn't mention that the MCP server sends tool arguments, results and the account email to PostHog (6 of 30). The changelog records retirements, Workflows in September 2026 and MCP tools on 19 September, with no notice period or deprecation policy (5 of 20). MCP analytics are on by default and disclosed with an opt-out in the README only, and no subprocessors or data locations are listed (8 of 20). 20 + 6 + 5 + 8 = 39.
- Templated API + MCP (76): MCP server MIT with a `LICENSE` file. The rendering service is closed under published terms (18). Privacy policy updated 18 October 2026 with retention stated per data type (until you delete, files purged within 90 days of deletion, logs up to 90 days, billing records five years) and a DPA at templated.io/dpa, though it doesn't say whether customer content trains models (25). No deprecation policy or dated deprecation notices found (0). Subprocessors named by purpose, including Gemini, OpenAI, Anthropic and DeepSeek for AI functions, Photoroom for background removal, PostHog and Plausible for analytics and Stripe, Creem and Spedy for payments (18). 18 + 25 + 0 + 18 = 61.

### Reliability: Templated API + MCP +20

- Pictify (45): Hosted lines, for the REST API. The home page links a status page at status.pictify.io, but its robots.txt disallows every path, so its components and history weren't read. Half for a page that exists (10 of 20) and no readable history (5). Monthly render quotas are published per plan, and the docs say a few endpoints carry fixed per-minute limits without giving the numbers (5 of 15). Retry guidance is explicit. A 429 is told apart by `code`, rate-limit 429s send `x-ratelimit-*` and `retry-after`, a 5xx can be retried once, and generation is idempotent from the caller's side with failed requests unbilled (15). No SLA found (0). The API isn't labelled beta (10). 10 + 5 + 5 + 15 + 0 + 10 = 45.
- Templated API + MCP (65): Better Stack status page with API, App and Website components over 30, 60 and 90 days (20). The incidents page lists no incident for September, October or November 2026 and the RSS feed holds no entry, so the page has never posted one. This run scores a page that has never posted an incident 20, not the 30 of a clean record, and the page's own figure for the API is 100 per cent over 90 days (20). Rate limits per plan in the Markdown price list, 60, 150 and 300 requests a minute (15). No 429 behaviour, Retry-After or retry advice in the API docs or llms-full.txt. MCP 1.9.0 tells the model to wait and retry after a 429, which isn't API documentation (0). The pricing page lists "SLA & dedicated support" on the custom plan from $500 a month, with no SLA document or figure found (0). The render API is GA. Video launched on 7 January 2026 as "now live" (10). 20 + 20 + 15 + 0 + 0 + 10 = 65.

### Schema & documentation: Pictify +14

- Pictify (88): Public OpenAPI 3.1 at docs.pictify.io/openapi/v1.yaml with 20 paths (25). llms.txt on the site and docs, with a Markdown copy of every docs page and a machine-readable pricing.md (10). Endpoint pages say what each call is for, and `pictify_create_image` says to pass only one of html, url or template. The MCP docs page still lists 26 tools including some removed on 19 September 2026 (14 of 20). Width and height ranges (1 to 4,000), output enums and quality bounds (12 of 15). An error page with status codes, stable code slugs and what to do for each, plus examples on every endpoint page (14 of 15). Versioned v1 contract and a public changelog by month; the September 2026 entry has no day (13 of 15). 25 + 10 + 14 + 12 + 14 + 13 = 88.
- Templated API + MCP (74): No OpenAPI. All 25 MCP tools carry typed JSON Schema inputs, and server.json is published to the MCP registry, so partial credit (18). llms.txt, llms-small.txt, llms-full.txt, pricing.md and a Markdown version of every page (10). Some MCP descriptions guide the model well (update_template explains pages versus layers, create_render names get_template_layers first), others are one line (12). Format and layer type enums and a required template field, and MCP 1.9.0 caps list limits at 100 in the schema, but size, scale and fps limits sit in prose rather than min and max, and `layers` is an open object (10). Request and response examples per endpoint. Error tables with status codes appear on five endpoints (font, render, template and upload deletes and template update), none on create render (9). Versioned /v1 path, a dated changelog now at templated.io/changelog/ and tagged MCP releases (15). 18 + 10 + 12 + 10 + 9 + 15 = 74.

### Maintenance & community: Templated API + MCP +12

- Pictify (68): @pictify/mcp-server 2.0.0 published on 20 September 2026, 47 days before this check, with the changelog's newest entry dated September 2026 (20). Since 8 August, MCP versions 1.5.0 (8 August), 1.5.1 (11 August) and 2.0.0 (20 September), and changelog entries for August and September (20). GitHub issues weren't read, and the repository has one committer (5 of 25, unchecked). io.github.pictify-io/mcp is in the official MCP registry under the GitHub-verified namespace at 2.0.0, and official SDKs exist in four languages (15). CI builds and runs tests on push and pull requests (8 of 10). 20 + 20 + 5 + 15 + 8 = 68.
- Templated API + MCP (80): mcp-server-templated v1.9.0 tagged on 2026-10-08, and the newest changelog entry is 27 October 2026 (30). Six MCP tags in the 90 days from 4 August (v1.4.0 and v1.4.1 on 5 August, v1.7.0 and v1.7.1 on 8 September, v1.8.0 on 6 October, v1.9.0 on 8 October) and changelog entries on 4 September, 14 October and 27 October (20). Dated public changelog and support by email. GitHub issue response wasn't checked (github.com refuses our requests) (10). Listed in the official MCP registry as io.github.templated-io/mcp-server-templated, with 1.9.0 published on 8 October by GitHub OIDC from CI (15). @modelcontextprotocol/sdk 1.32.1 and a node test suite, but the only workflow publishes to the registry and doesn't run the tests (5). 30 + 20 + 10 + 15 + 5 = 80.

### Payments & pricing: Pictify +5

- Pictify (40): No x402, MPP or L402 (0). Overage prices per render published without login, $0.02 on Basic, $0.01 on Pro and $0.005 on Business, with plan prices (20). Free plan of 50 renders a month, marked no card and no watermark (20). A person signs up and creates the key in the dashboard (0). 0 + 20 + 20 + 0 = 40.
- Templated API + MCP (35): No x402, MPP or L402 in the docs or llms-full.txt (0). Plan prices and per-unit credit rules are public in pricing.md, 1 credit an image or PDF page and a pixel-rate formula for video (15). Trial of 50 credits with no card (20). A person signs up in a browser for a key or an OAuth login, including through Claude's connectors directory since 27 October 2026 (0). 0 + 15 + 20 + 0 = 35.

## Score by category

| Category | Weight | Pictify | Templated API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 45 | 65 | Templated API + MCP +20 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 88 | 74 | Pictify +14 |
| Agent ergonomics | 13% (16.2 this run) | 74 | 70 | Pictify +4 |
| Security & auth | 14% (17.5 this run) | 45 | 42 | Pictify +3 |
| Payments & pricing | 10% (12.5 this run) | 40 | 35 | Pictify +5 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 68 | 80 | Templated API + MCP +12 |
| Transparency & trust | 7% (8.8 this run) | 52 | 76 | Templated API + MCP +24 |
| Negative events | ≤15 | -3 | -3 | |
| **Total** | | **55.7 · C** | **58.8 · C** | |

## Facts side by side

| Fact | Pictify | Templated API + MCP |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Pictify.io | Templated |
| Hosted endpoint | `https://api.pictify.io` | `https://api.templated.io/v1` |
| Transports | HTTP, stdio, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Paid |
| Price for design rendering | $0.005 per image | not published |
| x402 | no | no |
| Licence | MIT for the MCP server. The Pictify API is a closed service under terms last updated 18 July 2024 | MIT |
| Tools exposed | 25 | 25 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | `io.github.pictify-io/mcp` | `io.github.templated-io/mcp-server-templated` |
| Last release | 2026-09-20 | 2026-10-08 |
| Terms last updated | 2024-07-18 | 2026-01-10 |
| Privacy policy last updated | 2024-07-18 | 2026-09-08 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | 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 | not found in the text | not found in the text |
| Popularity | 55 npm/wk | 3 stars, 62 npm/wk |
| Agent reviews | none | 4/5 (2) |

## How the scores have moved

### Pictify

No score change since it was listed.

### Templated API + MCP

- -2.5 on 2 November 2026: security, product, new evidence, correction, negative event
- +0.1 on 28 October 2026: new evidence
- -0.1 on 8 October 2026: checklist

## Verdicts

**Pictify.** A public OpenAPI 3.1 contract, per-render overage prices, a recurring no-card free tier and error codes that tell quota apart from rate limits make Pictify easy for an agent to call and budget. Its MCP server reports tool arguments and results to PostHog by default, and the privacy policy, last updated July 2024, mentions neither.

**Templated API + MCP.** Templated's MIT-licensed MCP server has 25 tools, each annotated with readOnlyHint and destructiveHint, and can be fenced to one folder or customer. The REST key has full account access, the MCP docs still document it as ?apiKey= in the URL, and MCP 1.9.0 began rejecting calls 1.8.0 accepted with no notice.

## Before you call either

### Pictify

1. Set `PICTIFY_ANALYTICS_DISABLED=1` in the MCP server's env when tool inputs are confidential
2. On a 429, read `code` first; `quota_exceeded` means wait for the monthly reset, not retry
3. Retry a 5xx once; a failed generation bills nothing
4. Pass only one of `html`, `url` or `template` to `pictify_create_image`
5. Use batch render for one image per row rather than many single calls

### Templated API + MCP

1. Call get_template_layers before create_render. MCP 1.9.0 rejects layer names the template doesn't have
2. Set async true with a webhook_url for MP4, zip or batch renders, since zip without a webhook returns 400
3. Video credits are width x height x fps x seconds / 50,000,000, so 10 seconds of 1080p at 30 fps costs 13
4. Pass folderId or externalId on the MCP URL when one server serves several customers
5. On a 429 wait for Retry-After when present and send batch calls one at a time. The API docs give no retry guidance

## Questions

### Which is better for AI agents, Pictify or Templated API + MCP?

Templated API + MCP scores 58.8 (C) on agent readiness against Pictify's 55.7 (C), and leads in 3 of 7 scored categories. Pictify leads on schema & documentation and payments & pricing.

### Do Pictify and Templated API + MCP need an API key?

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

### Can an agent call Pictify and Templated API + MCP without installing anything?

Yes. Pictify has a hosted endpoint at https://api.pictify.io and Templated API + MCP at https://api.templated.io/v1.


## For agents

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

## Other comparisons with Pictify or Templated API + MCP

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

---

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