Docusign vs Ironclad

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Ironclad
   Docusign~partialprobed5/10

   Docusign has no llms.txt (confirmed 404 probe) but does provide agent-oriented documentation such as the Claude MCP connector guide, an official MCP server, and machine-readable OpenAPI specs explicitly described as enabling 'computers to discover and understand the capabilities of the service.' This covers part of the story but lacks the specific llms.txt convention many AI-native tools expect. missing for 10: llms.txt file, dedicated agent-facing doc index, independent confirmation that agents can consume these docs successfully.

   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.docusign.com/llms.txt”
   • [probe] “official MCP server documented at https://developers.docusign.com/platform/mcp-server/”
   • [claimed-docs] “The Docusign Connector in Anthropic Claude via MCP server provides a supported way to connect Claude to Docusign IAM capabilities.”
   • [claimed-docs] “Retrieve agreement context and metadata... Query agreement status and key dates... Trigger workflow actions through IAM tools”
   • [github] “allows both humans and computers to discover and understand the capabilities of the service”

   proof ↗⚑ flag

   Ironclad✓fullprobed9/10

   Direct probe evidence confirms Ironclad hosts a live llms.txt at the developer docs root and serves markdown-formatted docs pages (e.g. getting-started.md), which are exactly the agent-oriented doc formats an AI agent could point to. Missing for 10: no independent third-party confirmation of agents actually consuming these docs successfully in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.ironcladapp.com/llms.txt # Ironclad CLM API Documentation | Ironclad Developer Hub Documentati…”
   • [probe] “PROBE docs-md: HTTP 200 at https://developer.ironcladapp.com/docs/getting-started.md --- updatedAt: 2026-08-11T20:11:21.000Z --- Fetch the …”
   • [claimed-docs] “Ironclad's rich API can be used to connect your contract data and contracting process to your applications and internal platforms.”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Docusign
   Docusign~partialcommunity6/10

   Docusign exposes a REST API, official SDKs (e.g., Node.js client) and OpenAPI specs that let developers script sending/signing/approving documents programmatically, and the Gemini CLI + Docusign MCP integration explicitly supports automating agreement processes 'from your terminal.' However, there is no explicit CI/CD documentation, headless-mode guide, or automated pipeline example, and community feedback notes real integration friction (mixed embedded-API experiences). Missing for 10: dedicated CI/headless deployment guide, service-account/automation-focused docs, and independent verification of running the API in automated pipelines without a UI.

   • [claimed-docs] “Request Signatures & Automate Forms | REST API | Docusign”
   • [claimed-docs] “Send, sign, and approve documents using this client.”
   • [claimed-docs] “The Official Docusign Node.js Client Library used to interact with the eSign REST API. Send, sign, and approve documents using this client.”
   • [github] “We use OpenAPI/Swagger files to build many of our developer tools including our client SDKs”
   • [github] “allows both humans and computers to discover and understand the capabilities of the service”
   • [claimed-docs] “Query agreement data and automate agreement processes from your terminal by pairing Gemini CLI with Docusign MCP.”
   • [community] “We did exactly this embedded signing integration and it was fairly seamless - built a POC in Postman in about an hour and a Jr dev built a p…”
   • [community] “We use the v2 REST API creating embedded envelope signing URLs without issues. Documentation is fantastic in its thoroughness - opposite exp…”

   proof ↗⚑ flag

   Ironclad~partialclaimed5/10

   Ironclad exposes a REST API with OAuth bearer tokens, webhooks, and endpoints to launch workflows, trigger exports, and manage records — all of which can be scripted/automated without the UI, supporting headless-style automation. However there is no CLI, no explicit CI/CD integration examples, and workflow launch still requires a pre-published design from the in-app Workflow Designer, limiting full headless autonomy. Missing for 10: dedicated CLI or SDK for CI pipelines, explicit CI/CD examples, and evidence that workflow publishing itself can be done headlessly.

   • [claimed-docs] “Ironclad's rich API can be used to connect your contract data and contracting process to your applications and internal platforms.”
   • [claimed-docs] “Ironclad primarily uses the OAuth 2.0 Authorization Framework to generate API bearer tokens that can be used to authenticate API requests.”
   • [claimed-docs] “Webhooks allow you to specify that we should POST to your URL when certain events happen.”
   • [claimed-docs] “Technical audiences will learn how to use Ironclad's API to launch workflows.”
   • [claimed-docs] “Client submits an API request via Public API with request body payload to trigger an export job”
   • [claimed-docs] “Published workflow design and Workflow Designer access: See your internal company admin for access to Workflow Designer.”
   • [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Docusign
   Docusign✓fullprobed8/10

   Docusign documents an official MCP server (Docusign Connector via Anthropic Claude and Gemini CLI) with a dedicated developer platform page and guide, exposing IAM tools like retrieving agreement context/metadata and triggering workflow actions. Missing for 10: independent/hands-on verification of the MCP server's reliability and broader third-party adoption beyond vendor blog examples.

   • [claimed-docs] “The Docusign Connector in Anthropic Claude via MCP server provides a supported way to connect Claude to Docusign IAM capabilities.”
   • [claimed-docs] “Retrieve agreement context and metadata... Query agreement status and key dates... Trigger workflow actions through IAM tools”
   • [claimed-docs] “Query agreement data and automate agreement processes from your terminal by pairing Gemini CLI with Docusign MCP.”
   • [claimed-docs] “Build agreement workflows: Docusign MCP & Claude”
   • [probe] “official MCP server documented at https://developers.docusign.com/platform/mcp-server/”

   proof ↗⚑ flag

   Ironclad—none0/10

   Ironclad is not an AI agent itself, so publishing an official MCP server is a plausible, applicable axis, but no evidence pack item mentions MCP at all—only REST API, webhooks, and OAuth are documented.

   • [claimed-docs] “Ironclad's rich API can be used to connect your contract data and contracting process to your applications and internal platforms.”
   • [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
   • [claimed-docs] “Ironclad primarily uses the OAuth 2.0 Authorization Framework to generate API bearer tokens that can be used to authenticate API requests.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.ironcladapp.com/openapi.json, https://developer.ironcladapp.com/swagger.json, http…”

   proof ↗⚑ flag

4. ai-native userDrive the product through a documented public API

   weight 3 · round to Docusign
   Docusign✓fullprobed8/10

   Docusign publishes a well-documented public REST API (eSign REST API docs, Developer Center, OpenAPI/Swagger specs used to generate SDKs like the Node.js client), with community confirmation that thorough API-driven integrations (e.g., embedded signing) work well in production. This directly satisfies programmatic/API-driven use, though one community report describes a security workaround requiring a legacy API version, and there's no first-party llms.txt or discoverable openapi.json at the expected probe URLs. Missing for 10: a clean machine-readable OpenAPI spec at a standard endpoint (probe returned 404s) and stronger independent corroboration beyond one HN thread.

   • [claimed-docs] “Request Signatures & Automate Forms | REST API | Docusign”
   • [claimed-docs] “Docusign Developer Center | eSignature APIs & Resources | Docusign”
   • [github] “We use OpenAPI/Swagger files to build many of our developer tools including our client SDKs”
   • [github] “allows both humans and computers to discover and understand the capabilities of the service”
   • [github] “We use OpenAPI/Swagger files to build many of our developer tools including our client SDKs using `swagger-codegen`.”
   • [claimed-docs] “Send, sign, and approve documents using this client.”
   • [claimed-docs] “The Official Docusign Node.js Client Library used to interact with the eSign REST API. Send, sign, and approve documents using this client.”
   • [community] “We did exactly this embedded signing integration and it was fairly seamless - built a POC in Postman in about an hour and a Jr dev built a p…”
   • [community] “We use the v2 REST API creating embedded envelope signing URLs without issues. Documentation is fantastic in its thoroughness - opposite exp…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.docusign.com/openapi.json, https://developers.docusign.com/swagger.json, https://…”

   proof ↗⚑ flag

   Ironclad✓fullprobed7/10

   Ironclad ships a documented public REST API (Records, Workflows, Records) with OAuth2 authentication, webhooks, and detailed guides for launching workflows, exports, and embedding clickwraps, clearly enabling programmatic/agentic control of contracting processes. missing for 10: no discoverable OpenAPI/Swagger spec (all candidate paths 404), and no independent/hands-on developer corroboration beyond first-party docs.

   • [claimed-docs] “Ironclad's rich API can be used to connect your contract data and contracting process to your applications and internal platforms.”
   • [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
   • [claimed-docs] “Ironclad primarily uses the OAuth 2.0 Authorization Framework to generate API bearer tokens that can be used to authenticate API requests.”
   • [claimed-docs] “Webhooks allow you to specify that we should POST to your URL when certain events happen.”
   • [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
   • [claimed-docs] “Integrations can also directly control the contract process, automatically blocking or pushing forward approvals.”
   • [claimed-docs] “integrations can interface directly with underlying contract documents, reading contract text or updating new versions of the document”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.ironcladapp.com/openapi.json, https://developer.ironcladapp.com/swagger.json, http…”

   proof ↗⚑ flag

5. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round drawn
   Docusign—none0/10

   No evidence describes granular, scoped/least-privilege API credentials or OAuth scopes tailored for AI agents; the MCP connector docs mention triggering IAM workflow actions but not credential scoping controls. A community report even describes an API-user permission failure where embedded signing let a single API user's session expose the entire account's data, undermining any claim of fine-grained least-privilege access.

   • [claimed-docs] “The Docusign Connector in Anthropic Claude via MCP server provides a supported way to connect Claude to Docusign IAM capabilities.”
   • [claimed-docs] “Retrieve agreement context and metadata... Query agreement status and key dates... Trigger workflow actions through IAM tools”
   • [community] “We wanted embedded flows with one API user, but discovered that on page refresh, users could break out of the signing page and view/click ar…”

   proof ↗⚑ flag

   Ironclad—none0/10

   Ironclad's docs confirm OAuth 2.0 bearer token authentication for its API, but there is no evidence of scoped or least-privilege credential issuance (e.g., configurable permission scopes, role-based API keys, or agent-specific credential grants). The axis applies since an API platform could plausibly offer this, but no supporting evidence exists.

   • [claimed-docs] “Ironclad primarily uses the OAuth 2.0 Authorization Framework to generate API bearer tokens that can be used to authenticate API requests.”

   proof ↗⚑ flag

6. ai-native userBuild against official SDKs

   weight 2 · round to Docusign
   Docusign✓fullprobed8/10

   Docusign ships official client SDKs (e.g., docusign-esign-node-client) built from OpenAPI/Swagger specs, backed by a dedicated developer center and REST API docs, and community reports include successful hands-on integrations using the REST API. Missing for 10: independent corroboration of SDK quality/completeness across all supported languages, and machine-discoverable API specs (llms.txt and openapi.json probes both returned 404), plus some community reports of API friction that temper confidence in a flawless experience.

   • [claimed-docs] “Send, sign, and approve documents using this client.”
   • [claimed-docs] “The Official Docusign Node.js Client Library used to interact with the eSign REST API. Send, sign, and approve documents using this client.”
   • [claimed-docs] “Request Signatures & Automate Forms | REST API | Docusign”
   • [claimed-docs] “Docusign Developer Center | eSignature APIs & Resources | Docusign”
   • [github] “We use OpenAPI/Swagger files to build many of our developer tools including our client SDKs”
   • [github] “We use OpenAPI/Swagger files to build many of our developer tools including our client SDKs using `swagger-codegen`.”
   • [community] “We did exactly this embedded signing integration and it was fairly seamless - built a POC in Postman in about an hour and a Jr dev built a p…”
   • [community] “We use the v2 REST API creating embedded envelope signing URLs without issues. Documentation is fantastic in its thoroughness - opposite exp…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.docusign.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.docusign.com/openapi.json, https://developers.docusign.com/swagger.json, https://…”

   proof ↗⚑ flag

   Ironclad—none0/10

   Ironclad documents a REST API (Records, Workflows, webhooks, OAuth2) but the evidence pack contains no mention of official SDKs or client libraries in any language, and an OpenAPI spec probe returned 404s across all standard paths.

   • [claimed-docs] “Ironclad's rich API can be used to connect your contract data and contracting process to your applications and internal platforms.”
   • [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
   • [claimed-docs] “Ironclad primarily uses the OAuth 2.0 Authorization Framework to generate API bearer tokens that can be used to authenticate API requests.”
   • [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.ironcladapp.com/openapi.json, https://developer.ironcladapp.com/swagger.json, http…”

   proof ↗⚑ flag

7. ai-native userSubscribe to events via webhooks

   weight 2 · round to Ironclad
   Docusign—none0/10

   The evidence pack never mentions webhooks, event subscriptions, or DocuSign Connect (the product's known webhook feature); only REST APIs, SDKs, MCP connector, and unrelated product features are cited. Since webhook support is a plausible axis for an API-driven product like Docusign, absence of evidence makes this 'none' rather than 'na'.

   ⚑ flag

   Ironclad✓fullclaimed7/10

   Ironclad's developer docs explicitly document webhooks that POST to a user-specified URL when events occur, directly supporting event subscription. Missing for 10: details on event types/filtering, payload schema, retry/security (signature verification) documentation, and independent/hands-on confirmation of reliability.

   • [claimed-docs] “Webhooks allow you to specify that we should POST to your URL when certain events happen.”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Docusign
   Docusign✓fullclaimed7/10

   Docusign documents multiple AI-generated insight features directly in-product: AI-Assisted Summary and Q&A for signers, AI-Assisted Review that flags risky language, suggests redlines, and drafts new clauses against playbooks, and CLM's AI clause-compliance flagging and drafting. These are first-party vendor claims with no independent hands-on corroboration of the AI quality itself. Missing for 10: independent/third-party validation of AI insight accuracy, and no community evidence confirming these AI features work as described in practice.

   • [claimed-docs] “Our AI-Assisted Summary and Q&A features increase trust in agreements”
   • [claimed-docs] “Review and analyze agreements, flag potentially risky language, suggest surgical edits, and draft new language from an intuitive AI-powered …”
   • [claimed-docs] “Review agreements against your playbooks and ready-to-deploy agents and get suggested redlines to align terms with your requirements.”
   • [claimed-docs] “Docusign AI-Assisted Review integrates into MS Word to analyze, redline, and draft language based on your playbooks.”
   • [claimed-docs] “use AI to flag non-compliant clauses, suggest approved language, and draft new clauses on demand”
   • [claimed-docs] “AI-generated summaries and built-in Q&A give signers clarity faster so they can sign with confidence.”
   • [claimed-docs] “Leverage AI to easily create new contract review playbooks based on your standard templates or other reference documents.”

   proof ↗⚑ flag

   Ironclad~partialclaimed3/10

   Ironclad has a dedicated 'Ironclad AI' product page marketed as 'A New Era of Contract Intelligence,' implying AI-driven insights over contract data, but the evidence pack contains only page titles/taglines with no detail on what specific insights, suggestions, or analytics are actually generated or how a user interacts with them. Missing for 10: concrete feature descriptions (e.g., risk analysis, clause suggestions, obligation extraction), first-party documentation of AI capabilities, and independent/hands-on corroboration of the AI features working as described.

   • [claimed-docs] “Built on how contracts really move.”
   • [claimed-docs] “A New Era of Contract Intelligence | Ironclad”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Docusign
   Docusign~partialprobed6/10

   Docusign offers configurable workflows, CLM automation, and an official MCP server that lets AI agents (e.g., Claude) trigger workflow actions and retrieve agreement context, which supports agentic automation. However, there's no explicit evidence of scheduled, unattended, or fully autonomous background execution (e.g., cron-like triggers, webhooks, or agent-initiated jobs without a live AI session) — missing for 10: documented background/scheduled automation, webhook/event-driven triggers, and independent confirmation that MCP-driven workflows run without active human/agent supervision.

   • [claimed-docs] “take advantage of configurable workflows to tackle your trickiest agreement challenges”
   • [claimed-docs] “Trigger workflow actions through IAM tools”
   • [claimed-docs] “The Docusign Connector in Anthropic Claude via MCP server provides a supported way to connect Claude to Docusign IAM capabilities.”
   • [probe] “official MCP server documented at https://developers.docusign.com/platform/mcp-server/”
   • [claimed-docs] “Generate contracts in a click with dynamic templates and use AI to flag non-compliant clauses, suggest approved language, and draft new clau…”

   proof ↗⚑ flag

   Ironclad~partialclaimed5/10

   Ironclad's API and webhooks allow workflows to be triggered and events to fire automatically in the background (e.g., launching workflows via API, webhooks posting on contract events, integrations that can 'automatically block or push forward approvals'), which supports building autonomous automations. However, this requires custom integration/dev work rather than a native no-code 'set up an automation' feature aimed at AI-native users, and there's no evidence of an agent-oriented automation builder or scheduler. Missing for 10: a first-party no-code automation/agent builder, evidence of AI-driven autonomous triggers, and independent confirmation these automations run reliably unattended.

   • [claimed-docs] “Webhooks allow you to specify that we should POST to your URL when certain events happen.”
   • [claimed-docs] “Technical audiences will learn how to use Ironclad's API to launch workflows.”
   • [claimed-docs] “Integrations can also directly control the contract process, automatically blocking or pushing forward approvals.”
   • [claimed-docs] “integrations can read and write structured data from Ironclad, leaving the specifics around updating contract language and following approva…”
   • [claimed-docs] “Published workflow design and Workflow Designer access: See your internal company admin for access to Workflow Designer.”

   proof ↗⚑ flag

3. ai-native userDelegate tasks to a built-in AI assistant inside the product

   weight 3 · round to Docusign
   Docusign~partialclaimed6/10

   Docusign ships AI-Assisted Review, AI-Assisted Summary/Q&A, and Iris-powered form conversion embedded within its products, letting users delegate agreement-analysis and drafting tasks to built-in AI features rather than a single unified conversational assistant that can be delegated arbitrary tasks. missing for 10: evidence of a general-purpose, agentic in-product assistant that can autonomously execute multi-step tasks (not just summarize/flag/draft within a specific workflow), and independent/hands-on validation of these AI features actually working as described.

   • [claimed-docs] “Our AI-Assisted Summary and Q&A features increase trust in agreements”
   • [claimed-docs] “Review and analyze agreements, flag potentially risky language, suggest surgical edits, and draft new language from an intuitive AI-powered …”
   • [claimed-docs] “Review agreements against your playbooks and ready-to-deploy agents and get suggested redlines to align terms with your requirements.”
   • [claimed-docs] “Docusign AI-Assisted Review integrates into MS Word to analyze, redline, and draft language based on your playbooks.”
   • [claimed-docs] “AI-generated summaries and built-in Q&A give signers clarity faster so they can sign with confidence.”
   • [claimed-docs] “use AI to flag non-compliant clauses, suggest approved language, and draft new clauses on demand”
   • [claimed-docs] “use AI powered by Docusign Iris to instantly convert PDFs and templates”

   proof ↗⚑ flag

   Ironclad~partialclaimed2/10

   Ironclad has a dedicated 'Ironclad AI' product page referencing 'contract intelligence,' suggesting some built-in AI capability, but the evidence pack contains only marketing taglines with no detail on what tasks can be delegated to an assistant, how it's invoked, or its scope. Missing for 10: description of assistant task delegation, concrete feature list, hands-on or independent corroboration of AI assistant functionality.

   • [claimed-docs] “Built on how contracts really move.”
   • [claimed-docs] “A New Era of Contract Intelligence | Ironclad”

   proof ↗⚑ flag

4. ai-native userOperate the product with natural-language commands

   weight 2 · round to Docusign
   Docusign✓fullprobed7/10

   Docusign documents a supported MCP connector enabling Claude, Gemini CLI, and Copilot Studio to query agreement status/metadata and trigger IAM workflow actions via natural-language commands, plus AI-powered chat interfaces for contract review and summaries. This directly shows natural-language operation of core agreement workflows through agentic integrations. Missing for 10: independent/hands-on user verification of the MCP connector's reliability and breadth of NL command coverage beyond vendor blog examples.

   • [claimed-docs] “Retrieve agreement context and metadata”
   • [claimed-docs] “Trigger workflow actions through IAM tools”
   • [claimed-docs] “The Docusign Connector in Anthropic Claude via MCP server provides a supported way to connect Claude to Docusign IAM capabilities.”
   • [claimed-docs] “Retrieve agreement context and metadata... Query agreement status and key dates... Trigger workflow actions through IAM tools”
   • [claimed-docs] “Query agreement data and automate agreement processes from your terminal by pairing Gemini CLI with Docusign MCP.”
   • [claimed-docs] “Build agreement workflows: Docusign MCP & Claude”
   • [claimed-docs] “Internal enterprise GitHub Copilot”
   • [probe] “official MCP server documented at https://developers.docusign.com/platform/mcp-server/”
   • [claimed-docs] “Review and analyze agreements, flag potentially risky language, suggest surgical edits, and draft new language from an intuitive AI-powered …”

   proof ↗⚑ flag

   Ironclad—none0/10

   Evidence shows Ironclad offers APIs, webhooks, and a no-code workflow builder, but nothing indicates a natural-language command interface for operating the product; the 'Ironclad AI' page is only a marketing teaser with no described NL capability.

   • [claimed-docs] “Built on how contracts really move.”
   • [claimed-docs] “A New Era of Contract Intelligence | Ironclad”
   • [claimed-docs] “Ironclad's rich API can be used to connect your contract data and contracting process to your applications and internal platforms.”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Docusign—none0/10

   Evidence only shows a general Developer Center and REST API docs page plus an OpenAPI/Swagger spec repo, but nothing indicates an interactive, runnable API console; probes actually found 404s for openapi.json/llms.txt at the developer site, suggesting no readily discoverable interactive reference.

   • [claimed-docs] “Request Signatures & Automate Forms | REST API | Docusign”
   • [claimed-docs] “Docusign Developer Center | eSignature APIs & Resources | Docusign”
   • [github] “We use OpenAPI/Swagger files to build many of our developer tools including our client SDKs”
   • [github] “allows both humans and computers to discover and understand the capabilities of the service”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.docusign.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.docusign.com/openapi.json, https://developers.docusign.com/swagger.json, https://…”

   proof ↗⚑ flag

   Ironclad—none0/10

   Ironclad publishes a standard API reference (getting-started, authentication, webhooks, workflows) but nothing in the evidence indicates an interactive console or runnable code examples; a probe for an OpenAPI/Swagger spec (which typically powers interactive 'try it' consoles) returned 404 on all candidate paths, suggesting no such tooling exists.

   • [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
   • [claimed-docs] “Ironclad primarily uses the OAuth 2.0 Authorization Framework to generate API bearer tokens that can be used to authenticate API requests.”
   • [claimed-docs] “Webhooks allow you to specify that we should POST to your URL when certain events happen.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.ironcladapp.com/openapi.json, https://developer.ironcladapp.com/swagger.json, http…”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round to Docusign
   Docusign✓fullprobed8/10

   Docusign publishes and maintains a dedicated GitHub repository of OpenAPI/Swagger specifications used to generate their client SDKs, explicitly stated to let 'humans and computers discover and understand the capabilities of the service', plus a REST API developer docs site. Missing for 10: a directly discoverable openapi.json/swagger.json at the main developer site (probe found 404s at common well-known paths), so users must know to find the GitHub repo rather than a single canonical spec URL.

   • [github] “We use OpenAPI/Swagger files to build many of our developer tools including our client SDKs”
   • [github] “allows both humans and computers to discover and understand the capabilities of the service”
   • [github] “We use OpenAPI/Swagger files to build many of our developer tools including our client SDKs using `swagger-codegen`.”
   • [claimed-docs] “Request Signatures & Automate Forms | REST API | Docusign”
   • [claimed-docs] “Docusign Developer Center | eSignature APIs & Resources | Docusign”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.docusign.com/openapi.json, https://developers.docusign.com/swagger.json, https://…”

   proof ↗⚑ flag

   Ironclad—none0/10

   Ironclad has extensive API documentation (Records, Workflows, Webhooks) but a direct probe of common OpenAPI spec locations returned 404 for all candidates, and no evidence pack item shows a downloadable machine-readable spec file. missing for 10: an actual OpenAPI/Swagger JSON or YAML file accessible for download, any documented endpoint serving the spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.ironcladapp.com/openapi.json, https://developer.ironcladapp.com/swagger.json, http…”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round drawn
   Docusign—none0/10

   The evidence pack contains no mention of a developer/demo sandbox account, test environment, or non-production testing capability for Docusign's API or MCP connector; only production docs, SDKs, and integration guides are cited. missing for 10: explicit sandbox/demo account documentation, guidance on testing without production data, any developer-center reference to a sandbox environment.

   ⚑ flag

   Ironclad—none0/10

   No evidence of a sandbox/test environment, staging API, or separate test credentials distinct from production data; the docs cover OAuth, webhooks, and API objects but never mention a sandbox mode.

   ⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round to Docusign
   Docusign!disputedcontradicted3/10

   Docusign does expose versioned REST APIs (e.g. v2 eSignature API, OpenAPI/Swagger specs on GitHub) that could support a deprecation policy story, but no documented deprecation/versioning policy page is present, and a hands-on account describes being forced onto a 'legacy API version with no promise against sunsetting' after a security fix, directly contradicting reliable API lifecycle guarantees. missing for 10: an explicit deprecation-policy document, versioning changelog, and independent confirmation that old API versions are sunset predictably.

   • [community] “We wanted embedded flows with one API user, but discovered that on page refresh, users could break out of the signing page and view/click ar…”
   • [community] “We use the v2 REST API creating embedded envelope signing URLs without issues. Documentation is fantastic in its thoroughness - opposite exp…”
   • [github] “We use OpenAPI/Swagger files to build many of our developer tools including our client SDKs”
   • [claimed-docs] “Request Signatures & Automate Forms | REST API | Docusign”

   proof ↗⚑ flag

   Ironclad—none0/10

   Evidence shows a documented REST API (Records, Workflows, Webhooks) but no mention of API versioning scheme or a documented deprecation policy anywhere in the docs pack, and OpenAPI spec probes all 404. missing for 10: explicit API version numbering, changelog/release notes, deprecation policy or sunset timeline documentation.

   • [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
   • [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.ironcladapp.com/openapi.json, https://developer.ironcladapp.com/swagger.json, http…”

   proof ↗⚑ flag

Audit

1. legal-ops leadRely on a tamper-evident audit trail and completion certificate for every signed document

   weight 2 · round drawn
   Docusign—none0/10

   The evidence pack contains no mention of a tamper-evident audit trail, certificate of completion, or any compliance/audit documentation for signed envelopes — only generic e-signature marketing copy, integrations, and AI features. Although this is a core, expected capability for an e-signature platform (so the axis applies), nothing in the provided docs, GitHub, or community sources substantiates it. missing for 10: documentation of Certificate of Completion, audit trail/tamper-evidence mechanism (e.g., hash-sealing, timestamping), and any independent verification of its integrity.

   ⚑ flag

   Ironclad—none0/10

   Ironclad is a CLM/e-signature platform where a tamper-evident audit trail and completion certificate would be a natural expected capability, but the evidence pack contains no mention of audit trails, certificates of completion, or tamper-evidence for signed documents—only generic pages about signing, storing, and API access.

   • [claimed-docs] “Contract Signing Has Never Been Easier”
   • [claimed-docs] “Contract Signing Has Never Been Easier | Ironclad”
   • [claimed-docs] “Store Contracts Securely, Find Them Easily”

   proof ↗⚑ flag

2. legal-ops leadRequire stronger signer identity verification (SMS, ID check, knowledge-based) on sensitive documents

   weight 1 · round to Docusign
   Docusign✓fullclaimed8/10

   Docusign Identify offers multiple ID verification methods explicitly (SMS one-time-passcode, government ID + biometric check, knowledge-based/risk-based verification) and a Risk-Based Verification workflow that dynamically escalates verification strength based on risk — directly matching the legal-ops need for stronger identity checks on sensitive documents. The pricing page also confirms '5 identity verifications' as a configurable feature tier. Missing for 10: independent/hands-on third-party validation of these verification flows in practice and clearer documentation on per-document/per-envelope configuration granularity.

   • [claimed-docs] “Check the authenticity of government issue identity documents or verify recipient identities in less than a minute.”
   • [claimed-docs] “Enable repeat users to verify their identity by entering a one-time-passcode sent to their phone in seconds.”
   • [claimed-docs] “Dynamically adjust the type of verification your signers must complete based on an automated and instant risk assessment with our Risk-Based…”
   • [claimed-docs] “Require recipients to upload a photo of their government ID & complete a quick biometric challenge.”
   • [claimed-docs] “Reduce fraud risk with 5 identity verifications”

   proof ↗⚑ flag

   Ironclad—none0/10

   No evidence in the pack mentions signer identity verification methods such as SMS, ID check, or knowledge-based authentication for e-signature; the docs cover contract signing generally but not these verification tiers.

   • [claimed-docs] “Contract Signing Has Never Been Easier”
   • [claimed-docs] “Contract Signing Has Never Been Easier | Ironclad”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Ironclad
   Docusign—none0/10

   The evidence pack shows Docusign has a REST API, SDKs, and an MCP connector for triggering workflow actions, but nothing explicitly describes bulk/batch operations (e.g., a bulk-send feature, batch API endpoint, or multi-item automation) that would let an AI-native user act on many items at once. Missing for 10: any explicit bulk-send/batch-processing feature, batch API endpoint documentation, or evidence of MCP/agent tools operating on multiple envelopes/agreements simultaneously.

   • [claimed-docs] “Request Signatures & Automate Forms | REST API | Docusign”
   • [claimed-docs] “Send, sign, and approve documents using this client.”
   • [claimed-docs] “Retrieve agreement context and metadata”
   • [claimed-docs] “Trigger workflow actions through IAM tools”
   • [claimed-docs] “Retrieve agreement context and metadata... Query agreement status and key dates... Trigger workflow actions through IAM tools”

   proof ↗⚑ flag

   Ironclad~partialclaimed5/10

   Ironclad's Records/Workflows APIs allow retrieving, creating, and updating records/workflows programmatically, which enables scripted bulk operations across many contracts/records, and data-export jobs support bulk data retrieval. However, there is no explicit documentation of a native bulk/batch endpoint, rate-limit guidance for bulk calls, or first-party bulk-operation UI/API designed for AI-native agents. Missing for 10: dedicated bulk/batch API endpoints, documented pagination/batching best practices for large-scale operations, and independent evidence of successful bulk automation at scale.

   • [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
   • [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
   • [claimed-docs] “Client submits an API request via Public API with request body payload to trigger an export job”
   • [claimed-docs] “Template IDs can be obtained in-app or via API”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round to Ironclad
   Docusign~partialclaimed5/10

   Docusign advertises 'configurable workflows,' conditional logic in web forms, and CLM's drag-and-drop workflow builder, plus MCP-based 'trigger workflow actions through IAM tools,' suggesting some rule-based automation exists. However there's no concrete documentation of an event-trigger/webhook rule engine (e.g., Docusign Connect-style event listeners) or examples of automatically firing actions on defined events. Missing for 10: explicit event/trigger API or webhook docs, examples of rule definitions, independent verification that automation runs reliably without manual intervention.

   • [claimed-docs] “take advantage of configurable workflows to tackle your trickiest agreement challenges”
   • [claimed-docs] “Use a drag-and-drop editor to design contract processes”
   • [claimed-docs] “implement conditional logic to ensure only relevant fields appear”
   • [claimed-docs] “Dynamically adjust the type of verification your signers must complete based on an automated and instant risk assessment with our Risk-Based…”
   • [claimed-docs] “Trigger workflow actions through IAM tools”
   • [claimed-docs] “Retrieve agreement context and metadata... Query agreement status and key dates... Trigger workflow actions through IAM tools”
   • [claimed-docs] “Generate contracts in a click with dynamic templates and use AI to flag non-compliant clauses, suggest approved language, and draft new clau…”

   proof ↗⚑ flag

   Ironclad~partialclaimed6/10

   Ironclad supports webhooks to trigger outbound notifications on events and an API/Workflows API to programmatically launch or update workflows, plus integrations that can block/push forward approvals automatically — this gives event-driven automation. However there's no evidence of a native rules engine where AI-native users can define arbitrary conditional 'if event then action' automations without building custom integration code. Missing for 10: a first-class rules/automation builder, documented trigger-condition-action configuration UI, and independent confirmation of automated rule execution in practice.

   • [claimed-docs] “Webhooks allow you to specify that we should POST to your URL when certain events happen.”
   • [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
   • [claimed-docs] “Integrations can also directly control the contract process, automatically blocking or pushing forward approvals.”
   • [claimed-docs] “Technical audiences will learn how to use Ironclad's API to launch workflows.”

   proof ↗⚑ flag

3. ai-native userSchedule recurring jobs or workflows

   weight 2 · round drawn
   Docusign—none0/10

   Docusign documents configurable workflows, templates, MCP/API integrations, and third-party connectors (Zapier-style), so a buyer could reasonably ask about recurring/scheduled job automation, but no evidence pack item describes any cron-like scheduler, recurring trigger, or automated recurring workflow execution capability.

   ⚑ flag

   Ironclad—none0/10

   Ironclad's API/webhooks allow event-driven and on-demand workflow triggering, but there is no evidence of a scheduler or recurring-job/cron capability for workflows or exports.

   ⚑ flag

4. ai-native userVersion, review, and roll back my automations

   weight 1 · round drawn
   Docusign—none0/10

   No evidence describes any version history, review/approval workflow, or rollback mechanism for automations (workflows, templates, or MCP-triggered actions); Docusign's docs cover building and configuring workflows/templates but not versioning or reverting them.

   ⚑ flag

   Ironclad—none0/10

   Ironclad's docs mention publishing workflows via Workflow Designer and admin access, but there is no evidence of version history, review/approval flow for automation changes, or rollback capability for workflows/integrations themselves.

   • [claimed-docs] “Published workflow design and Workflow Designer access: See your internal company admin for access to Workflow Designer.”
   • [claimed-docs] “In Workflow Designer, publish the workflow you wish to launch if it has not been published already.”

   proof ↗⚑ flag

Compliance

1. legal-ops leadSee a compliance calendar of upcoming filing deadlines and get reminders before each one

   weight 2 · round drawn
   Docusign—none0/10

   No evidence in the pack references a compliance calendar, filing deadlines, or deadline reminder features; Docusign's evidence covers e-signature, CLM, AI review, identity verification, and integrations but nothing about tracking regulatory/filing deadlines or proactive reminders for legal-ops compliance calendars.

   ⚑ flag

   Ironclad—none0/10

   Ironclad's evidence covers contract creation, signing, storage, workflows, and API/webhooks, but there is no mention of a compliance/filing deadline calendar or reminder system for legal-ops filing obligations.

   ⚑ flag

Compliance agentic

1. 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 Docusign
   Docusign~partialprobed4/10

   Docusign's MCP connector lets an agent (e.g. Claude) retrieve agreement context, query status, and trigger IAM workflow actions, and its CLM/AI-Assisted Review features can flag non-compliant clauses and draft language, suggesting a path toward agent-driven contract/compliance workflows. However, there is no evidence of an agent autonomously preparing a full 'annual report' or 'compliance filing' end-to-end with minimal human input — the evidence only covers discrete building blocks (signing, clause review, status queries) rather than a demonstrated compliance-filing delegation flow. Missing for 10: concrete example of an agent completing a compliance filing/annual report task autonomously, evidence of minimal-human-input completion, and independent corroboration beyond vendor blog/docs.

   • [claimed-docs] “The Docusign Connector in Anthropic Claude via MCP server provides a supported way to connect Claude to Docusign IAM capabilities.”
   • [claimed-docs] “Retrieve agreement context and metadata... Query agreement status and key dates... Trigger workflow actions through IAM tools”
   • [claimed-docs] “use AI to flag non-compliant clauses, suggest approved language, and draft new clauses on demand”
   • [claimed-docs] “Review and analyze agreements, flag potentially risky language, suggest surgical edits, and draft new language from an intuitive AI-powered …”
   • [claimed-docs] “Review agreements against your playbooks and ready-to-deploy agents and get suggested redlines to align terms with your requirements.”
   • [claimed-docs] “Build agreement workflows: Docusign MCP & Claude”
   • [probe] “official MCP server documented at https://developers.docusign.com/platform/mcp-server/”

   proof ↗⚑ flag

   Ironclad—none0/10

   Ironclad's evidence covers APIs, workflows, and webhooks for contract lifecycle automation, but nothing describes an agent autonomously preparing an annual report or compliance filing end-to-end with minimal human input; 'Ironclad AI' references are generic marketing without this specific capability.

   • [claimed-docs] “Built on how contracts really move.”
   • [claimed-docs] “A New Era of Contract Intelligence | Ironclad”
   • [claimed-docs] “Ironclad's rich API can be used to connect your contract data and contracting process to your applications and internal platforms.”
   • [claimed-docs] “Technical audiences will learn how to use Ironclad's API to launch workflows.”

   proof ↗⚑ flag

Clm agentic

1. ai-native userHave an agent monitor contract renewals and deadlines through the product's API and act before they lapse

   weight 2 · round to Docusign
   Docusign~partialprobed7/10

   Docusign's REST API and new MCP connector explicitly expose agreement status, key dates, and metadata, and let AI agents (Claude, Gemini CLI, Copilot) trigger workflow actions through IAM tools, which supports agent-driven monitoring and pre-lapse action. However, there's no explicit documentation of renewal-specific alerts/triggers or an end-to-end example of an agent proactively acting before a deadline lapses, and no independent corroboration of this MCP monitoring workflow in production. Missing for 10: explicit renewal/deadline-triggered automation examples, third-party/hands-on validation of the MCP agent acting autonomously before lapse.

   • [claimed-docs] “Retrieve agreement context and metadata”
   • [claimed-docs] “Trigger workflow actions through IAM tools”
   • [claimed-docs] “The Docusign Connector in Anthropic Claude via MCP server provides a supported way to connect Claude to Docusign IAM capabilities.”
   • [claimed-docs] “Retrieve agreement context and metadata... Query agreement status and key dates... Trigger workflow actions through IAM tools”
   • [probe] “official MCP server documented at https://developers.docusign.com/platform/mcp-server/”
   • [claimed-docs] “Query agreement data and automate agreement processes from your terminal by pairing Gemini CLI with Docusign MCP.”
   • [claimed-docs] “Build agreement workflows: Docusign MCP & Claude”

   proof ↗⚑ flag

   Ironclad~partialclaimed5/10

   Ironclad exposes a Records API, Workflows API, and webhooks that could let an external agent poll contract data or receive event notifications and then trigger workflow actions via the API, which is the raw plumbing needed for automated renewal/deadline monitoring. However, there is no explicit documentation of a renewal-date or deadline field/endpoint, no webhook event specifically for upcoming expirations, and no mention of an agent-oriented monitoring pattern. Missing for 10: explicit renewal/deadline tracking endpoints or webhook events, documented example of automated pre-lapse action, independent/hands-on confirmation that this workflow works in practice.

   • [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
   • [claimed-docs] “Webhooks allow you to specify that we should POST to your URL when certain events happen.”
   • [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
   • [claimed-docs] “Integrations can also directly control the contract process, automatically blocking or pushing forward approvals.”
   • [claimed-docs] “integrations can read and write structured data from Ironclad, leaving the specifics around updating contract language and following approva…”

   proof ↗⚑ flag

Clm authoring

1. legal-ops leadDraft, negotiate, and redline contracts in a controlled workflow instead of email attachments

   weight 3 · round drawn
   Docusign~partialclaimed6/10

   Docusign CLM and AI-Assisted Review offer redlining, playbook-based suggested edits, and MS Word integration for contract negotiation, moving beyond email attachments, and web forms/templates support structured drafting workflows. However, evidence is entirely vendor-sourced marketing copy with no independent hands-on account of a full negotiation/redline cycle, and community threads focus on unrelated integration/security complaints rather than corroborating the CLM/redlining workflow. Missing for 10: independent or hands-on verification of the redline/negotiation workflow in practice, detail on multi-party version control during negotiation, and confirmation that AI-Assisted Review's Word integration handles full negotiation cycles reliably.

   • [claimed-docs] “use AI to flag non-compliant clauses, suggest approved language, and draft new clauses on demand”
   • [claimed-docs] “Use a drag-and-drop editor to design contract processes”
   • [claimed-docs] “Review and analyze agreements, flag potentially risky language, suggest surgical edits, and draft new language from an intuitive AI-powered …”
   • [claimed-docs] “Review agreements against your playbooks and ready-to-deploy agents and get suggested redlines to align terms with your requirements.”
   • [claimed-docs] “Docusign AI-Assisted Review integrates into MS Word to analyze, redline, and draft language based on your playbooks.”
   • [claimed-docs] “Generate contracts in a click with dynamic templates and use AI to flag non-compliant clauses, suggest approved language, and draft new clau…”
   • [claimed-docs] “Leverage AI to easily create new contract review playbooks based on your standard templates or other reference documents.”

   proof ↗⚑ flag

   Ironclad~partialclaimed6/10

   Ironclad's docs show core CLM capabilities relevant to the story—no-code contract creation, workflow designer for approvals, APIs to update contract language and control the process, and structured storage/signing—supporting a controlled workflow model instead of email attachments. However, the pack lacks explicit evidence of a redlining/track-changes or counterparty negotiation feature, and community citations are thin/tangential rather than corroborating negotiation workflows in practice. Missing for 10: explicit redline/version-comparison feature documentation, first-hand or independent evidence of negotiation collaboration replacing email attachments.

   • [claimed-docs] “Create Contracts in No-Code Builder”
   • [claimed-docs] “Built on how contracts really move.”
   • [claimed-docs] “integrations can read and write structured data from Ironclad, leaving the specifics around updating contract language and following approva…”
   • [claimed-docs] “Integrations can also directly control the contract process, automatically blocking or pushing forward approvals.”
   • [claimed-docs] “integrations can interface directly with underlying contract documents, reading contract text or updating new versions of the document”
   • [claimed-docs] “Published workflow design and Workflow Designer access: See your internal company admin for access to Workflow Designer.”
   • [claimed-docs] “In Workflow Designer, publish the workflow you wish to launch if it has not been published already.”

   proof ↗⚑ flag

Clm repository

1. legal-ops leadStore executed contracts in a searchable repository with key terms and metadata extracted

   weight 2 · round to Docusign
   Docusign✓fullclaimed7/10

   Docusign's IAM/CLM platform explicitly markets a searchable agreement repository ('Securely store and access all your agreements in one place', 'Find, analyze, and act on agreements powered by AI') plus metadata/key-term extraction via AI-assisted review and MCP connector features ('Retrieve agreement context and metadata', AI flags clauses and suggests terms). This directly matches the legal-ops story of a searchable repository with extracted key terms and metadata. missing for 10: independent/hands-on corroboration of the repository search and metadata-extraction UX, and detail on extraction accuracy or breadth of metadata fields captured

   • [claimed-docs] “Securely store and access all your agreements in one place”
   • [claimed-docs] “Find, analyze, and act on agreements powered by AI”
   • [claimed-docs] “Analyze agreements with AI, sign documents electronically, and automate workflows with the Intelligent Agreement Management (IAM) platform.”
   • [claimed-docs] “Retrieve agreement context and metadata”
   • [claimed-docs] “use AI to flag non-compliant clauses, suggest approved language, and draft new clauses on demand”
   • [claimed-docs] “Review and analyze agreements, flag potentially risky language, suggest surgical edits, and draft new language from an intuitive AI-powered …”
   • [claimed-docs] “Leverage AI to easily create new contract review playbooks based on your standard templates or other reference documents.”

   proof ↗⚑ flag

   Ironclad✓fullclaimed6/10

   Ironclad's marketing and developer docs explicitly describe a 'Store Contracts Securely, Find Them Easily' repository and a Records API for retrieving/updating structured contract metadata, plus an 'Ironclad AI'/Contract Intelligence product implying key-term extraction. Missing for 10: detailed documentation of specific extracted fields/metadata schema, search functionality specifics, and independent/hands-on corroboration of extraction accuracy.

   • [claimed-docs] “Store Contracts Securely, Find Them Easily”
   • [claimed-docs] “Store Contracts Securely, Find Them Easily | Ironclad”
   • [claimed-docs] “Built on how contracts really move.”
   • [claimed-docs] “A New Era of Contract Intelligence | Ironclad”
   • [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
   • [claimed-docs] “integrations can read and write structured data from Ironclad, leaving the specifics around updating contract language and following approva…”

   proof ↗⚑ flag

2. legal-ops leadTrack contract renewals, expirations, and obligations with automatic alerts

   weight 2 · round drawn
   Docusign—none0/10

   Docusign's CLM and IAM materials mention querying 'agreement status and key dates' and general agreement analysis, but no evidence describes automated renewal/expiration tracking or alerting for obligations. missing for 10: explicit renewal/expiration tracking feature, automatic alert/notification mechanism, obligation management documentation.

   • [claimed-docs] “Retrieve agreement context and metadata... Query agreement status and key dates... Trigger workflow actions through IAM tools”
   • [claimed-docs] “Analyze agreements with AI, sign documents electronically, and automate workflows with the Intelligent Agreement Management (IAM) platform.”
   • [claimed-docs] “Use a drag-and-drop editor to design contract processes”

   proof ↗⚑ flag

   Ironclad—none0/10

   The evidence pack covers Ironclad's contract creation, storage, signing, workflows, and API/webhooks, but nowhere mentions renewal tracking, expiration dates, obligation management, or automatic alerts—core to this story. Missing for 10: any documentation of renewal/expiration tracking, obligation management, or alerting/notification features.

   • [claimed-docs] “Store Contracts Securely, Find Them Easily”
   • [claimed-docs] “Store Contracts Securely, Find Them Easily | Ironclad”
   • [claimed-docs] “Webhooks allow you to specify that we should POST to your URL when certain events happen.”

   proof ↗⚑ flag

Clm workflow

1. legal-ops leadRoute contracts through configurable approval workflows before signature

   weight 2 · round to Ironclad
   Docusign~partialclaimed6/10

   Docusign explicitly markets configurable workflows (docusign-docs-4), CLM drag-and-drop process design (docusign-docs-17), and delegated signing (docusign-docs-9), and integrates with systems like Salesforce for auto-populating agreements (docusign-docs-24), which together support pre-signature approval routing. However, the evidence lacks detail on how approval-specific routing (multi-stage sign-off before signature) is configured, no independent/hands-on validation of workflow configuration exists, and community evidence focuses on embedded signing/security issues rather than approval workflows. Missing for 10: concrete documentation or demo of approval-stage routing logic, independent corroboration of workflow configurability, and detail on approval conditions/rules engine.

   • [claimed-docs] “take advantage of configurable workflows to tackle your trickiest agreement challenges”
   • [claimed-docs] “Use a drag-and-drop editor to design contract processes”
   • [claimed-docs] “Avoid delays by enabling delegated signing”
   • [claimed-docs] “Auto-populate new agreements with data from systems like Salesforce”
   • [claimed-docs] “Generate contracts in a click with dynamic templates and use AI to flag non-compliant clauses, suggest approved language, and draft new clau…”

   proof ↗⚑ flag

   Ironclad✓fullclaimed7/10

   Ironclad's docs describe Workflow Designer for building and publishing approval workflows, launching workflows via API/UI, and explicitly reference 'approval and signature policies' being enforced by the platform (docs-8, docs-15, docs-16, docs-20), directly matching the story of routing contracts through configurable approval steps before signature. Missing for 10: independent/hands-on verification of the approval-workflow configuration UI and no detailed walkthrough of multi-stage approval logic beyond brief doc mentions.

   • [claimed-docs] “Published workflow design and Workflow Designer access: See your internal company admin for access to Workflow Designer.”
   • [claimed-docs] “integrations can read and write structured data from Ironclad, leaving the specifics around updating contract language and following approva…”
   • [claimed-docs] “In Workflow Designer, publish the workflow you wish to launch if it has not been published already.”
   • [claimed-docs] “Integrations can also directly control the contract process, automatically blocking or pushing forward approvals.”
   • [claimed-docs] “Technical audiences will learn how to use Ironclad's API to launch workflows.”

   proof ↗⚑ flag

Doc api

1. 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 to Docusign
   Docusign~partialprobed6/10

   Docusign provides real building blocks: a REST/eSign API to create envelopes and route documents for signature (docusign-docs-21, docusign-docs-40), an official MCP server connector for Claude that can retrieve agreement context and 'trigger workflow actions through IAM tools' (docusign-docs-47, docusign-probe-3), and AI-assisted drafting/redlining features (docusign-docs-16, docusign-docs-20, docusign-docs-44) that could draft NDA language. However, no single documented workflow shows an agent drafting an NDA and then routing it end-to-end for signature purely via the MCP server or API in one flow — drafting lives in CLM/AI-Assisted Review while signature routing lives in eSignature API/MCP triggers, and there's no first-party or independent example stitching these together for a document like an NDA. missing for 10: an explicit worked example (docs or hands-on) of drafting+signature routing combined via MCP/API, independent confirmation the MCP trigger actions actually send envelopes, and any real-world demo showing this specific NDA-drafting-to-signature pipeline.

   • [claimed-docs] “Request Signatures & Automate Forms | REST API | Docusign”
   • [claimed-docs] “The Official Docusign Node.js Client Library used to interact with the eSign REST API. Send, sign, and approve documents using this client.”
   • [claimed-docs] “Retrieve agreement context and metadata... Query agreement status and key dates... Trigger workflow actions through IAM tools”
   • [claimed-docs] “use AI to flag non-compliant clauses, suggest approved language, and draft new clauses on demand”
   • [claimed-docs] “Review and analyze agreements, flag potentially risky language, suggest surgical edits, and draft new language from an intuitive AI-powered …”
   • [probe] “official MCP server documented at https://developers.docusign.com/platform/mcp-server/”
   • [claimed-docs] “Build agreement workflows: Docusign MCP & Claude”

   proof ↗⚑ flag

   Ironclad~partialprobed4/10

   Ironclad's Public API supports creating records from templates, launching workflows, and retrieving/interacting with workflows and contract data (ironclad-docs-2,5,13,23), which could technically support an agent drafting and routing an NDA end-to-end. However there is no evidence of an official MCP server, no explicit NDA-drafting example, and the docs note that approval/signature policies are handled by the platform rather than fully exposed for programmatic completion (ironclad-docs-15). Missing for 10: official MCP server, concrete NDA-draft-to-signature API walkthrough, independent confirmation of full automation without manual signature steps.

   • [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
   • [claimed-docs] “Technical audiences will learn how to use Ironclad's API to launch workflows.”
   • [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
   • [claimed-docs] “integrations can read and write structured data from Ironclad, leaving the specifics around updating contract language and following approva…”
   • [claimed-docs] “Template IDs can be obtained in-app or via API”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.ironcladapp.com/openapi.json, https://developer.ironcladapp.com/swagger.json, http…”

   proof ↗⚑ flag

2. developerGenerate, populate, and send legal documents programmatically through a documented API

   weight 3 · round to Ironclad
   Docusign!disputedcontradicted6/10

   Docusign ships a well-documented REST API, official OpenAPI specs, and client SDKs (e.g. Node.js) explicitly for generating, populating, and sending agreements programmatically, and some developers report smooth, well-documented integrations. However, other hands-on reports describe the API as an 'afterthought' compared to competitors, cite a security flaw in embedded signing flows, and describe failed/costly integration attempts, directly contradicting the polished vendor narrative. missing for 10: consistent independent confirmation without contradicting failure reports, and a working openapi.json/llms.txt discovery endpoint (both probes 404).

   • [claimed-docs] “Request Signatures & Automate Forms | REST API | Docusign”
   • [claimed-docs] “Docusign Developer Center | eSignature APIs & Resources | Docusign”
   • [github] “We use OpenAPI/Swagger files to build many of our developer tools including our client SDKs”
   • [claimed-docs] “Send, sign, and approve documents using this client.”
   • [community] “We did exactly this embedded signing integration and it was fairly seamless - built a POC in Postman in about an hour and a Jr dev built a p…”
   • [community] “We use the v2 REST API creating embedded envelope signing URLs without issues. Documentation is fantastic in its thoroughness - opposite exp…”
   • [community] “We wanted embedded flows with one API user, but discovered that on page refresh, users could break out of the signing page and view/click ar…”
   • [community] “If you're trying to wrap an e-sign provider within your application, I would recommend HelloSign 1000x. HelloSign's API is a first class cit…”
   • [community] “I once worked at a company that dealt with DocuSign integration; rumors were we paid more than double $20,000, and the integration never rea…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.docusign.com/openapi.json, https://developers.docusign.com/swagger.json, https://…”

   proof ↗⚑ flag

   Ironclad~partialprobed6/10

   Ironclad's developer docs describe a documented API (Workflows API to launch workflows, Records API to create/retrieve contract data, template IDs obtainable via API, webhooks for events) that supports generating, populating, and sending contracts programmatically. However, launching workflows still requires a pre-published Workflow Designer template (admin-gated, no-code step) rather than fully programmatic document creation, and there's no independent/hands-on developer corroboration of the API in practice, nor a discoverable OpenAPI spec (probe found only 404s). Missing for 10: independent developer testimonials of using the API end-to-end, a public OpenAPI/swagger spec, and evidence of fully code-driven document creation without the Workflow Designer dependency.

   • [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
   • [claimed-docs] “Technical audiences will learn how to use Ironclad's API to launch workflows.”
   • [claimed-docs] “Published workflow design and Workflow Designer access: See your internal company admin for access to Workflow Designer.”
   • [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
   • [claimed-docs] “In Workflow Designer, publish the workflow you wish to launch if it has not been published already.”
   • [claimed-docs] “Template IDs can be obtained in-app or via API”
   • [claimed-docs] “Webhooks allow you to specify that we should POST to your URL when certain events happen.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.ironcladapp.com/openapi.json, https://developer.ironcladapp.com/swagger.json, http…”

   proof ↗⚑ flag

Governance

1. legal-ops leadPrepare board consents and resolutions and collect approvals online

   weight 2 · round to Docusign
   Docusign✓fullcommunity7/10

   Docusign's core eSignature product supports creating reusable templates, configurable workflows, and routing for multi-party sign-off, which covers preparing and circulating documents like board consents/resolutions and collecting approvals online. However, there is no evidence of legal-ops-specific board-resolution templates or governance-specific workflow features, and community feedback flags integration/security friction that could affect legal-ops implementations. Missing for 10: dedicated board-resolution/corporate-governance templates, evidence of legal-ops specific approval chains (e.g., quorum tracking), and independent validation of reliability for this exact use case.

   • [claimed-docs] “take advantage of configurable workflows to tackle your trickiest agreement challenges”
   • [claimed-docs] “Save hours of manual setup with reusable templates”
   • [claimed-docs] “Standardize agreements by sharing templates with your team”
   • [claimed-docs] “Avoid delays by enabling delegated signing”
   • [claimed-docs] “Securely store and access all your agreements in one place”
   • [community] “We use the v2 REST API creating embedded envelope signing URLs without issues. Documentation is fantastic in its thoroughness - opposite exp…”

   proof ↗⚑ flag

   Ironclad~partialclaimed4/10

   Ironclad is a general contract lifecycle management platform with workflow builders, e-signature, and approval routing that could be used to create and route a board consent/resolution document for approval, but there is no specific evidence of board-consent/resolution templates, cap-table/equity-fundraising features, or governance-specific workflows tailored to legal-ops board approvals. missing for 10: evidence of board consent/resolution-specific templates or workflows, evidence of equity-fundraising or governance use cases, and independent validation that Ironclad is used for board approvals specifically rather than generic contracts.

   • [claimed-docs] “Create Contracts in No-Code Builder”
   • [claimed-docs] “Contract Signing Has Never Been Easier”
   • [claimed-docs] “Technical audiences will learn how to use Ironclad's API to launch workflows.”
   • [claimed-docs] “Published workflow design and Workflow Designer access: See your internal company admin for access to Workflow Designer.”

   proof ↗⚑ flag

Hiring

1. legal-ops leadRun hiring and equity paperwork — offer letters, confidentiality/IP agreements, and option grants — through the platform

   weight 2 · round to Docusign
   Docusign~partialclaimed5/10

   Docusign's generic eSignature and template/workflow features (reusable templates, configurable workflows, real-time collaboration, Salesforce integration) could be used to send and sign offer letters, IP agreements, or option grants, but there is no evidence of equity/HR-specific templates, cap-table or option-grant management integration, or hiring-specific workflow support. Missing for 10: dedicated offer-letter/option-grant templates, HR/equity system integrations (e.g., cap table tools like Carta), and any case study or docs specifically covering hiring/equity paperwork use cases.

   • [claimed-docs] “Save hours of manual setup with reusable templates”
   • [claimed-docs] “Standardize agreements by sharing templates with your team”
   • [claimed-docs] “take advantage of configurable workflows to tackle your trickiest agreement challenges”
   • [claimed-docs] “Easily integrate your agreements with your apps of choice, including Salesforce, Microsoft, Google, Zoom and more.”
   • [claimed-docs] “Send, sign, and succeed with the world’s #1 eSignature solution and the world’s #1 CRM, together.”

   proof ↗⚑ flag

   Ironclad~partialcommunity3/10

   Ironclad is a general-purpose CLM platform with no-code contract creation, workflows, and e-signature that could technically be configured to handle offer letters or NDAs (ironclad-docs-9, ironclad-docs-10, ironclad-comm-6 mentions using it for contractor onboarding), but there is no evidence of purpose-built templates, workflows, or integrations for hiring/equity paperwork specifically, especially option grants which typically require cap-table integration. Missing for 10: dedicated HR/equity templates, option grant or cap-table integration evidence, and any case study showing legal-ops running full hiring paperwork through Ironclad.

   • [claimed-docs] “Create Contracts in No-Code Builder”
   • [claimed-docs] “Contract Signing Has Never Been Easier”
   • [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
   • [community] “We use IronClad at Zinc and they are amazing. Whenever we have a new contractor, we shoot them an email (actually now we click a button) and…”

   proof ↗⚑ flag

Esign

1. founderSend a document for legally binding e-signature to multiple recipients with routing

   weight 3 · round to Docusign
   Docusign✓fullcommunity8/10

   Docusign's core eSignature product explicitly supports configurable workflows, delegated signing, and sending to multiple recipients with routing, backed by extensive first-party docs and a mature REST API/SDKs for building signing flows. Community evidence (comm-4, comm-5) corroborates that embedded/API-based signing works smoothly in practice, though other community reports focus on unrelated integration/security complaints rather than the routing feature itself. Missing for 10: independent hands-on confirmation specifically of multi-recipient sequential/parallel routing behavior (most community evidence discusses embedded signing or security, not routing order).

   • [claimed-docs] “Send, sign and manage all your agreements for free.”
   • [claimed-docs] “take advantage of configurable workflows to tackle your trickiest agreement challenges”
   • [claimed-docs] “Avoid delays by enabling delegated signing”
   • [claimed-docs] “Request Signatures & Automate Forms | REST API | Docusign”
   • [community] “We did exactly this embedded signing integration and it was fairly seamless - built a POC in Postman in about an hour and a Jr dev built a p…”
   • [community] “We use the v2 REST API creating embedded envelope signing URLs without issues. Documentation is fantastic in its thoroughness - opposite exp…”

   proof ↗⚑ flag

   Ironclad~partialclaimed6/10

   Ironclad markets a dedicated 'Sign Contracts' capability and documents a Workflow Designer/Workflows API that lets processes 'follow approval and signature policies,' implying routing across multiple parties, and workflows can be launched via API for automation. However, the pack lacks concrete detail on multi-recipient routing order, legally-binding signature specifics, or independent verification of the e-signature flow working end-to-end. Missing for 10: explicit documentation of multi-recipient signing order/routing configuration, legal-binding compliance details (e.g., ESIGN/UETA), and independent/hands-on confirmation of the signature flow.

   • [claimed-docs] “Contract Signing Has Never Been Easier”
   • [claimed-docs] “Contract Signing Has Never Been Easier | Ironclad”
   • [claimed-docs] “integrations can read and write structured data from Ironclad, leaving the specifics around updating contract language and following approva…”
   • [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
   • [claimed-docs] “Technical audiences will learn how to use Ironclad's API to launch workflows.”
   • [claimed-docs] “In Workflow Designer, publish the workflow you wish to launch if it has not been published already.”

   proof ↗⚑ flag

Esign embed

1. developerEmbed the signing experience inside my own app or website

   weight 2 · round to Ironclad
   Docusign!disputedcontradicted6/10

   Docusign's docs and API support embedding signing/forms into apps (docusign-docs-43 embed forms, docusign-docs-21/22 REST API for building custom flows), and community reports confirm working embedded signing integrations built via the REST API (docusign-comm-4, docusign-comm-5). However, a separate hands-on account documents a concrete security flaw in the embedded signing flow — users could break out of the signing iframe and access the whole account, forcing a downgrade to a legacy API (docusign-comm-1) — a documented counter-example that contradicts the claim of a clean embed experience. Missing for 10: first-party embedded-signing quickstart/tutorial evidence, resolution confirmation of the reported security issue, and independent recent corroboration beyond a single old HN thread.

   • [claimed-docs] “Embed forms directly into your business applications, so your customers get the consistent user experience and look they expect from your br…”
   • [claimed-docs] “Request Signatures & Automate Forms | REST API | Docusign”
   • [community] “We wanted embedded flows with one API user, but discovered that on page refresh, users could break out of the signing page and view/click ar…”
   • [community] “We did exactly this embedded signing integration and it was fairly seamless - built a POC in Postman in about an hour and a Jr dev built a p…”
   • [community] “We use the v2 REST API creating embedded envelope signing URLs without issues. Documentation is fantastic in its thoroughness - opposite exp…”
   • [community] “If you're trying to wrap an e-sign provider within your application, I would recommend HelloSign 1000x. HelloSign's API is a first class cit…”

   proof ↗⚑ flag

   Ironclad✓fullclaimed7/10

   Ironclad provides documented Clickwrap Workflow embedding via iframe for signing/agreement flows directly on a developer's own page. Missing for 10: independent hands-on confirmation of the embedding working in production, and broader coverage beyond clickwrap (e.g., full contract e-signature embedding) is not detailed.

   • [claimed-docs] “This is a simple example outlining how to embed a clickwrap within an iframe.”
   • [claimed-docs] “Technical audiences will learn how to use Ironclad's Clickwrap Workflow to implement embedded clickwrap in their own pages.”
   • [claimed-docs] “This guide will cover the steps for embedding a clickwrap in your own page, once you have created and published a Clickwrap Workflow.”

   proof ↗⚑ flag

Esign scale

1. legal-ops leadBulk-send the same document to many recipients at once

   weight 1 · round drawn
   Docusign—none0/10

   The evidence pack describes templates, workflows, branding, identity verification, and AI features but never mentions a bulk-send/mass-mail capability for sending one document to many recipients simultaneously. Missing for 10: any documentation of a 'bulk send' or mass-recipient distribution feature, recipient list upload, or per-recipient tracking at scale.

   ⚑ flag

   Ironclad—none0/10

   Evidence shows Ironclad's Workflow API can launch individual contract workflows and clickwraps can be embedded, but there is no documentation or feature reference to a bulk-send capability (sending one document to many recipients simultaneously). Missing for 10: any mention of bulk-send, mail-merge-style multi-recipient dispatch, or batch signature request tooling.

   • [claimed-docs] “Technical audiences will learn how to use Ironclad's API to launch workflows.”
   • [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
   • [claimed-docs] “In Workflow Designer, publish the workflow you wish to launch if it has not been published already.”

   proof ↗⚑ flag

2. legal-ops leadSet signing order, automatic reminders, and expirations on outstanding signature requests

   weight 1 · round to Docusign
   Docusign~partialclaimed3/10

   Evidence only vaguely references 'configurable workflows' and 'delegated signing' for agreement flows, with no explicit documentation of signing order/routing, automatic reminder scheduling, or envelope expiration settings, which are the specific capabilities the story asks about. Missing for 10: explicit docs on setting signer routing order, reminder frequency/timing configuration, and expiration date settings for envelopes.

   • [claimed-docs] “take advantage of configurable workflows to tackle your trickiest agreement challenges”
   • [claimed-docs] “Avoid delays by enabling delegated signing”

   proof ↗⚑ flag

   Ironclad—none0/10

   Evidence only shows generic e-signature and workflow/API pages but no mention of configuring signing order, automatic reminders, or expiration settings on signature requests. Missing for 10: any documentation of signing order configuration, reminder scheduling, or expiration/timeout settings for signature requests.

   • [claimed-docs] “Contract Signing Has Never Been Easier”
   • [claimed-docs] “Contract Signing Has Never Been Easier | Ironclad”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round drawn
   Docusign~partialprobed5/10

   Docusign publishes a comprehensive eSignature REST API, SDKs, OpenAPI specs, and an MCP server enabling programmatic sending, signing, and workflow triggering (docusign-docs-21, docusign-gh-1, docusign-docs-47, docusign-probe-3), but several UI-only capabilities (CLM drag-and-drop process builder, web-forms drag-and-drop editor, AI-assisted review chat) are marketed as click/drag experiences without documented API equivalents. Community reports also describe real API limitations/security issues in embedded signing flows that forced a downgrade to a legacy API (docusign-comm-1), undercutting full UI/API parity. Missing for 10: explicit API endpoints for CLM workflow design, web-forms builder, and AI-review features, plus independent confirmation that all UI actions are API-reachable without workarounds.

   • [claimed-docs] “Request Signatures & Automate Forms | REST API | Docusign”
   • [github] “We use OpenAPI/Swagger files to build many of our developer tools including our client SDKs”
   • [claimed-docs] “Retrieve agreement context and metadata... Query agreement status and key dates... Trigger workflow actions through IAM tools”
   • [probe] “official MCP server documented at https://developers.docusign.com/platform/mcp-server/”
   • [community] “We wanted embedded flows with one API user, but discovered that on page refresh, users could break out of the signing page and view/click ar…”
   • [claimed-docs] “Use a drag-and-drop editor to design contract processes”
   • [claimed-docs] “Use drag-and-drop functionality and clicks, not code, to build your forms in minutes.”

   proof ↗⚑ flag

   Ironclad~partialprobed5/10

   Ironclad exposes a broad API (Records, Workflows, Webhooks, Data Exports, launching published workflows) letting AI-native users read/write core contract data and trigger processes, but design-time actions like building/publishing workflows and templates are explicitly UI/no-code-builder only ('See your internal company admin for access to Workflow Designer'), and no public OpenAPI spec was found (probe returned 404s for all standard spec paths), indicating incomplete machine-discoverable parity with the UI. missing for 10: API-driven workflow/template design and publishing, a public OpenAPI/schema for full endpoint discovery, and independent confirmation that all UI actions (e.g., clickwrap embedding config, template creation) are API-accessible.

   • [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
   • [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
   • [claimed-docs] “Published workflow design and Workflow Designer access: See your internal company admin for access to Workflow Designer.”
   • [claimed-docs] “In Workflow Designer, publish the workflow you wish to launch if it has not been published already.”
   • [claimed-docs] “Create Contracts in No-Code Builder”
   • [claimed-docs] “Client submits an API request via Public API with request body payload to trigger an export job”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.ironcladapp.com/openapi.json, https://developer.ironcladapp.com/swagger.json, http…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round to Ironclad
   Docusign—none0/10

   The evidence pack shows Docusign APIs for sending/retrieving individual agreements and metadata, but no documented bulk data-export tool, account-closure export, or open-format portability feature that would let a user extract all their data and leave the platform.

   ⚑ flag

   Ironclad~partialclaimed5/10

   Ironclad documents a Data Exports API and Records/Workflows APIs that let customers retrieve their contract records and trigger export jobs, which supports data portability, but nothing explicitly states the export format is open/standard (e.g., JSON/CSV) or that a full, wholesale data exit is guaranteed. missing for 10: explicit statement of open export formats, documentation of a full account data export/deletion process, and independent confirmation that customers can fully migrate off Ironclad.

   • [claimed-docs] “Client submits an API request via Public API with request body payload to trigger an export job”
   • [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
   • [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
   • [claimed-docs] “integrations can read and write structured data from Ironclad, leaving the specifics around updating contract language and following approva…”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Docusign—none0/10

   No evidence in the pack addresses data residency, regional storage options, or geographic data controls for Docusign; all citations focus on e-signature features, AI capabilities, integrations, and unrelated community complaints. Missing for 10: any mention of data center regions, EU/US data residency options, or customer-selectable storage location settings.

   ⚑ flag

   Ironclad—none0/10

   No evidence in the pack mentions data residency, regional storage options, or geographic hosting controls for Ironclad; the docs focus on API, workflows, and contract management only. Missing for 10: any mention of region selection, data residency guarantees, or geo-specific hosting infrastructure.

   ⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round drawn
   Docusign—none0/10

   The evidence pack contains no mention of AI training data opt-out, data usage policies, or privacy controls specific to AI model training; only unrelated feature and integration descriptions plus community complaints about API issues and phishing. Missing for 10: any documented opt-out/consent mechanism for AI training, privacy policy language on data usage, or admin controls to restrict data use for model training.

   ⚑ flag

   Ironclad—none0/10

   No evidence in the pack addresses AI training data usage, opt-out controls, or data privacy policies regarding model training; the pack only covers API/product features and unrelated community feedback.

   ⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Docusign—none0/10

   No evidence in the pack addresses data retention policies, deletion controls, or configurable data lifecycle management for AI/agent interactions; the evidence covers e-signature, CLM, identity verification, and MCP connector features but nothing about retention/deletion settings.

   ⚑ flag

   Ironclad—none0/10

   The evidence pack covers API/webhook/workflow documentation and data export jobs, but contains no mention of data retention policies, deletion controls, or AI-training data opt-outs. This is a fair axis for any SaaS handling contract data, so absence of evidence means 'none' rather than 'na'.

   ⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round drawn
   Docusign—none0/10

   No evidence in the pack addresses telemetry/usage-tracking opt-out settings for Docusign or its AI features; the pack covers product features, integrations, and unrelated community complaints. This axis applies to any AI-native product handling user data, but no documentation of an opt-out mechanism exists.

   ⚑ flag

   Ironclad—none0/10

   No evidence in the pack addresses telemetry, usage tracking, or an opt-out mechanism for AI-native or any users; documentation focuses on API, workflows, and contract features.

   ⚑ flag

Templates

1. founderStart from a library of vetted standard legal templates (NDAs, agreements, policies) instead of hiring counsel for routine documents

   weight 2 · round to Ironclad
   Docusign—none0/10

   Docusign's evidence describes reusable/custom templates that users build and share within their own workflows (e.g., docusign-docs-6, docusign-docs-7, docusign-docs-34), but there is no mention of a pre-built, vetted library of standard legal documents (NDAs, agreements, policies) that a founder could use in place of counsel. Docusign's template features are about reusing your own document setup, not sourcing vetted legal content.

   • [claimed-docs] “Save hours of manual setup with reusable templates”
   • [claimed-docs] “Standardize agreements by sharing templates with your team”
   • [claimed-docs] “Reduce prep time by standardizing your most-used agreements.”

   proof ↗⚑ flag

   Ironclad!disputedcontradicted3/10

   Ironclad markets contract creation tools (No-Code Builder, workflow templates) that could serve as a template library, but hands-on community feedback from early users directly disputes the 'vetted standard legal templates' framing: users questioned whether the templates constituted unauthorized practice of law and whether Ironclad carried malpractice insurance, and the company pulled the product to rethink it rather than defend the templates as reliable substitutes for counsel. Missing for 10: any current documentation of a curated NDA/agreement/policy template library, evidence of legal vetting or counsel review, and independent validation that founders can safely skip a lawyer.

   • [claimed-docs] “Create Contracts in No-Code Builder”
   • [claimed-docs] “Create Contracts in No-Code Builder | Ironclad”
   • [community] “This appears to be the unauthorized practice of law... I'll give you guys a week to rethink your service and get a lawyer on board, but next…”
   • [community] “What is up with the pre-loaded 'industry standard' templates? Are you guys a law firm? Do you carry malpractice insurance in case these temp…”
   • [community] “Hey everyone, thanks a ton for your comments and interest. Now that we've had a chance to get some feedback, we'll be closing up the site wh…”
   • [community] “Full disclosure: Actual flesh-and-blood lawyer here. These tools are great when things are going well... you might be pushing off minor expe…”

   proof ↗⚑ flag