CompleteOct 29228 of 228 pages readUnclaimed

Agent readiness report

Layerre

layerre.com

SaaSVisit site ↗

Layerre automates design variations and bulk-generates Canva content at scale with its API.

69/100Tier 4 · Agent-Ready
69/100

Tier 4 · Agent-Ready

15 questions a buyer might ask ChatGPT, Claude, Dots or Muse

11 of 15 buyer questions hit a dead end.

Buyer questions58/10011 dead ends
Agent access94/10015 of 16 pass
Re-audit · 1 credit

12 to fix · 228 of 228 pages read · Oct 29, 2026

Buyer questions

11 dead ends · 4 answered

What an AI agent reading layerre.com would conclude

Goes silentOperations · medium+4 pts est.

What uptime SLA do you offer on the render API, and what compensation applies if you miss it?

  1. Closest pages
  2. Pages say

    No page answers it.

    The site does not publish an uptime SLA for the render API, and it does not mention any compensation such as service credits for missed availability. The pricing page lists plan features and support levels, from basic email support to dedicated priority support, but no availability commitment appears anywhere on the site.

Fix

Publish an SLA section on the pricing page stating the render API uptime target and the service credits or refunds applied when it is missed.

Goes silentTechnical · medium+4 pts est.

If a render fails halfway through a 500-row batch, does it resume from the failed row or restart everything, and are retries idempotent?

  1. Closest pages
  2. Pages say

    No page answers it.

    The site does not say whether a failed batch render resumes from the failed row or starts over, and it never addresses retry idempotency. The API reference at /openapi.json shows bulk render requests are capped at 50 items per call and responses report total_created and total_failed counts, but no error handling, retry, or idempotency behavior is documented anywhere on the site.

Fix

Add an 'Error handling and retries' section to the API docs stating whether failed bulk renders resume from the failed item or restart, and whether retries are idempotent.

HedgesIntegration · high+3 pts est.

Do I need my own Canva account (and does it have to be a paid Canva plan) for Layerre to automate my templates, or does Layerre render designs independently?

  1. Found on
  2. Pages say

    Mentioned, not specified.

    No paid Canva plan is required: the FAQ at /faq/can-you-use-canva-api-without-enterprise says you can automate Canva designs via API on any Canva plan using Layerre, and the Layerre vs Canva Connect API comparison notes that Canva's own API needs Enterprise while Layerre renders Canva templates in one API call on any plan. The site does not explicitly say whether you need your own Canva account. Its pages describe importing your existing Canva designs into Layerre (for example the multi-page Canva designs FAQ and the Bannerbear alternative page's 'Keep Canva templates'), which implies your designs start in Canva, but no page states the account requirement outright.

Fix

Add to /faq/can-you-use-canva-api-without-enterprise whether a Canva account is required, that the free Canva plan is enough, and that Layerre renders designs itself after a one-time import.

HedgesSecurity · high+3 pts est.

Will you sign a DPA, and is customer data from uploaded spreadsheets and images processed in a GDPR-compliant way?

  1. Found on
  2. Pages say

    Mentioned, not specified.

    Yes: Layerre publishes a Data Processing Addendum (DPA / AVV) under GDPR Article 28 for customers who process personal data through its design automation API, at layerre.com/dpa. The privacy policy at layerre.com/privacy states it covers GDPR/DSGVO and how data is collected, used, and protected, including subprocessors. The site does not specifically describe how uploaded spreadsheet and image data is processed in a GDPR-compliant way.

Fix

Add a section to /dpa or /privacy stating how uploaded spreadsheet and image data is stored, processed, retained, and deleted under GDPR.

HedgesLimits · medium+3 pts est.

