Startup Legal & Incorporation Arena
Clerky vs LegalZoom
Clerky wins · 15–5 (7 drawn)
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
Agent access
ai-native userPoint an agent at llms.txt or agent-oriented docs
weight 2 · round to ClerkyClerky's developer docs site serves a valid llms.txt (HTTP 200) with structured links to markdown-formatted docs pages, confirmed by direct probe evidence, satisfying the ability to point an agent at agent-oriented documentation. missing for 10: independent third-party confirmation of an agent successfully consuming the llms.txt in practice.
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.clerky.com/llms.txt - [Lifecycle](https://developers.clerky.com/getting-started/lifecycle/ind…”
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
A direct probe confirms LegalZoom serves a live llms.txt file at /llms.txt with AI-crawler guidance content, showing the site is agent-discoverable. Missing for 10: no visibility into the full content/structure of the llms.txt beyond the header, and no independent community confirmation of its usefulness for agents.
- [probe] “PROBE llms.txt: HTTP 200 at https://www.legalzoom.com/llms.txt ################################################################ # :blue_book…”
ai-native userDrive the product through a documented public API
weight 3 · round to ClerkyClerky publishes real developer documentation for a Partner API (developers.clerky.com, discoverable via llms.txt) covering document-set lifecycle, form schemas, and endpoints like POST /v1/document_sets and GET forms, which is genuine documented programmatic access. However, the docs themselves state OAuth-based authentication is 'coming soon' and not yet live, meaning the API isn't fully operational for external partner integration yet, and scope is limited to Delaware C-Corp formations only. Missing for 10: live/functional authentication flow, evidence of broader API scope, and independent developer reports of successful integration.
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scop…”
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.clerky.com/llms.txt - [Lifecycle](https://developers.clerky.com/getting-started/lifecycle/ind…”
LegalZoomnone0/10No evidence of any documented public API for LegalZoom; evidence only covers service offerings, pricing, and an llms.txt crawler guidance file, none of which constitute an API for programmatic control. Missing for 10: any API documentation, authentication scheme, endpoints, or SDK enabling programmatic/agentic use.
- [probe] “PROBE llms.txt: HTTP 200 at https://www.legalzoom.com/llms.txt ################################################################ # :blue_book…”
Agentic features
ai-native userGet AI-generated insights and suggestions from my data inside the product
weight 2 · round to LegalZoomClerkynone0/10Clerky is a legal document/formation platform with an MCP server and partner API for workflow automation, but there is no evidence of AI-generated insights or suggestions surfaced from the user's own data (e.g., analytics, recommendations, anomaly detection) inside the product. The MCP server exposes tools for AI assistants to act on data, not the product itself generating insights.
- [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
- [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”
The only AI-related capability found is 'AI-powered creation of meeting minutes for official record keeping,' which generates content rather than surfacing insights or suggestions derived from the user's own data. There's no evidence of AI-driven analytics, recommendations, or personalized suggestions based on a user's business data. Missing for 10: dashboard-level AI insights, data-driven suggestions/recommendations, any first-party or independent account of AI analyzing user data to produce actionable insights.
- [claimed-docs] “AI-powered creation of meeting minutes for official record keeping”
ai-native userDelegate tasks to a built-in AI assistant inside the product
weight 3 · round drawnClerkynone0/10Evidence shows Clerky exposes an MCP server so external AI assistants (Claude, ChatGPT) can call into Clerky's tools, but this is the reverse of a built-in assistant inside Clerky's own product that a user delegates tasks to. No evidence of any in-app AI assistant/chat feature for delegating formation, hiring, or document tasks.
- [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
- [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”
LegalZoomnone0/10Evidence shows only a narrow 'AI-powered meeting minutes' feature and an llms.txt file for crawler guidance, not a built-in assistant that users can delegate broader tasks to. No documentation of a conversational AI agent, task delegation interface, or agentic assistant within the product.
- [claimed-docs] “AI-powered creation of meeting minutes for official record keeping”
- [probe] “PROBE llms.txt: HTTP 200 at https://www.legalzoom.com/llms.txt ################################################################ # :blue_book…”
ai-native userOperate the product with natural-language commands
weight 2 · round to ClerkyClerky ships a live MCP server (mcp.clerky.com) enabling Claude/ChatGPT and other AI assistants to invoke Clerky tools with team-scoped access, which is the mechanism for natural-language operation; a probe confirms the endpoint is real and OAuth-gated rather than vaporware. Missing for 10: no hands-on transcript or independent report of actually issuing natural-language commands through the MCP tools, and no evidence of a broader in-app conversational/NL command interface beyond the MCP integration.
- [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
- [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.clerky.com/llms.txt - [Lifecycle](https://developers.clerky.com/getting-started/lifecycle/ind…”
LegalZoomnone0/10There is no evidence of any natural-language command interface, chat-based operation, or AI agent control surface for LegalZoom's product; the llms.txt probe only indicates AI-crawler guidance for content indexing, not user-facing natural-language operation. missing for 10: any natural-language command interface, chatbot/agent control of the product, API or automation surface, evidence of AI-native operability beyond crawler guidance.
- [probe] “PROBE llms.txt: HTTP 200 at https://www.legalzoom.com/llms.txt ################################################################ # :blue_book…”
Api quality
ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)
weight 2 · round drawnClerkynone0/10Clerky has a documented Partner API with REST endpoints and JSON schema forms, but explicit probes for OpenAPI/Swagger spec files (openapi.json, swagger.json, .well-known/openapi.json) all returned 404, and no docs page offers a downloadable machine-readable spec.
- [probe] “PROBE openapi: all candidate paths 404 (https://handbooks.clerky.com/openapi.json, https://handbooks.clerky.com/swagger.json, https://handbo…”
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
Compliance registered agent — stories about compliance registered agent in this arenaCompliance registered agent
Stories about compliance registered agent in this arena
Compliance
founderFile annual reports and franchise tax on time through the platform
weight 2 · round to LegalZoomClerkynone0/10No evidence anywhere in the pack mentions annual report filing, franchise tax filing, registered agent services, or compliance deadline tracking; Clerky's documented scope is formation, equity, hiring, banking, and IRS forms only.
LegalZoom docs show registered-agent and annual-report services with deadline reminders and real-time compliance status alerts (docs-14, docs-16), which support timely annual report filing, but there's no explicit evidence of franchise tax filing/payment services on the platform. Missing for 10: franchise tax filing/payment capability, evidence of actual on-time filing outcomes, and independent/hands-on corroboration of the annual report filing process working as described.
- [claimed-docs] “Get an alert as soon as official mail arrives for you—plus, get reminders when annual report deadlines are approaching.”
- [claimed-docs] “Real-time notifications about your compliance status, upon receipt of data from your state filing office”
- [claimed-docs] “All paperwork needed to switch RAs completed for you, plus state fees covered”
legal-ops leadSee a compliance calendar of upcoming filing deadlines and get reminders before each one
weight 2 · round to LegalZoomClerkynone0/10No evidence in the pack of any compliance calendar, filing-deadline tracking, or reminder feature; Clerky's evidence covers document formation, collaboration, task assignment, and API/MCP integrations but nothing about deadline tracking or reminders.
LegalZoom's registered agent and annual report services document reminders for annual report deadlines and real-time compliance status notifications, which meets the 'reminders before deadlines' part of the story. However, there's no evidence of a unified compliance calendar view aggregating multiple filing deadlines for legal-ops oversight. Missing for 10: dedicated calendar UI/dashboard listing all upcoming filings, evidence of reminders for filings beyond annual reports (e.g., licenses, permits), and independent confirmation the reminder system works reliably.
- [claimed-docs] “Get an alert as soon as official mail arrives for you—plus, get reminders when annual report deadlines are approaching.”
- [claimed-docs] “Real-time notifications about your compliance status, upon receipt of data from your state filing office”
- [claimed-docs] “A personalized dashboard available to you 24/7”
founderUse the platform as my registered agent and receive scanned legal mail and service of process digitally
weight 2 · round to LegalZoomClerkynone0/10No evidence anywhere in the pack that Clerky offers registered agent services or digital mail/service-of-process scanning; its documented scope is document generation, e-signature, IRS filings, banking, and API/MCP integrations. Registered agent service is a plausible offering for a startup-formation platform, so absence of evidence yields 'none' rather than 'na'.
LegalZoom's registered agent service page confirms core RA functionality: alerts when official mail arrives, unlimited cloud storage for documents, and assistance switching agents, which supports the founder-story premise of receiving legal mail digitally. However, there's no explicit documentation confirming scanned copies of service of process specifically or digital delivery mechanics (scan speed, dashboard viewing), and no independent/hands-on corroboration of the mail-forwarding experience. missing for 10: explicit mention of 'service of process' handling, description of scanning/digitization process, independent user reports confirming reliability of mail alerts.
- [claimed-docs] “All paperwork needed to switch RAs completed for you, plus state fees covered”
- [claimed-docs] “Get an alert as soon as official mail arrives for you—plus, get reminders when annual report deadlines are approaching.”
- [claimed-docs] “Unlimited cloud storage for all your business documents”
Compliance agentic
ai-native userDelegate an annual report or compliance filing to an agent that prepares it through the platform with minimal human input
weight 2 · round to ClerkyClerky offers a remote MCP server and Partner API that let an AI assistant interact with document sets, forms, and workflow state (clerky-docs-19/20/22), and IRS forms can be completed and submitted online (clerky-docs-5/15), suggesting some agent-driven compliance work is possible. However, the probe shows the MCP tools are read-only with team-scoped OAuth access (clerky-probe-5), and there is no evidence of an actual 'annual report' or ongoing compliance-filing product, nor of an agent completing filings end-to-end with minimal human input. missing for 10: evidence of annual report/compliance-filing capability specifically, evidence the MCP/API can autonomously submit filings (not just read/collect data), and confirmation that human sign-off isn't required at each step.
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
- [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”
- [claimed-docs] “Use Clerky to complete IRS forms and submit them to the IRS, completely online. No need for a fax machine.”
- [claimed-docs] “Use Clerky to complete IRS forms and submit them to the IRS, completely online. No need for a fax machine. 100% in-house, not outsourced.”
LegalZoomnone0/10LegalZoom offers annual-report reminders, compliance notifications, and registered-agent services, but all evidence points to a human-driven web platform (dashboard, live specialists, attorney consults) with no API, agent integration, or documented way for an autonomous agent to actually execute a filing with minimal human input; the llms.txt probe only shows AI-crawler guidance, not an agentic execution channel.
- [claimed-docs] “Get an alert as soon as official mail arrives for you—plus, get reminders when annual report deadlines are approaching.”
- [claimed-docs] “Real-time notifications about your compliance status, upon receipt of data from your state filing office”
- [claimed-docs] “A personalized dashboard available to you 24/7”
- [claimed-docs] “Connect with a business or personal services specialist in under two minutes to help get you to the solutions you need.”
- [probe] “PROBE llms.txt: HTTP 200 at https://www.legalzoom.com/llms.txt ################################################################ # :blue_book…”
Contract lifecycle — stories about contract lifecycle in this arenaContract lifecycle
Stories about contract lifecycle in this arena
Clm agentic
ai-native userHave an agent monitor contract renewals and deadlines through the product's API and act before they lapse
weight 2 · round drawnClerkynone0/10Clerky's API and MCP server are scoped to formation document-set workflows (create, fill forms, sign, poll lifecycle state) — there is no evidence of tracking contract renewal dates, deadline alerts, or proactive lapse-prevention actions via the API or MCP tools.
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
- [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”
LegalZoomnone0/10No evidence of an API for agents to monitor contracts or deadlines; only human-facing dashboard alerts and email/reminder notifications (registered agent alerts, compliance status alerts) are mentioned, with no programmatic access. Missing for 10: any public API/webhook documentation, agent integration examples, or developer-facing endpoints for contract lifecycle monitoring.
- [claimed-docs] “Get an alert as soon as official mail arrives for you—plus, get reminders when annual report deadlines are approaching.”
- [claimed-docs] “Real-time notifications about your compliance status, upon receipt of data from your state filing office”
- [claimed-docs] “A personalized dashboard available to you 24/7”
Clm authoring
legal-ops leadDraft, negotiate, and redline contracts in a controlled workflow instead of email attachments
weight 3 · round to ClerkyClerky offers real-time collaboration, attorney review/comment, customization of key terms, and full audit logging of document set changes, which supports a 'controlled workflow instead of email attachments' for its own formation/equity documents. However, there is no evidence of redlining, track-changes, or multi-round negotiation with external counterparties—Clerky's workflow is field-based data entry and e-signature for standardized startup legal docs, not general contract redlining. Missing for 10: explicit redline/track-changes tooling, version comparison, negotiation cycles with external parties, and support for arbitrary (non-template) contracts.
- [claimed-docs] “We log every change anyone makes to a document set or workspace, so you can always see who was responsible for what.”
- [claimed-docs] “you can easily loop in your attorney to have them review and comment on the information you're entering.”
- [claimed-docs] “Our software makes it easy to invite other people to collaborate on a document set, in real-time.”
- [claimed-docs] “Our software makes it easy to invite other people to collaborate on a document set, in real-time. Rest easy knowing everyone is looking at t…”
- [claimed-docs] “Our software makes it easy to customize the key terms of the legal paperwork you're working on.”
LegalZoomnone0/10Evidence shows LegalZoom offers business formation, registered agent, compliance, and template document services, but nothing about a contract drafting/negotiation/redlining workflow, version control, or collaborative markup replacing email. Missing for 10: contract drafting workflow, redlining/version comparison tools, negotiation collaboration features, audit trail of changes.
Clm repository
legal-ops leadStore executed contracts in a searchable repository with key terms and metadata extracted
weight 2 · round drawnClerkynone0/10Clerky is a formation/document-generation tool; evidence covers document sets, activity logs, and collaboration but nothing about a searchable repository of executed contracts with extracted key terms/metadata—no full-text search, term extraction, or metadata tagging is described anywhere in the pack.
LegalZoomnone0/10Evidence shows LegalZoom offers unlimited cloud storage for business documents (legalzoom-docs-15) but nothing about a searchable repository with automated extraction of key contract terms/metadata—no clause extraction, no contract search/filtering, no metadata tagging capability is described anywhere in the evidence pack.
- [claimed-docs] “Unlimited cloud storage for all your business documents”
Document automation — stories about document automation in this arenaDocument automation
Stories about document automation in this arena
Doc api
ai-native userHave an agent draft an NDA and route it for signature end-to-end via the product's API or MCP server
weight 3 · round drawnClerkynone0/10Clerky's Partner API and MCP server are real and documented, but the API explicitly states it 'currently supports Delaware C-Corporation formations' only, and the MCP server tools are scoped to Clerky's startup-formation document sets (cap tables, safes, stock plans) — there is no evidence of NDA drafting or NDA e-signature routing via either channel.
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
- [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”
LegalZoomnone0/10No evidence of an API or MCP server for drafting/routing NDAs; the evidence pack only covers business-formation product pages, community pricing complaints, and an llms.txt crawler-guidance file—none showing programmatic document drafting or e-signature routing capability. Missing for 10: any API/MCP endpoint, NDA drafting automation, e-signature routing integration.
- [probe] “PROBE llms.txt: HTTP 200 at https://www.legalzoom.com/llms.txt ################################################################ # :blue_book…”
developerGenerate, populate, and send legal documents programmatically through a documented API
weight 3 · round to ClerkyClerky publishes a documented Partner API with concrete lifecycle steps (create document set, GET forms with json_schema, POST values, poll state) covering document generation and population (clerky-docs-19, clerky-docs-20). However, the API currently only supports Delaware C-Corp formations, OAuth-based authentication is explicitly stated as 'coming soon' rather than live (clerky-docs-21), and 'sending' is really 'user signs on Clerky' rather than a programmatic send step, so the story is only partially realized in production. Missing for 10: live/production authentication for partners, broader document-type coverage beyond formations, and independent/hands-on evidence of a working end-to-end integration.
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scop…”
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.clerky.com/llms.txt - [Lifecycle](https://developers.clerky.com/getting-started/lifecycle/ind…”
LegalZoomnone0/10No evidence of any developer API, SDK, or programmatic document generation/send capability—only consumer-facing web forms and service descriptions are documented. missing for 10: public API reference, authentication/SDK docs, programmatic document population/send endpoints, developer sandbox or examples.
Equity fundraising — stories about equity fundraising in this arenaEquity fundraising
Stories about equity fundraising in this arena
Fundraising
founderGenerate and sign SAFEs or convertible notes on standard terms without drafting from scratch
weight 3 · round to ClerkyClerky's core startup product explicitly supports issuing SAFEs and convertible notes on standard forms with customizable key terms, collaborative editing, attorney review, and e-signature—removing the need to draft from scratch. Community feedback corroborates ease of use and frictionless process for founders using Clerky's paperwork workflows. Missing for 10: independent hands-on account of actually generating/signing a SAFE end-to-end and specifics on which standard SAFE variants (YC, pre/post-money) are supported.
- [claimed-docs] “Issue safes or convertible notes. Hire employees, consultants, and advisors, and issue stock or stock options as equity compensation.”
- [claimed-docs] “Our software makes it easy to customize the key terms of the legal paperwork you're working on.”
- [claimed-docs] “you can easily loop in your attorney to have them review and comment on the information you're entering.”
- [claimed-docs] “Our software makes it easy to invite other people to collaborate on a document set, in real-time.”
- [community] “Wow, this is great. Props to the Clerky team. If this had existed in 2015 we would have used it, instead we paid a few thousand extra.”
- [community] “We were among the first companies to use this product at Crowdbotics... the process was almost totally frictionless and Clerky's support was…”
LegalZoomnone0/10Evidence pack covers business formation, registered agent, compliance, and bookkeeping services but contains no mention of SAFEs, convertible notes, equity fundraising documents, or investor-facing templates. This is a plausible axis for a legal-document generation service, but no evidence shows LegalZoom supports generating/signing SAFEs or convertible notes.
Governance
legal-ops leadPrepare board consents and resolutions and collect approvals online
weight 2 · round to ClerkyClerky's docs describe document-set collaboration, inviting co-founders/attorneys to review and comment in real-time, and issuing stock/options (which typically requires board approval) — these features generally support drafting and collecting sign-off on corporate paperwork online. However, no evidence explicitly names 'board consents' or 'resolutions' as a document type or confirms an approval-workflow specifically for board actions. Missing for 10: explicit mention of board consent/resolution templates, a dedicated approval/e-signature workflow for board members, and independent confirmation that board-level approvals are collected through the platform.
- [claimed-docs] “Issue safes or convertible notes. Hire employees, consultants, and advisors, and issue stock or stock options as equity compensation.”
- [claimed-docs] “Our software makes it easy to invite other people to collaborate on a document set, in real-time.”
- [claimed-docs] “Our software makes it easy to invite other people to collaborate on a document set, in real-time. Rest easy knowing everyone is looking at t…”
- [claimed-docs] “you can easily loop in your attorney to have them review and comment on the information you're entering.”
- [claimed-docs] “We've built features that let you easily assign tasks to co-founders and work on everything together.”
- [community] “Clerky gives me management tools (including the post-incorporation package: Fundraising, Hiring and Maintenance) although this does not give…”
Hiring
legal-ops leadRun hiring and equity paperwork — offer letters, confidentiality/IP agreements, and option grants — through the platform
weight 2 · round to ClerkyClerky's own product docs explicitly cover hiring paperwork (offer/hiring workflows), confidentiality/IP agreements implied via founder/employee onboarding docs, and equity issuance (stock, stock options, safes, convertible notes) via a stock plan, plus attorney oversight/collaboration features for legal-ops review. Community reviews corroborate real-world use of the hiring/fundraising/maintenance packages. Missing for 10: explicit mention of confidentiality/IP agreement templates by name and independent case studies detailing legal-ops workflows specifically.
- [claimed-docs] “Issue safes or convertible notes. Hire employees, consultants, and advisors, and issue stock or stock options as equity compensation.”
- [claimed-docs] “Adopt a stock plan to easily issue restricted stock or stock options to employees, consultants, and advisors.”
- [claimed-docs] “Forming a startup on Clerky enables access to a legal dashboard that makes it easy to do additional legal paperwork.”
- [claimed-docs] “you can easily loop in your attorney to have them review and comment on the information you're entering.”
- [community] “Clerky gives me management tools (including the post-incorporation package: Fundraising, Hiring and Maintenance) although this does not give…”
LegalZoomnone0/10The evidence pack covers business formation, registered agent, annual reports, and general legal document access, but contains no mention of offer letters, employee confidentiality/IP assignment agreements, or stock option grant paperwork—the core equity-fundraising/HR-ops artifacts in this story.
Esignature flows — stories about esignature flows in this arenaEsignature flows
Stories about esignature flows in this arena
Esign
founderSend a document for legally binding e-signature to multiple recipients with routing
weight 3 · round to ClerkyClerky's document sets clearly involve multiple signers (collaborators, attorneys, co-founders) and a signing workflow (clerky-docs-13/17, clerky-docs-19/20), but this is signing within Clerky's own fixed legal document templates rather than a general-purpose 'send any document for signature with custom multi-recipient routing' capability. No evidence describes configurable signing order, roles, or routing logic for recipients. Missing for 10: explicit documentation of routing/sequencing controls, ability to send arbitrary documents (not just Clerky-generated ones) for signature, and independent confirmation of multi-recipient routing behavior.
- [claimed-docs] “Our software makes it easy to invite other people to collaborate on a document set, in real-time.”
- [claimed-docs] “Our software makes it easy to invite other people to collaborate on a document set, in real-time. Rest easy knowing everyone is looking at t…”
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
LegalZoomnone0/10No evidence pack items mention e-signature functionality, multi-recipient routing, or document signing workflows; all evidence is about business formation, registered agent, and compliance services. Missing for 10: any mention of e-signature feature, multi-recipient routing/workflow, or signing order/audit trail.
Incorporation — stories about incorporation in this arenaIncorporation
Stories about incorporation in this arena
Formation
founderObtain a federal EIN for my new company through the platform
weight 2 · round to ClerkyClerky explicitly advertises completing and submitting IRS forms (including EIN application, a core IRS form for new companies) fully online without fax, done in-house — clerky-docs-5/15. Community evidence corroborates general ease/friction of the incorporation process but doesn't specifically dispute the EIN step. Missing for 10: independent hands-on confirmation specifically of the EIN application step (vs. general process reviews) and detail on turnaround time.
- [claimed-docs] “Use Clerky to complete IRS forms and submit them to the IRS, completely online. No need for a fax machine.”
- [claimed-docs] “Use Clerky to complete IRS forms and submit them to the IRS, completely online. No need for a fax machine. 100% in-house, not outsourced.”
- [community] “We were among the first companies to use this product at Crowdbotics... the process was almost totally frictionless and Clerky's support was…”
LegalZoom's LLC formation package explicitly lists obtaining an EIN as part of the service, used for taxes, banking, and hiring staff. Missing for 10: dedicated EIN service documentation detailing the application process/turnaround, and independent/hands-on confirmation of EIN delivery.
- [claimed-docs] “An EIN, which is used to file taxes, open bank accounts, and build your staff”
founderIncorporate a Delaware startup end-to-end online, including the filing, bylaws, and initial board approvals
weight 3 · round to ClerkyClerky is purpose-built for online Delaware incorporation, covering formation filing, customizable bylaws/legal documents, board approvals, and post-incorporation paperwork, corroborated by positive hands-on founder accounts of using it for incorporation. missing for 10: independent verification of the full end-to-end filing-to-board-approval flow (vs marketing pages), and a documented step-by-step walkthrough showing bylaws/board consent generation explicitly.
- [claimed-docs] “Forming a startup on Clerky enables access to a legal dashboard that makes it easy to do additional legal paperwork.”
- [claimed-docs] “Our software makes it easy to customize the key terms of the legal paperwork you're working on.”
- [claimed-docs] “Issue safes or convertible notes. Hire employees, consultants, and advisors, and issue stock or stock options as equity compensation.”
- [claimed-docs] “Adopt a stock plan to easily issue restricted stock or stock options to employees, consultants, and advisors.”
- [community] “I used Clerky in 2016. I found them pleasant and easy to work with. Took the time to answer all of my questions. Prices quite reasonable.”
- [community] “We were among the first companies to use this product at Crowdbotics... the process was almost totally frictionless and Clerky's support was…”
- [community] “I love Stripe Atlas overall for fast/excellent UX, but Clerky supports PBCs and a higher degree of customization (eg useful for incorporatin…”
LegalZoom's docs confirm it can file corporation formation (S corp/C corp) online with flat fees and error correction guarantees, which covers the core 'filing' part of a Delaware startup incorporation, but there is no evidence of Delaware-specific service, bylaws drafting, or initial board resolutions/approvals being part of the package (those items are only mentioned for LLC operating agreements, not corporations). Community feedback focuses on LLC formation cost complaints, not corporate incorporation completeness. Missing for 10: Delaware-specific incorporation flow, bylaws generation, initial board consent/resolution documents, and independent verification that these are actually delivered.
- [claimed-docs] “Corporation (S corp or C corp)”
- [claimed-docs] “Raise funds by appealing to investors who may prefer corporations for the ability to offer stock.”
- [claimed-docs] “If your filing is rejected or incorrect due to our error, we'll correct it with the government agency at no additional cost to you.”
- [community] “I am a lawyer. I used Legalzoom to form a 50/50 California LLC in which I am one of the 50% people. The stakes were low, would always be low…”
founderComplete post-incorporation setup — founder stock purchases, IP assignment, and 83(b) elections — with correct standard paperwork
weight 2 · round to ClerkyClerky's docs confirm founder stock/equity issuance (clerky-docs-9, clerky-docs-16) and completing/submitting IRS forms online (clerky-docs-5, clerky-docs-15), which covers 83(b) elections, and community confirms a post-incorporation 'Maintenance' package (clerky-comm-3). However, IP assignment agreements are not explicitly named in the evidence pack, so full coverage of that specific document isn't directly confirmed. missing for 10: explicit documentation of IP assignment agreement generation, independent verification that 83(b) filings are correctly executed, and hands-on account of the full post-incorporation flow.
- [claimed-docs] “Use Clerky to complete IRS forms and submit them to the IRS, completely online. No need for a fax machine.”
- [claimed-docs] “Issue safes or convertible notes. Hire employees, consultants, and advisors, and issue stock or stock options as equity compensation.”
- [claimed-docs] “Use Clerky to complete IRS forms and submit them to the IRS, completely online. No need for a fax machine. 100% in-house, not outsourced.”
- [claimed-docs] “Adopt a stock plan to easily issue restricted stock or stock options to employees, consultants, and advisors.”
- [community] “Clerky gives me management tools (including the post-incorporation package: Fundraising, Hiring and Maintenance) although this does not give…”
LegalZoomnone0/10The evidence pack covers LLC/incorporation filing, registered agent, annual reports, and general legal document services, but contains no mention of founder stock purchase agreements, IP assignment agreements, or 83(b) election filing support — the specific post-incorporation paperwork the story asks about. Nothing in the docs, community, or probe items addresses this startup-specific stock/equity setup workflow.
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
ai-native userDo everything through the API that I can do in the UI
weight 2 · round to ClerkyClerky has a Partner API but it explicitly 'currently supports Delaware C-Corporation formations' only, a narrow subset of the 40+ products, safes, stock plans, hiring, banking integrations, and legal dashboard features described in the UI docs. OAuth authentication is also still 'coming soon,' meaning the API isn't even fully live yet, and there's no evidence of API coverage for post-formation workflows (safes, convertible notes, hiring, stock issuance, IRS filing, banking apps) that are core UI capabilities. Missing for 10: API coverage for post-incorporation products (safes, hiring, equity issuance, IRS/bank filings), live OAuth access, and evidence of parity across the 40+ advanced products.
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scop…”
- [claimed-docs] “Issue safes or convertible notes. Hire employees, consultants, and advisors, and issue stock or stock options as equity compensation.”
- [claimed-docs] “Attorney accounts get access to over 40 advanced products that are not publicly available.”
- [claimed-docs] “Apply for accounts with the most popular banks for startups. Pre-filled applications make it as easy as possible.”
LegalZoomnone0/10No evidence of a public API for LegalZoom services at all — only an llms.txt for AI crawling guidance and marketing/docs pages describing UI-based products. Missing for 10: any documented API, API authentication, endpoint coverage of formation/filing/document features, or third-party integration evidence.
- [probe] “PROBE llms.txt: HTTP 200 at https://www.legalzoom.com/llms.txt ################################################################ # :blue_book…”
ai-native userExport all of my data in open formats and leave
weight 3 · round drawnClerkynone0/10No evidence of any bulk data export in open/standard formats (e.g., document download bundles, JSON/CSV exports of legal data) for users to take their data and leave; the Partner API and MCP server are designed for partner integrations/AI assistants working within Clerky, not full data portability/exit. Probes also show no llms.txt/docs export or export-oriented endpoints beyond the legal-workflow API.
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scop…”
- [probe] “PROBE llms.txt: HTTP 404 at https://handbooks.clerky.com/llms.txt”
- [probe] “PROBE docs-md: HTTP 404 at https://handbooks.clerky.com/legal-concepts.md”
- [probe] “PROBE openapi: all candidate paths 404 (https://handbooks.clerky.com/openapi.json, https://handbooks.clerky.com/swagger.json, https://handbo…”
LegalZoomnone0/10No evidence anywhere in the pack of a data export feature, open format export (e.g., CSV/JSON/PDF bulk download), or account/data portability tooling for leaving the platform; evidence only covers business formation services, pricing, and add-ons. Missing for 10: any documented export tool, data portability API, or account closure/data-download workflow.
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
ai-native userPrevent my data from being used to train AI models
weight 3 · round drawnClerkynone0/10No evidence in the pack addresses AI training data usage, opt-out settings, or any privacy policy statement about model training; Clerky's materials focus on legal document workflows, MCP/API integration, and formation services with nothing on this axis.
LegalZoomnone0/10No evidence of an AI-training opt-out or data-use control mechanism anywhere in LegalZoom's docs, marketing, or community discussion; the evidence pack covers business formation services, not privacy/data controls. missing for 10: any privacy policy or settings documentation on AI training opt-out, data usage controls, or user consent mechanisms for AI model training.
Templates library — stories about templates library in this arenaTemplates library
Stories about templates library in this arena
Templates
founderAnswer guided questionnaires that fill in legal documents correctly and flag choices that need attorney review
weight 1 · round to ClerkyClerky's docs show forms with structured fields/json_schema that collect info to fill documents (clerky-docs-19, clerky-docs-20), easy customization of key terms (clerky-docs-11), and the ability to loop in an attorney to review and comment on entered information (clerky-docs-12). However, there is no explicit evidence of a system that automatically flags specific choices as needing attorney review versus a general 'invite attorney' collaboration feature. missing for 10: explicit automated flagging/warning UI for attorney-review-needed choices, independent user account of the questionnaire flow itself, and confirmation the guided form correctly maps answers to legal documents.
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “Our software makes it easy to customize the key terms of the legal paperwork you're working on.”
- [claimed-docs] “you can easily loop in your attorney to have them review and comment on the information you're entering.”
- [claimed-docs] “Our software makes it easy to invite other people to collaborate on a document set, in real-time.”
LegalZoom's docs show guided document creation (150+ customizable legal documents, LLC/incorporation forms, operating agreements) and bundled attorney consultations for follow-up questions, implying some review path, but there is no explicit evidence of an in-flow questionnaire mechanism that flags specific answer choices needing attorney review. Community comments (e.g., a lawyer noting operating agreements are not commodities) suggest the templated approach may miss nuanced legal decisions that would warrant human review, without directly disputing the questionnaire's correctness. missing for 10: explicit description of the guided questionnaire UI/logic that flags risky choices, independent verification that flagged items are accurate or attorney-reviewed in real time.
- [claimed-docs] “An operating agreement, which helps you set entity guidelines and settle disputes”
- [claimed-docs] “Access 150+ customizable legal documents for 1 year”
- [claimed-docs] “Unlimited 30-minute attorney consults about new legal topics related to your business for 30 days”
- [claimed-docs] “Unlimited 30-minute attorney consultations about new legal topics related to your business—30 day subscription included”
- [community] “I am a lawyer. I used Legalzoom to form a 50/50 California LLC in which I am one of the 50% people. The stakes were low, would always be low…”
founderStart from a library of vetted standard legal templates (NDAs, agreements, policies) instead of hiring counsel for routine documents
weight 2 · round to LegalZoomClerky documents show a template-driven system for startup-specific legal paperwork (formation, safes/convertible notes, stock plans, hiring/equity agreements, IRS forms) that lets founders self-serve rather than hire counsel for those documents. However, the evidence never mentions NDAs, general contract templates, or company policy documents, which are explicitly named in the story. Missing for 10: evidence of NDA templates, general business agreement templates, and policy document templates beyond incorporation/equity paperwork.
- [claimed-docs] “Issue safes or convertible notes. Hire employees, consultants, and advisors, and issue stock or stock options as equity compensation.”
- [claimed-docs] “Adopt a stock plan to easily issue restricted stock or stock options to employees, consultants, and advisors.”
- [claimed-docs] “Use Clerky to complete IRS forms and submit them to the IRS, completely online. No need for a fax machine.”
- [claimed-docs] “Our software makes it easy to customize the key terms of the legal paperwork you're working on.”
- [community] “Clerky gives me management tools (including the post-incorporation package: Fundraising, Hiring and Maintenance) although this does not give…”
LegalZoom explicitly offers access to '150+ customizable legal documents' for a year as part of its formation packages, which covers routine business documents like agreements and policies. However, community commentary (a lawyer user) cautions that while basic filings are a commodity, actual document content like operating agreements 'couldn't be more wrong' to assume as commodity, suggesting template quality/customization limits for more complex needs; other users note forms are 'easy enough to fill out yourself' without paid help, undercutting the value-add. Missing for 10: explicit breakdown of NDA/policy-specific templates, evidence of attorney-vetting process behind each template, and independent quality assessment of document library beyond LLC-related bundle mentions.
- [claimed-docs] “Access 150+ customizable legal documents for 1 year”
- [claimed-docs] “An operating agreement, which helps you set entity guidelines and settle disputes”
- [community] “I am a lawyer. I used Legalzoom to form a 50/50 California LLC in which I am one of the 50% people. The stakes were low, would always be low…”
- [community] “When I was 16, three years ago, I got overcharged by LegalZoom for setting up an LLC. They made it seem more complicated than it is. You can…”
Not comparable on these axes
ai-native userRun the product headlessly / in CI for automation
weight 2 · not comparableClerky exposes a Partner API (create document sets, list forms, submit JSON, poll status) that could in principle be scripted, but authentication is an OAuth authorization-code flow tied to a human sign-in ('coming soon' per docs), and legal documents still require human e-signature, so true unattended/CI automation isn't demonstrated. Missing for 10: machine-to-machine/service-account auth, CLI or CI examples, and confirmation the workflow can complete without a human signing step.
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scop…”
ai-native userPlug MCP servers into this product so it can use their tools
weight 3 · not comparableClerkyn/aClerky is a legal-paperwork SaaS, not an AI agent/assistant platform; the evidence shows it exposes its own remote MCP server (mcp.clerky.com) for other AI assistants to consume its tools, which is the opposite direction from this story (a user plugging external MCP servers into Clerky so it can use their tools). There is no evidence Clerky itself acts as an MCP client consuming outside tools, and this capability is outside its product category.
- [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
- [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”
ai-native userConnect an agent via an official MCP server
weight 3 · not comparableClerky publishes an official remote MCP server (https://mcp.clerky.com/mcp) with documented setup for Claude, ChatGPT, and other AI assistants, and a live probe confirms the endpoint is real and OAuth-gated as documented. Missing for 10: independent/community confirmation of real-world agent usage and full detail on the OAuth authorization flow completion.
- [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
- [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”
- [claimed-docs] “# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scop…”
ai-native userUse an official CLI
weight 2 · not comparableClerkynone0/10Clerky provides a Partner API and a remote MCP server, but no evidence of an official CLI tool for AI-native workflows; probes for docs/llms.txt found no CLI references.
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.clerky.com/llms.txt - [Lifecycle](https://developers.clerky.com/getting-started/lifecycle/ind…”
ai-native userIssue scoped/least-privilege API credentials for an agent
weight 2 · not comparableClerky documents an OAuth 2.0 bearer-token model for its Partner API with an 'access model' limiting what each token can do, and a live remote MCP server gated by OAuth ('team access you authorize') confirmed via a 401 invalid_token probe rather than being open. However, OAuth for the Partner API is explicitly marked 'coming soon' with scopes/lifetime 'to be published,' and the MCP scoping described is team-level, not clearly a fine-grained least-privilege credential model for individual agents. Missing for 10: published granular scopes/permissions list, confirmed live least-privilege token issuance flow, and independent verification of scope enforcement.
- [claimed-docs] “# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scop…”
- [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
- [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”
ai-native userBuild against official SDKs
weight 2 · not comparableClerky publishes an official Partner API (REST, JSON schema-driven forms, document-set lifecycle) with docs and an llms.txt developer portal, plus a documented remote MCP server for AI assistants — both usable for programmatic/agentic integration. However there is no evidence of a packaged SDK (client libraries in Python/JS/etc.), and the API's OAuth authentication is explicitly still 'coming soon,' meaning full client access isn't yet live. Missing for 10: language-specific SDK packages, completed/live OAuth client registration, independent developer corroboration of successful integration.
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scop…”
- [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.clerky.com/llms.txt - [Lifecycle](https://developers.clerky.com/getting-started/lifecycle/ind…”
- [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”
ai-native userSubscribe to events via webhooks
weight 2 · not comparableClerkynone0/10The Partner API docs explicitly describe a poll-based lifecycle model (create, submit, poll for state) rather than any webhook/event-subscription mechanism, and no evidence anywhere mentions webhooks or push notifications.
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
ai-native userSet up automations that run autonomously in the background
weight 2 · not comparableClerkynone0/10Clerky's MCP server and Partner API let AI assistants or partner products interactively invoke Clerky tools (with team-scoped OAuth access), but nothing in the evidence describes autonomous, unattended background automations (e.g., scheduled triggers, event-driven workflows) running without a live user/assistant session initiating each action.
- [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
- [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
ai-native userExplore an interactive API reference with runnable examples
weight 2 · not comparableClerkynone0/10Clerky's developer docs describe the Partner API lifecycle, forms, and authentication in prose (clerky-docs-19/20/21) and llms.txt lists doc pages, but there is no evidence of an interactive API reference (e.g., Swagger/OpenAPI explorer) or runnable examples; explicit probes for openapi.json/swagger.json all returned 404 (clerky-probe-3).
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scop…”
- [probe] “PROBE openapi: all candidate paths 404 (https://handbooks.clerky.com/openapi.json, https://handbooks.clerky.com/swagger.json, https://handbo…”
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.clerky.com/llms.txt - [Lifecycle](https://developers.clerky.com/getting-started/lifecycle/ind…”
ai-native userTest against a sandbox environment without touching production data
weight 1 · not comparableClerkynone0/10Clerky's Partner API and MCP server docs describe production workflows (document sets, OAuth, live formation filings) but no evidence anywhere mentions a sandbox, test mode, or staging environment separate from production data.
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scop…”
- [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
- [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”
ai-native userRely on versioned APIs with a documented deprecation policy
weight 2 · not comparableClerkynone0/10The Partner API docs show endpoints prefixed with /v1/ but there is no evidence of a documented API versioning scheme, changelog, or deprecation policy anywhere in the docs, llms.txt index, or OpenAPI probes (which 404). Missing for 10: any explicit versioning/deprecation policy documentation, changelog, or migration guidance for breaking changes.
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scop…”
- [probe] “PROBE openapi: all candidate paths 404 (https://handbooks.clerky.com/openapi.json, https://handbooks.clerky.com/swagger.json, https://handbo…”
- [probe] “PROBE llms.txt: HTTP 200 at https://developers.clerky.com/llms.txt - [Lifecycle](https://developers.clerky.com/getting-started/lifecycle/ind…”
legal-ops leadRely on a tamper-evident audit trail and completion certificate for every signed document
weight 2 · not comparableClerky documents that it logs every change made to a document set or workspace so admins can see who did what, which is a basic audit-log capability, but there is no mention of tamper-evidence (e.g., cryptographic sealing, hash-chained logs) or of a signing completion certificate being issued for executed documents. Missing for 10: tamper-evident/cryptographic audit trail mechanics, completion certificate artifact, and any independent verification of these claims.
- [claimed-docs] “We log every change anyone makes to a document set or workspace, so you can always see who was responsible for what.”
LegalZoomn/aLegalZoom is a legal services/business formation platform, not an e-signature or document execution tool; tamper-evident audit trails and completion certificates are specific to e-signature products (e.g., DocuSign) and this axis doesn't apply to LegalZoom's business model shown in evidence.
legal-ops leadRequire stronger signer identity verification (SMS, ID check, knowledge-based) on sensitive documents
weight 1 · not comparableClerkynone0/10No evidence anywhere in the pack mentions signer identity verification methods like SMS, ID check, or knowledge-based authentication for document signing; Clerky's documentation focuses on formation workflows, collaboration, and audit logs, not signer verification strength.
LegalZoomn/aLegalZoom is a consumer/business legal-services and document platform (business formation, registered agent, compliance filings), not an e-signature/document-signing product with configurable signer identity verification options. The story's axis (SMS/ID/KBA verification for e-signature workflows) does not apply to this product category.
ai-native userPerform bulk operations across many items at once
weight 2 · not comparableClerkynone0/10Evidence shows Clerky's Partner API and MCP server operate on a single document set at a time (create, fill forms, submit, poll) with no batch/bulk endpoints or bulk document/task operations documented; task assignment features are per-item, not bulk. Missing for 10: any bulk create/update endpoint, batch API operations, or bulk import/export capability across multiple items.
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
- [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”
LegalZoomn/aLegalZoom is a consumer legal-services platform for individual business formation/compliance tasks, not a data or workflow tool with bulk/batch operations across many items. No evidence pack content addresses bulk processing, and the product's nature (one entity/filing at a time) makes this axis a category mismatch.
ai-native userDefine rules that trigger actions automatically on events
weight 3 · not comparableClerkyn/aClerky is a legal document/incorporation product, not a rules/automation-engine platform; defining event-triggered automation rules is a category error for this type of product.
ai-native userSchedule recurring jobs or workflows
weight 2 · not comparableClerkyn/aClerky is a legal/formation document platform; scheduling recurring automated jobs or workflows is not a fit for its product category (document sets, formations, partner API, MCP tools for legal paperwork), and no evidence suggests any job-scheduling capability.
ai-native userVersion, review, and roll back my automations
weight 1 · not comparableClerkyn/aClerky is a legal-document/formation automation service (document sets, e-signatures, filings), not a workflow/automation-builder product with versionable automations to review or roll back; the closest evidence is basic audit logging of document-set changes, not automation versioning.
- [claimed-docs] “We log every change anyone makes to a document set or workspace, so you can always see who was responsible for what.”
legal-ops leadTrack contract renewals, expirations, and obligations with automatic alerts
weight 2 · not comparableClerkyn/aClerky is a startup legal-document formation and equity/incorporation platform, not a contract-lifecycle management tool; there is no evidence of contract renewal tracking, expiration alerts, or obligation management, and this is not the kind of capability Clerky's product category would offer.
LegalZoomnone0/10LegalZoom's evidence shows alerts for compliance filings, annual reports, and registered-agent mail, but nothing about tracking contract renewals, expirations, or contractual obligations specifically — a distinct contract-lifecycle-management capability that is plausible for a legal services provider but unevidenced here.
- [claimed-docs] “Get an alert as soon as official mail arrives for you—plus, get reminders when annual report deadlines are approaching.”
- [claimed-docs] “Real-time notifications about your compliance status, upon receipt of data from your state filing office”
legal-ops leadRoute contracts through configurable approval workflows before signature
weight 2 · not comparableClerkynone0/10Clerky's evidence covers document generation, collaboration, task assignment, and attorney review invites, but nothing describes configurable approval workflows/routing before signature (e.g., multi-step approval chains, conditional routing rules, or sign-off gating). Collaboration/task features are not the same as an approval workflow engine.
- [claimed-docs] “We've built features that let you easily assign tasks to co-founders and work on everything together.”
- [claimed-docs] “you can easily loop in your attorney to have them review and comment on the information you're entering.”
- [claimed-docs] “Our software makes it easy to invite other people to collaborate on a document set, in real-time.”
- [claimed-docs] “Our software makes it easy to invite other people to collaborate on a document set, in real-time. Rest easy knowing everyone is looking at t…”
LegalZoomn/aLegalZoom is a consumer/SMB legal document and business-formation service; there is no evidence of contract lifecycle management or configurable approval workflow features. This is a category mismatch rather than a missing feature of a CLM product—LegalZoom's product type does not include enterprise approval-routing workflows.
developerEmbed the signing experience inside my own app or website
weight 2 · not comparableClerky's Partner API lets a developer create a document set, render forms, and collect data inside their own product, but the docs explicitly state 'Users enter formation information in your product and sign documents on Clerky' — meaning the actual signing step happens on Clerky's own platform rather than being embedded, and OAuth authentication for partners is still listed as 'coming soon' rather than live. missing for 10: evidence of an embeddable signing widget/iframe, live partner OAuth flow, and any third-party confirmation of a working embedded integration.
- [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
- [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
- [claimed-docs] “# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scop…”
legal-ops leadBulk-send the same document to many recipients at once
weight 1 · not comparableClerkynone0/10Clerky's evidence describes single document-set collaboration, invitations, and signature workflows for specific named parties (co-founders, employees, attorneys) but nothing about bulk-sending one document to many recipients at once, a feature typical of e-signature platforms like DocuSign.
legal-ops leadSet signing order, automatic reminders, and expirations on outstanding signature requests
weight 1 · not comparableClerkynone0/10No evidence describes signing order, automatic reminders, or expiration settings for signature requests; Clerky's evidence focuses on document collaboration, workspace access, and formation workflows, not e-signature controls of this kind.
LegalZoomn/aLegalZoom is a business formation and legal services platform, not an e-signature/document-signing product; setting signing order, reminders, and expirations on signature requests is a category error for this product's core offering, with no evidence of such e-signature workflow features.
ai-native userRead the product's source under an open license
weight 2 · not comparableClerkynone0/10Clerky is a closed-source legal SaaS product; there is no evidence of any open-source license or public source repository, and probes for open documentation/API artifacts returned 404s. Missing for 10: any open-source license, public code repository, or source availability statement.
- [probe] “PROBE llms.txt: HTTP 404 at https://handbooks.clerky.com/llms.txt”
- [probe] “PROBE docs-md: HTTP 404 at https://handbooks.clerky.com/legal-concepts.md”
- [probe] “PROBE openapi: all candidate paths 404 (https://handbooks.clerky.com/openapi.json, https://handbooks.clerky.com/swagger.json, https://handbo…”
ai-native userSelf-host the core product
weight 3 · not comparableClerkyn/aClerky is a SaaS legal/formation platform tied to legal filings and attorney workflows; self-hosting the core product is not a coherent capability for this category, as it depends on Clerky's own infrastructure, attorneys, and IRS/state filing pipelines.
ai-native userChoose where my data is stored (region/residency)
weight 2 · not comparableClerkyn/aClerky is a legal document/formation service, not infrastructure with configurable data residency; the evidence pack contains no mention of region/residency options, and this is not a fair capability to expect from this type of product (a US-focused legal filing service).
ai-native userControl data retention and deletion
weight 2 · not comparableClerkynone0/10No evidence in the pack addresses data retention policies, export, or deletion controls for user data within Clerky; the docs focus on formation, collaboration, and MCP/API features, none of which mention retention or deletion. Missing for 10: any documentation of data retention periods, deletion requests, or export/erasure controls.
ai-native userOpt out of telemetry and usage tracking
weight 2 · not comparableClerkynone0/10No evidence in the pack addresses telemetry, usage tracking, or any opt-out mechanism for Clerky; the documentation focuses entirely on legal/document workflows with no privacy-controls content.