Zapier

Last scanned docs.zapier.comMintlify15 pages tested

AI agents can find, read and use these docs well. Zapier scores 93 out of 100 (grade A), passing 21 of 27 checks. 6 still need work.

Fix it with Documentation.AI

Get this report by email

We send the full report to your inbox. Nothing on this page needs an email.

Use your work email. We only send what you asked for, and every email has an unsubscribe link.

Developer docs

Kind of site

21/27

Checks passed

3

Partly passed

3

Failed

Access

Content discoverability5 passed2 partly
  • llms.txt fits in an agent's context

    llms.txt is 54,963 characters (between 50,000 and 100,000; consider splitting)

    Your llms.txt is 54,963 characters, which may be truncated on some agent platforms. If it grows further, split into nested llms.txt files with a root index under 50,000 characters.

    Check your fix: curl -s https://docs.zapier.com/llms.txt | wc -c prints less than 50000.

  • llms.txt links work

    All 15 same-origin sampled links resolve (358 total links) (4 external links also failed; may be bot-detection or rate-limiting)

    4 of 30 links in your llms.txt return errors. Audit and fix or remove broken URLs to prevent agents from hitting dead ends.

    Check your fix: Every link in llms.txt returns 200 when fetched.

  • llms.txt exists

    llms.txt found at https://docs.zapier.com/llms.txt

  • llms.txt follows the standard structure

    llms.txt follows the proposed structure (H1, blockquote, heading-delimited link sections)

  • llms.txt links point to Markdown

    15/15 same-origin sampled links point to markdown content (100%) (21 external links excluded)

  • Pages point agents to llms.txt

    llms.txt directive found in HTML of all 15 sampled pages, near the top of content

  • Markdown pages point agents to llms.txt

    llms.txt directive found in markdown of all 15 sampled pages, near the top of content

Markdown availability2 passed
  • Pages are available as Markdown

    15/15 sampled pages support .md URLs (100%)

  • Server returns Markdown when asked

    15/15 sampled pages support content negotiation (100%)

Page size and truncation4 passed
  • Content is in the HTML without JavaScript

    All 15 sampled pages contain server-rendered content

  • Markdown pages fit in context

    All 15 pages under 50K chars (median 4K, max 20K)

  • HTML pages fit in context

    All 15 sampled pages under 50K chars (median 473K HTML โ†’ 10K markdown (98% boilerplate))

  • Content starts near the top

    Content starts within first 10% on all 15 sampled pages (median 2%)

Content structure2 passed
  • Headings inside tabs name their variant

    1 page(s) with tabs found, but no section headers inside tab panels to evaluate

  • Tabs don't bloat the page

    1 tab group(s) across 1 of 15 sampled pages; all serialize under 50K chars

  • Code blocks are well-formed

    All 26 code fences properly closed across 16 pages

URL stability2 passed
  • Missing pages return a real 404

    All 15 sampled pages return proper error codes for bad URLs

  • Redirects stay on the same host

    All 1 redirect(s) across 15 sampled pages are same-host HTTP redirects

Content health1 passed1 failed1 partly
  • Markdown matches the HTML page

    1 of 15 pages have substantive content differences between markdown and HTML (avg 4% missing)

    1 pages have substantive content differences between markdown and HTML (avg 4% missing). If unintentional, agents are getting outdated content; regenerate markdown from source or fix the build pipeline.

  • llms.txt covers the whole site

    llms.txt covers 342/395 sitemap doc pages (87%); 53 missing; 24 llms.txt links not in sitemap (may indicate stale links or incomplete sitemap)

    Your llms.txt covers 87% of your site's pages (80-95% is warn). 53 live pages are not represented in the index.

  • Cache headers allow timely updates

    All 16 endpoints have appropriate cache headers

Authentication and access1 passed
  • Gated docs offer another way in

    All docs pages are publicly accessible; no alternative access paths needed

  • Docs are readable without logging in

    All 15 sampled pages are publicly accessible

Crawler access2 passed
  • Crawlers and AI assistants may read the docs

    robots.txt lets Googlebot, Bingbot, OAI-SearchBot, PerplexityBot, Claude-SearchBot and Claude-User read the docs.

  • Sitemap lists the docs pages

    The sitemap at https://docs.zapier.com/sitemap.xml lists 331 of the 340 docs pages found through llms.txt and page links.

Freshness