What's the maximum file size per render job, and which output formats (PDF, PNG, SVG) are supported?

  1. Found on
  2. Pages say

    Mentioned, not specified.

    Layerre supports four export formats: PNG, JPEG, PDF, and WebP. SVG is not supported; the API reference at /openapi.json defines the ExportType enum as png, pdf, jpeg, webp, and the glossary, MCP integration page, and What's New pages list the same four formats. The site does not state a maximum file size per render job; it only documents pixel dimension caps of 10000 by 10000, a 2000-override limit per variant, and a render timeout error.

Fix

Add the max file size per render job in MB to the limits docs at /docs/ and state explicitly that SVG is not an export format.

HedgesSecurity · medium+3 pts est.

How does API authentication work — static keys, HTTP message signatures, or OAuth — and can I rotate credentials without breaking production?

  1. Found on
  2. Pages say

    Mentioned, not specified.

    Layerre uses two auth methods: static API keys (create a lyr_ key at layerre.com/app/api-keys and send it as Authorization: Bearer) for the REST API and headless MCP, and OAuth 2.1 with PKCE for the hosted MCP server, with the site noting OAuth does not yet cover the public REST API. HTTP message signatures appear only as a JWKS directory for Web Bot Auth verification, not as a documented way to authenticate API calls. On rotation, auth.md says only to rotate compromised keys in the dashboard and revoke OAuth clients via the authorization server; it does not say whether old keys stay valid during rotation, so zero-downtime rotation is not documented.

Fix

Add a rotation procedure to /auth.md stating whether a new lyr_ key can run alongside the old one and how long old keys stay valid after rotation.

HedgesLimits · high+1 pts est.

What are the actual API rate limits — requests per second and concurrent render jobs — on each paid plan?

  1. Found on
  2. Pages say

    Mentioned, not specified.

    The site does not publish requests-per-second rate limits or concurrent render job limits for any plan. What it documents instead are render credit quotas: Starter 500 renders/month ($15), Plus 2,000/month ($29), Pro 20,000/month ($99), with annual equivalents of 6,000, 24,000, and 240,000 renders, and the API reference shows a 403 'Plan limit exceeded' error when a cap is hit. The pricing page and API reference are silent on per-second throttling and concurrency caps.

Fix

Add a Rate limits section to the API docs at /docs/ stating requests-per-second and concurrent render job caps for Starter, Plus, and Pro.

HedgesPricing · high+1 pts est.

If I blow past my monthly render quota mid-cycle, do extra renders get billed automatically, get throttled, or just fail?

  1. Found on
  2. Pages say

    Mentioned, not specified.

    Layerre's pricing page sets monthly render quotas per plan (Free: 50, Starter: 500, Plus: 2,000 renders per month) but never explains what happens when you hit the cap. The site does not state whether extra renders are billed automatically, throttled, or blocked.

Fix

Add an overage policy section to /pricing stating whether renders beyond the monthly quota are billed per render, throttled, or hard-fail, with exact rates or limits.

HedgesSupport · medium+1 pts est.

What support channels come with paid plans, and how fast can I expect a response when my integration breaks?

  1. Found on
  2. Pages say

    Mentioned, not specified.

    Layerre's pricing page lists support by plan: Free gets basic email support, Starter gets priority email support, Plus gets 'priority support with faster response', and Pro gets 'dedicated priority support'. The site never states an actual response time or SLA, and for Plus and Pro it does not name the support channel beyond 'priority support'. So paid plans clearly buy faster and more dedicated help, but no published speed figure exists anywhere.

Fix

Add to /pricing the support channel and a target response time for each plan, e.g. Starter: email within 24h, Plus: 8h, Pro: dedicated channel within 4h.

HedgesTechnical · medium+1 pts est.

Do you support webhooks or async callbacks when a batch render finishes, or do I have to poll the API for job status?

  1. Found on
  2. Pages say

    Mentioned, not specified.

    You should not need to poll for single renders: Layerre's API is synchronous, described on the /compare/layerre-vs-canva-api page as rendering Canva templates 'in one API call on any plan' and listed in the glossary as a 'synchronous REST API'. The site does not say whether Layerre supports webhook or async callbacks when a batch render finishes. Its webhook mentions are generic glossary content about integration patterns, or the 'No webhooks' limitation of Canva Bulk Create on the FAQ page, not a statement about Layerre's own API.

Fix

Add a 'Webhooks' section to /docs/ stating whether Layerre sends callbacks when renders finish, or confirm every render is synchronous and returns the image in the response.

HedgesLimits · low+1 pts est.

How long are generated files kept on your servers after rendering, and can I deliver outputs to my own S3 bucket?

  1. Found on
  2. Pages say

    Mentioned, not specified.

    The site does not state how long generated files are kept after rendering; the pricing page only says every plan includes 'Asset storage for generated designs' with no retention period. It also does not mention S3 or any customer owned storage destination; the delivery routes listed are API access plus Make, Zapier, and n8n integrations.

Fix

Add a file retention and export section to layerre.com/limitations/ stating how many days generated files are kept and whether outputs can be delivered to a customer S3 bucket.

Answered4Getting started, Pricing, Integration and 1 moreShowHide

  • Is there a free trial or sandbox API key I can use to test the render API before committing to a paid plan?

    Yes. The pricing page lists a permanent Free plan at $0 with 50 renders per month that includes API access, so you can test the render API without paying; no separate sandbox key or time-limited trial is mentioned. To start, create an account, generate a key (lyr_…) at layerre.com/app/api-keys, and call https://api.layerre.com/v1 with a Bearer header, as described on the auth page.

    Found on /pricing.md › Monthly plans › Free

  • How many renders or API credits come with each pricing tier, and what's the entry-level monthly cost?

    Layerre prices by render credits: Free is $0 with 50 renders/month, Starter is $15/month with 500 renders, Plus is $29/month with 2,000 renders, and Pro is $99/month with 20,000 renders. The entry-level paid tier is Starter at $15/month. Annual plans cost $150 for Starter (6,000 renders/year), $290 for Plus (24,000/year), and $990 for Pro (240,000/year).

    Found on /pricing.md

  • Does each Zapier or Make action consume one render credit, or are multi-step automations metered differently?

    No. Layerre meters by render operations, not by automation steps: the pricing page states each template import counts as one render and each variant generated counts as one render, and llms.txt confirms billing uses render credits on exactly that basis. Make, Zapier, and n8n are listed as included integrations on every plan with no per-action charges, so a multi-step Zap or Make scenario consumes credits only for the Layerre imports and variants it triggers, not per action or per step.

    Found on /pricing.md

  • I already use Canva's built-in Bulk Create — what can Layerre do that Bulk Create can't, and how much work is it to migrate my existing templates?

    Layerre runs the same Canva templates through a REST API with no ~100-variant CSV cap, supports color and font swaps beyond Bulk Create's text and image changes, and adds Zapier, n8n, and Google Sheets triggers for recurring automation, per /compare/layerre-vs-canva-bulk-create and /faq/canva-bulk-create-limits. Migration effort is described as low: Layerre imports your existing Canva design, keeps designers in Canva, and you can start generating via API in minutes on a free tier, with a dedicated guide at /faq/how-to-migrate-from-canva-bulk-create-to-layerre/.

    Found on /faq/canva-bulk-create-limits › What are the limits of Canva Bulk Create?

Agent access

1 of 16 fail · 15 pass

Files and settings agents look for

FailsIdentity · Recommended+2 pts est.

Organization schema

Observed

homepage has 1 JSON-LD block, none an Organization with a name

Fix

Add Organization JSON-LD (name, URL, logo) to your homepage head.

Download organization.json from this audit, check the name and logo, and paste it into a ld+json script tag.

