# Layerre vs Pictify

> Layerre scores 57.6 (C) to Pictify's 55.7 (C) for design templates. Prices, MCP, x402, uptime and agent notes side by side.

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

Layerre scores 57.6 (C) on agent readiness against Pictify's 55.7 (C), and leads in 3 of 7 scored categories. Pictify leads on agent ergonomics and payments & pricing. Both do design templates.

- Layerre: grade C, 57.6/100, rank #785 of 1486. Markdown https://www.anchorterminal.com/tools/layerre.md · JSON https://www.anchorterminal.com/api/v1/tools/layerre.json
- 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
- 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

### Layerre (C)

Good for: Bulk image and PDF variants from Canva designs a team already has.

Ahead on:
- Maintenance & community, 78 against 68
- Transparency & trust, 63 against 52

Also in its favour:
- No incidents deducted, where Pictify loses 3 points for them

Watch for: Imports Canva designs only; there is no template editor of its own

### 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:
- Agent ergonomics, 74 against 69
- Payments & pricing, 40 against 25

Also in its favour:
- Free to start without a card

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


## Why the edge

### Payments & pricing: Pictify +15

- Layerre (25): No x402, MPP or L402 (0). Plan prices are public with render counts, and one import or one variant is one render, so the price a render follows from the plan (about $0.03 on Starter, $0.005 on Pro) without being published per unit (15 of 20). Free plan of 50 renders a month with API access; the pricing page doesn't say whether a card is needed (10 of 20, half as with an unstated card rule). A person signs up and creates the key, or approves OAuth in a browser (0). 0 + 15 + 10 + 0 = 25.
- 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.

### Transparency & trust: Layerre +11

- Layerre (63): The MCP server is MIT. The service is closed under terms of 13 August 2026 that name a sole proprietorship in Ontario (20 of 30). The privacy policy and DPA of the same date agree. Data is kept while the account is active and deleted from production on account deletion, with limited backups. Design files aren't used to train public AI models. Google Analytics runs on accepted cookies (24 of 30). No deprecation policy or notice period (0). Ten subprocessors listed with purpose and location in both documents, including Supabase, Stripe, Cloudflare, Google, Resend, Canva and Slack (20). 20 + 24 + 0 + 20 = 64.
- 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.

### Maintenance & community: Layerre +10

- Layerre (78): @layerre/mcp-server 0.1.0 published to npm on 29 October 2026, 8 days before this check (30). MCP server commits from 19 to 24 October, the registry entry of 29 October, and What's New entries dated 21 August and 18 October in the sitemap (20). The repository is a week old with no issues to judge; support by email and in-app chat (5 of 25). com.layerre/layerre is in the official MCP registry under a domain-verified namespace (15). CI runs the vitest suite on push and pull requests to main on Node 22 (8 of 10). 30 + 20 + 5 + 15 + 8 = 78.
- 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.

### Agent ergonomics: Pictify +5

- Layerre (69): 13 MCP tools (15 for 11 to 30), with no toolsets or read-only subset (15). Template and variant lists take `skip` and `limit`, and templates filter by `tag` and `q` and can leave out layers (16 of 20). 422 validation bodies and a JSON 429 with `retry_after` (17 of 20). Every tool is annotated, read tools with readOnlyHint and idempotentHint, updates idempotent, no tool destructive, and the server has no delete tool. The REST API has no idempotency keys for variant creation (16 of 20). Few required fields, but no official SDK; a Postman collection and the MCP package only (5 of 15). 15 + 16 + 17 + 16 + 5 = 69.
- Pictify (74): 25 MCP tools in the 2.0.0 source (15 for 11 to 30), with no toolsets or read-only subset (15). List endpoints page with `page` and `limit` (16 of 20). Error bodies carry `code` slugs such as `quota_exceeded`, `template_limit_reached` and `invalid_variable`, and the docs say which are retryable (18 of 20). Generation is safe to retry and failed calls bill nothing, but the MCP source sets no readOnlyHint or destructiveHint, and the delete tools for templates and video templates run without a confirmation step (10 of 20). Official SDKs for Node.js, Python, Go and Ruby, sensible defaults such as 1200 x 630 PNG (15). 15 + 16 + 18 + 10 + 15 = 74.

## Score by category

| Category | Weight | Layerre | Pictify | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 42 | 45 | Pictify +3 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 87 | 88 | Pictify +1 |
| Agent ergonomics | 13% (16.2 this run) | 69 | 74 | Pictify +5 |
| Security & auth | 14% (17.5 this run) | 48 | 45 | Layerre +3 |
| Payments & pricing | 10% (12.5 this run) | 25 | 40 | Pictify +15 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 78 | 68 | Layerre +10 |
| Transparency & trust | 7% (8.8 this run) | 63 | 52 | Layerre +11 |
| Negative events | ≤15 | 0 | -3 | |
| **Total** | | **57.6 · C** | **55.7 · C** | |

## Facts side by side

| Fact | Layerre | Pictify |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Layerre | Pictify.io |
| Hosted endpoint | `https://api.layerre.com/v1` | `https://api.pictify.io` |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, stdio, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | MIT for the MCP server. The Layerre API is a closed service under terms last updated 13 August 2026 | MIT for the MCP server. The Pictify API is a closed service under terms last updated 18 July 2024 |
| Tools exposed | 13 | 25 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | `com.layerre/layerre` | `io.github.pictify-io/mcp` |
| Last release | 2026-10-29 | 2026-09-20 |
| Terms last updated | no date given | 2024-07-18 |
| Privacy policy last updated | no date given | 2024-07-18 |
| 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 | 119 npm/wk | 55 npm/wk |

## Verdicts

**Layerre.** A public OpenAPI 3.1 contract, published rate limits with Retry-After, and 13 annotated MCP tools that can't delete anything make Layerre straightforward for an agent to call. It works only from Canva designs, is run by a sole proprietor with no status page or SLA, and its API and MCP server are at version 0.1.0.

**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.

## Before you call either

### Layerre

1. Call `layerre_auth_status` first to confirm the connection
2. Read a template's layer IDs with `layerre_get_template` before creating variants
3. Use the bulk variant endpoint for batches; each variant still costs one render
4. On 429 wait for the Retry-After seconds; limits are per IP address
5. Expect template import from a Canva link to take 10 to 30 seconds

### 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

## Questions

### Which is better for AI agents, Layerre or Pictify?

Layerre scores 57.6 (C) on agent readiness against Pictify's 55.7 (C), and leads in 3 of 7 scored categories. Pictify leads on agent ergonomics and payments & pricing.

### Do Layerre and Pictify need an API key?

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

### Can an agent call Layerre and Pictify without installing anything?

Yes. Layerre has a hosted endpoint at https://api.layerre.com/v1 and Pictify at https://api.pictify.io.


## For agents

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

## Other comparisons with Layerre or Pictify

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

---

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