Maintenance2 passed1 failed
  • Links and section anchors work

    3 of 58 references checked on the sampled pages are broken: 0 links and 3 section anchors. 1 more could not be verified (timeouts or blocked requests) and is not counted.

    Fix or remove the broken links, redirect moved pages to their new address, and restore or retarget section anchors. Agents follow links to gather context, and a dead link ends that path.

    Check your fix: Every link on https://docs.zapier.com/integrations/build-cli/overview#shorthand-http-requests (no such section) linked from https://docs.zapier.com/integrations/build-cli/faqs returns 200, and every #section link points at an element with that id.

  • Pages say when they were last changed

    14 of 15 sampled pages state when they were last changed, and 1 more has a date only in the sitemap.

  • Sitemap entries still exist

    All 10 sitemap entries sampled still exist.

Consistency with the API spec1 failed
  • Endpoints in the docs exist in the API spec

    2 of 2 endpoints mentioned in the docs are not in https://docs.zapier.com/powered-by-zapier/api-reference/promotions-openapi.yaml.

    Update either the docs or the OpenAPI file so they describe the same endpoints. Agents trust the spec when generating code, and a mismatch produces calls that fail.

    Check your fix: Every METHOD /path the docs mention appears under paths in the OpenAPI file.

CurrencyNot applicable
  • Deprecated operations are marked as such

    https://docs.zapier.com/powered-by-zapier/api-reference/promotions-openapi.yaml marks no operation as deprecated, so there is nothing to compare.

Additional checks

Not part of the score: optional extras that help agents use your docs.

  • MCP server is discoverable

    An MCP server answers at https://docs.zapier.com/mcp.

  • llms-full.txt is available

    llms-full.txt found at https://docs.zapier.com/llms-full.txt (2,478,535 characters).

  • Agent skills are published

    1 agent skill published at https://docs.zapier.com/.well-known/agent-skills/index.json.

About this scan

Scanned
Oct 21, 2026
Pages tested
15 of 361 found
Platform
Mintlify
Kind of site
Developer docs
AFDocs score, on its own
96 (A), 17 of 23 checks pass
  • Based on 15 sampled pages, chosen deterministically from the sitemap and llms.txt. Pages outside the sample were not read.
  • Pages were fetched without running JavaScript, the way most AI agents read the web.
  • robots.txt stopped the scanner from reading 1 URL; checks that needed them are unverified.
  • Answerability, where an AI agent answers real questions written from these pages, runs in the open-source scanner with your own API key. This web score is made of Access and Freshness.

Methodology 2026-09.6 ยท AFDocs 0.20.0

Pages we sampled (15)
  • https://docs.zapier.com/
  • https://docs.zapier.com/integrations/build-cli/faqs
  • https://docs.zapier.com/integrations/build/error-array-expected
  • https://docs.zapier.com/integrations/build/subdomain-validation
  • https://docs.zapier.com/integrations/manage/change-perform
  • https://docs.zapier.com/integrations/manage/versions
  • https://docs.zapier.com/integrations/publish/partner-program
  • https://docs.zapier.com/integrations/reference/dynamic-dropdown-tutorial
  • https://docs.zapier.com/mcp/get-started/connect/claude-small-business
  • https://docs.zapier.com/mcp/get-started/connect/toolhouse
  • https://docs.zapier.com/mcp/overview/usage
  • https://docs.zapier.com/powered-by-zapier/api-reference/authentication#retrieving-a-user-access-token
  • https://docs.zapier.com/powered-by-zapier/api-reference/zap-templates/get-zap-templates
  • https://docs.zapier.com/powered-by-zapier/running-actions/action-run-callbacks
  • https://docs.zapier.com/sdk/permissions

Show your score

Add the badge to your docs or README. It updates each time the site is scanned.

Agent Readiness Score badge

Markdown

[![Agent Readiness Score: 93 (A)](https://documentation.ai/agent-score/badge/zapier.svg)](https://documentation.ai/agent-score/zapier)

HTML

<a href="https://documentation.ai/agent-score/zapier"><img src="https://documentation.ai/agent-score/badge/zapier.svg" alt="Agent Readiness Score: 93 (A)" height="20"></a>

Agent-ready docs by default

Documentation.AI sites ship with llms.txt, Markdown pages, a sitemap and an MCP server, and our agent keeps the content current.

Live in under 5 min ยท No credit card required