Schema.org ↗
Passing15robots.txt, sitemap.xml, llms.txt and 12 moreShowHide

  • robots.txt

    GET /robots.txt → 200 text/plain (1,459 characters)

  • sitemap.xml

    sitemap found at /sitemap.xml

  • llms.txt

    /llms.txt has an H1 and 1,849 characters of text; first link https://layerre.com/.well-known/api-catalog → 200 application/linkset+json

  • AI crawler access

    robots.txt names no AI crawlers and does not block all crawlers from /

  • Content signal

    robots.txt has Content-Signal: ai-train=no, search=yes, ai-input=yes

  • Pages load cleanly

    228 of 228 crawled pages returned content (100.0%; needs over 95%)

  • Markdown on request

    Accept: text/markdown → 200 text/markdown; Vary: Accept

  • Server-rendered text

    raw homepage HTML has 8,874 visible characters before JavaScript runs (needs 500)

  • MCP server card

    found /.well-known/mcp/server-card.json → 200 application/json

  • OpenAPI spec

    found /openapi.json → 200 application/json

  • WebMCP

    /.well-known/webmcp.json found but lists no tools; homepage HTML has WebMCP markers

  • Canonical URL

    homepage canonical: https://layerre.com

  • Meta description

    meta description is 49 characters

  • Page language

    <html lang="en">

  • Sitemap dates

    209 of 209 sitemap entries have <lastmod> (100.0%; needs at least 80%)

Not applicable3Payment docs, Webhook docs, Auth docsShowHide

  • Payment docs

    site category is not commerce

  • Webhook docs

    site category is not commerce

  • Auth docs

    site category is not commerce

Observed, not scored93 fail · not in the score yetShowHide

  • AI agent accessPass

    robots.txt allows all 10 search and user AI bots on /. training and mixed-use tokens (0 points): all 6 allowed

  • Reachable by agentsPass

    SitedexBot homepage fetch (/) → 200 text/html; no challenge

  • Real 404sFails

    GET /sitedex-probe-404/e8b1c4d2/missing (a page that does not exist) → 200 text/markdown: a soft 404 (success status for a missing page)

    Return a real 404 status for pages that do not exist, not a 200 page that says “not found” or a redirect to your homepage. Agents read the status code to tell a missing page from a real one.

  • Open Graph tagsPass

    homepage has all four required Open Graph tags (og:title, og:type, og:image, og:url)

  • Organization contact detailsNot applicable

    no Organization JSON-LD with a name on the homepage

  • JSON-LD parsesPass

    1 of 1 JSON-LD block on the homepage parse as JSON

  • About, contact and privacy pagesPartly passes

    no about page crawled; no contact page crawled; privacy /privacy (13,164 bytes) (needs 500+ bytes of text each)

    Publish an about page, a contact page and a privacy page with real text (about 500 characters of text or more each), and link them from your site so a crawl finds them.

  • Agent guidance in llms.txtFails

    /llms.txt has no section that says when to use the site or gives agent instructions (heuristic: an H2-H6 heading such as “When to use” or “Instructions for agents”, with text under it)

    Add a section to /llms.txt that tells an agent when to use your site, for example a “## When to use” heading with a few lines on what the site is for and what it is not for.

Claim layerre.com

Free · full crawl · score history

Claim site

Score your site

Free · results in minutes

All 40 SaaS sites

Scoring v2 · checks v2 · Oct 29, 2026

How this is scored

Score

  • Buyer questions70%
  • Agent access30%

Buyer questions

  • Answeredanswered from your pages
  • Hedgesmentioned, not specified
  • Contradictspages disagree
  • Goes silentno page answers it

Agent access

16 checks count toward the score. Checks marked not scored are recorded and shown, and do not move the score yet.

Estimates

+N pts est. is the gain to this score if that one item is fixed alone. Estimates do not add up.

Tiers

  • Agent-Native80 to 100
  • Agent-Ready60 to 79
  • Agent-Accessible40 to 59
  • Basic Presence20 to 39
  • Agent-Unreadable0 to 19

Scoring v2 · checks v2