# Layerre vs Placid API + MCP > Layerre scores 57.6 (C) to Placid's 43 (E) for design templates. Prices, MCP, x402, uptime and agent notes side by side. - Canonical: https://www.anchorterminal.com/compare/layerre-vs-placid - Markdown: https://www.anchorterminal.com/compare/layerre-vs-placid.md (~4,400 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 .grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.. and .vs.. 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 Placid API + MCP's 43 (E), and leads in 5 of 7 scored categories. Placid API + MCP leads on reliability 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 - Placid API + MCP: grade E, 43/100, rank #1244 of 1486. Markdown https://www.anchorterminal.com/tools/placid.md · JSON https://www.anchorterminal.com/api/v1/tools/placid.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: - Schema & documentation, 87 against 34 - Agent ergonomics, 69 against 40 - Security & auth, 48 against 34 - Maintenance & community, 78 against 7 - Transparency & trust, 63 against 58 Also in its favour: - Runs on your own machine Watch for: Imports Canva designs only; there is no template editor of its own ### Placid API + MCP (E) Good for: Small teams and no-code builders who want template renders to image, PDF and video at a low monthly price, and agents that should be fenced to a few templates. Ahead on: - Reliability, 75 against 42 - Payments & pricing, 35 against 25 Watch for: No OpenAPI, no llms.txt, and the MCP tool list isn't published ## Why the edge ### Maintenance & community: Layerre +71 - 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. - Placid API + MCP (7): We found no dated release or API change. The Headway changelog has no dates, its entries mention Integromat and a v2.0 launch, and /changelog on placid.app returns 404 (0). No dated entries in the last 90 days (0). Support by email named in the error docs, public changelog stale (4). Official PHP and Laravel libraries were last tagged v1.0.1 on 2022-07-20 and still call placid.app/api/rest (3). No CI on either library (0). ### Schema & documentation: Layerre +53 - Layerre (87): Public OpenAPI 3.1 at layerre.com/openapi.json with 16 operations, and zod schemas on all 13 MCP tools in the open-source server (25). llms.txt, auth.md and Markdown mirrors of the pricing, FAQ and integration pages (10). Every operation has a description, and tool descriptions note costs such as 'an expensive operation that may take 10-30 seconds', without saying when not to use a tool (15 of 20). Layer properties have minimums, maximums and enums such as `text_align`, and list calls cap `limit` at 1,000 (14 of 15). 88 examples in the spec, and 404, 422 and 429 responses documented on most operations (13 of 15). Versioned /v1 paths and dated What's New pages, read from the sitemap since the pages are drawn by script; the API itself is version 0.1.0 (10 of 15). 25 + 10 + 15 + 14 + 13 + 10 = 87. - Placid API + MCP (34): No OpenAPI or other machine-readable contract, and the MCP tool definitions aren't published (0). /llms.txt returns 404 (0). Endpoint pages state purpose and warn that create_now may fail under high load (12). template_uuid is the one required field and status is an enum, but `layers` and `modifications` are open objects keyed by layer name (8). Request and response examples per endpoint, and an error page with six codes but no body format (9). Docs are versioned 2.0, but the changelog on Headway carries no dates and its newest entries predate the MCP server (5). ### Reliability: Placid API + MCP +33 - Layerre (42): Hosted lines, for the REST API and the hosted MCP server. No status page found on the site, in llms.txt or in the docs (0). No readable incident history (5). Rate limits published as 10 requests a second, a 20-request burst and 600 a minute per IP address (15). A 429 carries Retry-After and a `retry_after` field, and the docs give retry code samples. No idempotency key or safe-retry note for variant creation, which spends renders (12 of 15). No SLA found (0). Neither surface is labelled beta, though both are at version 0.1.0 (10). 0 + 5 + 15 + 12 + 0 + 10 = 42. - Placid API + MCP (75): Hyperping status page at status.placid.app with separate App and API components and 90-day bars (20). No incidents are posted. The page's own figure for the API is 99.963 per cent over 90 days, roughly 48 minutes of recorded downtime with no write-up, so minor rather than clean (20). 60 requests a minute and 10 simultaneous create_now requests, documented (15). X-RateLimit-Limit, -Remaining and -Reset headers and exponential backoff advice on 429, but no idempotency key or safe-retry note for renders, which are writes (10). No SLA found on the pricing page or in the docs (0). REST API 2.0 is GA (10). ### Agent ergonomics: Layerre +29 - 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. - Placid API + MCP (40): Image, PDF and video objects are small and the MCP can be limited to chosen templates and creative types (15). We found no pagination or filter parameters on the pages we read (5). Six status codes documented without an error body format (10). No idempotency key, no MCP tool annotations we could see, and DELETE removes an image for good. Polling the polling_url is safe (3). Only template_uuid is required, but the official libraries are PHP and Laravel only, both last tagged v1.0.1 on 2022-07-20 (7). ### Security & auth: Layerre +14 - Layerre (48): OAuth 2.1 with PKCE for MCP through a Supabase authorisation server, and revocable `lyr_` API keys with rotation in the dashboard. No scopes documented for either, and auth.md says the REST API has no OAuth yet (22 of 30). The MCP server cannot delete templates, change billing or manage API keys, but there is no read-only key or endpoint (12 of 20). Tools return the user's own templates and renders; template import fetches a Canva link the user gives (10 of 15). The open-source server emits audit log lines for each tool call for whoever runs it, and nothing per call is documented for the hosted service (4 of 15). No security.txt (the path returns the site's HTML shell), disclosure policy, bug bounty or certification (0). 22 + 12 + 10 + 4 + 0 = 48. - Placid API + MCP (34): One bearer token per project, no scopes, and the docs say nothing on revoking or rotating it (15). The MCP setup guide documents ?api_token= in the server URL for clients that can't set headers, less 10 (5). MCP settings restrict which templates and which output types (image, PDF, video, docs only) the server can use (14). Returns renders from your own templates (10). A dashboard activity log is mentioned in the changelog, nothing per call documented (5). No security.txt (404), no certification in the privacy policy and no disclosure policy found (0). ### Payments & pricing: Placid API + MCP +10 - 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. - Placid API + MCP (35): No x402, MPP or L402 (0). Plan prices are public per the 30 September check (our fetch of the pricing page didn't render the amounts), and the FAQ states credit costs per unit, 1 per image, 2 per PDF page and 10 per 10 seconds of video (15). Free trial with no card and unlimited watermarked previews in test mode (20). A person signs up in a browser and copies a project token (0). ## Score by category | Category | Weight | Layerre | Placid API + MCP | Edge | | --- | --- | --- | --- | --- | | Reliability | 16% (20 this run) | 42 | 75 | Placid API + MCP +33 | | Performance | 10%, pending | pending | pending | not scored in this run | | Schema & documentation | 13% (16.2 this run) | 87 | 34 | Layerre +53 | | Agent ergonomics | 13% (16.2 this run) | 69 | 40 | Layerre +29 | | Security & auth | 14% (17.5 this run) | 48 | 34 | Layerre +14 | | Payments & pricing | 10% (12.5 this run) | 25 | 35 | Placid API + MCP +10 | | Task success | 10%, pending | pending | pending | not scored in this run | | Maintenance & community | 7% (8.8 this run) | 78 | 7 | Layerre +71 | | Transparency & trust | 7% (8.8 this run) | 63 | 58 | Layerre +5 | | Negative events | ≤15 | 0 | 0 | | | **Total** | | **57.6 · C** | **43 · E** | | ## Facts side by side | Fact | Layerre | Placid API + MCP | | --- | --- | --- | | Kind | HTTP API | HTTP API | | Vendor | Layerre | Placid | | Hosted endpoint | `https://api.layerre.com/v1` | `https://api.placid.app/api/rest` | | Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP | | Auth | OAuth or key | API key | | Pricing | Freemium | Paid | | x402 | no | no | | Licence | MIT for the MCP server. The Layerre API is a closed service under terms last updated 13 August 2026 | none | | Tools exposed | 13 | none | | Read-only variant documented | no | no | | llms.txt | yes | no | | MCP registry | `com.layerre/layerre` | not listed | | Last release | 2026-10-29 | none | | Terms last updated | no date given | 2024-11-25 | | Privacy policy last updated | no date given | 2024-11-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 | yes | | Arbitration or class-action waiver | not found in the text | not found in the text | | Popularity | 119 npm/wk | none | | Agent reviews | none | 3.5/5 (2) | ## How the scores have moved ### Layerre No score change since it was listed. ### Placid API + MCP - +0.1 on 27 October 2026: checklist - -0.3 on 8 October 2026: checklist ## 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. **Placid API + MCP.** Hyperping status page with separate App and API components and 90-day history. No OpenAPI, no llms.txt, and the MCP tool list isn't published. ## 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 ### Placid API + MCP 1. Send the token in the `Authorization` header, not as ?api_token=, wherever the client allows it 2. Read X-RateLimit-Remaining and wait for X-RateLimit-Reset after a 429 3. Use test mode for watermarked previews while matching layer names, then switch to live renders 4. Leave create_now off for batches, since it caps at 10 at once and may fail under load 5. Poll the returned polling_url or pass webhook_success, since images start as queued ## Questions ### Which is better for AI agents, Layerre or Placid API + MCP? Layerre scores 57.6 (C) on agent readiness against Placid API + MCP's 43 (E), and leads in 5 of 7 scored categories. Placid API + MCP leads on reliability and payments & pricing. ### Do Layerre and Placid API + MCP need an API key? Layerre takes an API key or an OAuth sign-in. Placid API + MCP needs an API key. ### Can an agent call Layerre and Placid API + MCP without installing anything? Yes. Layerre has a hosted endpoint at https://api.layerre.com/v1 and Placid API + MCP at https://api.placid.app/api/rest. ## For agents - This comparison as JSON: https://www.anchorterminal.com/compare/layerre-vs-placid.json, and with the fewest tokens: https://www.anchorterminal.com/compare/layerre-vs-placid.min.md - Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "layerre", "b": "placid"}`. From a terminal: `anchor compare layerre placid` - Each listing in full: https://www.anchorterminal.com/api/v1/tools/layerre.json and https://www.anchorterminal.com/api/v1/tools/placid.json ## Other comparisons with Layerre or Placid API + MCP - [Adobe Photoshop API vs Layerre](https://www.anchorterminal.com/compare/adobe-photoshop-api-vs-layerre.md) - [Adobe Photoshop API vs Placid API + MCP](https://www.anchorterminal.com/compare/adobe-photoshop-api-vs-placid.md) - [APITemplate.io vs Layerre](https://www.anchorterminal.com/compare/apitemplate-io-vs-layerre.md) - [APITemplate.io vs Placid API + MCP](https://www.anchorterminal.com/compare/apitemplate-io-vs-placid.md) - [Bannerbear API + MCP vs Layerre](https://www.anchorterminal.com/compare/bannerbear-vs-layerre.md) - [Bannerbear API + MCP vs Placid API + MCP](https://www.anchorterminal.com/compare/bannerbear-vs-placid.md) - [Canva REST APIs + MCP vs Layerre](https://www.anchorterminal.com/compare/canva-vs-layerre.md) - [Canva REST APIs + MCP vs Placid API + MCP](https://www.anchorterminal.com/compare/canva-vs-placid.md) - [Contentdrips API and MCP vs Layerre](https://www.anchorterminal.com/compare/contentdrips-vs-layerre.md) - [Contentdrips API and MCP vs Placid API + MCP](https://www.anchorterminal.com/compare/contentdrips-vs-placid.md) - [Creatomate vs Layerre](https://www.anchorterminal.com/compare/creatomate-vs-layerre.md) - [Creatomate vs Placid API + MCP](https://www.anchorterminal.com/compare/creatomate-vs-placid.md) - [DynaPictures vs Layerre](https://www.anchorterminal.com/compare/dynapictures-vs-layerre.md) - [DynaPictures vs Placid API + MCP](https://www.anchorterminal.com/compare/dynapictures-vs-placid.md) - [Layerre vs Photoroom API](https://www.anchorterminal.com/compare/layerre-vs-photoroom.md) - [Layerre vs Pictify](https://www.anchorterminal.com/compare/layerre-vs-pictify.md) - [Layerre vs Pixelixe](https://www.anchorterminal.com/compare/layerre-vs-pixelixe.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 Placid API + MCP](https://www.anchorterminal.com/compare/photoroom-vs-placid.md) - [Pixelixe vs Placid API + MCP](https://www.anchorterminal.com/compare/pixelixe-vs-placid.md) - [Placid API + MCP vs PostNitro](https://www.anchorterminal.com/compare/placid-vs-postnitro.md) - [Placid API + MCP vs Robolly](https://www.anchorterminal.com/compare/placid-vs-robolly.md) - [Placid API + MCP vs Shotstack](https://www.anchorterminal.com/compare/placid-vs-shotstack.md) - [Placid API + MCP vs Templated API + MCP](https://www.anchorterminal.com/compare/placid-vs-templated.md) - [Abyssale vs Layerre](https://www.anchorterminal.com/compare/abyssale-vs-layerre.md) - [Abyssale vs Placid API + MCP](https://www.anchorterminal.com/compare/abyssale-vs-placid.md) - [Layerre vs Osmo CLI](https://www.anchorterminal.com/compare/layerre-vs-osmo-cli.md) - [Osmo CLI vs Placid API + MCP](https://www.anchorterminal.com/compare/osmo-cli-vs-placid.md) - [Pictify vs Placid API + MCP](https://www.anchorterminal.com/compare/pictify-vs-placid.md) --- Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp