Skip to content
ProductArena

How Docusign’s scores are calculated

The full audit trail, recomputed from the verdict data at build time through the same code that produced the leaderboard: verdict × quality × story weight per cell, cells sum to dimension scores, dimensions blend into the PA Score. Every number on the product page is reproducible from this page alone; for why the formula looks like this, see the methodology.

verdict factors: full ×1.0 · partial ×0.6 · disputed ×0.3 · none ×0.0 · n/a excluded from both sides · cell points = weight × quality × factor · cell max = weight × 10

PA Score27/100

Agent-ready 36.8 × 0.30 = 11.04

API quality 25.4 × 0.20 = 5.08

Openness 8.6 × 0.20 = 1.72

Built-in AI 51.1 × 0.15 = 7.67

Automation 11.3 × 0.15 = 1.70

(11.04 + 5.08 + 1.72 + 7.67 + 1.70) ÷ (0.30 + 0.20 + 0.20 + 0.15 + 0.15) = 27.20 ÷ 1.00 = 27.2

Scores are stored to 1 decimal; the product page’s pills round to whole numbers for display. Each dimension below shows the stories, verdicts, and cited evidence behind its number.

Agent-ready36.8/100×0.30 of the PA blend

Outside-in: can YOUR agent reach and drive this product — API, MCP, CLI, headless runs, agent docs.

Point an agent at llms.txt or agent-oriented docsweight 2

2 (weight) × 5 (quality) × 0.6 (partial) = 6.0 of 20 max

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

Run the product headlessly / in CI for automationweight 2

2 (weight) × 6 (quality) × 0.6 (partial) = 7.2 of 20 max

  • [claimed-docs] https://developers.docusign.com/docs/esign-rest-api/“Request Signatures & Automate Forms | REST API | Docusign”
  • [claimed-docs] https://github.com/docusign/docusign-esign-node-client“Send, sign, and approve documents using this client.”
  • [claimed-docs] https://github.com/docusign/docusign-esign-node-client“The Official Docusign Node.js Client Library used to interact with the eSign REST API. Send, sign, and approve documents using this client.”
  • [github] https://github.com/docusign/OpenAPI-Specifications“We use OpenAPI/Swagger files to build many of our developer tools including our client SDKs”
  • [github] https://github.com/docusign/OpenAPI-Specifications“allows both humans and computers to discover and understand the capabilities of the service”
  • [claimed-docs] https://www.docusign.com/integrations“Query agreement data and automate agreement processes from your terminal by pairing Gemini CLI with Docusign MCP.”
  • [community] https://news.ycombinator.com/item?id=18989744“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 production service managing all our DocuSign integration.”
  • [community] https://news.ycombinator.com/item?id=18989744“We use the v2 REST API creating embedded envelope signing URLs without issues. Documentation is fantastic in its thoroughness - opposite experience of the failed integration described.”

Plug MCP servers into this product so it can use their toolsweight 3

3 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 30 max

  • [claimed-docs] https://www.docusign.com/blog/developers/claude-docusign-mcp-connector-guide“The Docusign Connector in Anthropic Claude via MCP server provides a supported way to connect Claude to Docusign IAM capabilities.”
  • [claimed-docs] https://www.docusign.com/integrations“Query agreement data and automate agreement processes from your terminal by pairing Gemini CLI with Docusign MCP.”
  • [claimed-docs] https://www.docusign.com/blog/developers/claude-docusign-mcp-connector-guide“Build agreement workflows: Docusign MCP & Claude”
  • [probe] https://developers.docusign.com/platform/mcp-server/“official MCP server documented at https://developers.docusign.com/platform/mcp-server/”

Connect an agent via an official MCP serverweight 3

3 (weight) × 8 (quality) × 1.0 (full) = 24.0 of 30 max

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

Use an official CLIweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

  • [claimed-docs] https://www.docusign.com/integrations“Query agreement data and automate agreement processes from your terminal by pairing Gemini CLI with Docusign MCP.”
  • [claimed-docs] https://developers.docusign.com/docs/esign-rest-api/“Request Signatures & Automate Forms | REST API | Docusign”
  • [claimed-docs] https://github.com/docusign/docusign-esign-node-client“The Official Docusign Node.js Client Library used to interact with the eSign REST API. Send, sign, and approve documents using this client.”

Drive the product through a documented public APIweight 3

3 (weight) × 8 (quality) × 1.0 (full) = 24.0 of 30 max

  • [claimed-docs] https://developers.docusign.com/docs/esign-rest-api/“Request Signatures & Automate Forms | REST API | Docusign”
  • [claimed-docs] https://developers.docusign.com“Docusign Developer Center | eSignature APIs & Resources | Docusign”
  • [github] https://github.com/docusign/OpenAPI-Specifications“We use OpenAPI/Swagger files to build many of our developer tools including our client SDKs”
  • [github] https://github.com/docusign/OpenAPI-Specifications“allows both humans and computers to discover and understand the capabilities of the service”
  • [github] https://github.com/docusign/OpenAPI-Specifications“We use OpenAPI/Swagger files to build many of our developer tools including our client SDKs using `swagger-codegen`.”
  • [claimed-docs] https://github.com/docusign/docusign-esign-node-client“Send, sign, and approve documents using this client.”
  • [claimed-docs] https://github.com/docusign/docusign-esign-node-client“The Official Docusign Node.js Client Library used to interact with the eSign REST API. Send, sign, and approve documents using this client.”
  • [community] https://news.ycombinator.com/item?id=18989744“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 production service managing all our DocuSign integration.”
  • [community] https://news.ycombinator.com/item?id=18989744“We use the v2 REST API creating embedded envelope signing URLs without issues. Documentation is fantastic in its thoroughness - opposite experience of the failed integration described.”
  • [probe] https://developers.docusign.com/openapi.json“PROBE openapi: all candidate paths 404 (https://developers.docusign.com/openapi.json, https://developers.docusign.com/swagger.json, https://developers.docusign.com/api/openapi.json, https://developers.docusign.com/.well-known/openapi.json)”

Issue scoped/least-privilege API credentials for an agentweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

  • [claimed-docs] https://www.docusign.com/blog/developers/claude-docusign-mcp-connector-guide“The Docusign Connector in Anthropic Claude via MCP server provides a supported way to connect Claude to Docusign IAM capabilities.”
  • [claimed-docs] https://www.docusign.com/blog/developers/claude-docusign-mcp-connector-guide“Retrieve agreement context and metadata... Query agreement status and key dates... Trigger workflow actions through IAM tools”
  • [community] https://news.ycombinator.com/item?id=18989744“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 around the entire account's data. DocuSign's fix required shifting to a legacy API version with no promise against sunsetting.”

Build against official SDKsweight 2

2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max

  • [claimed-docs] https://github.com/docusign/docusign-esign-node-client“Send, sign, and approve documents using this client.”
  • [claimed-docs] https://github.com/docusign/docusign-esign-node-client“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] https://developers.docusign.com/docs/esign-rest-api/“Request Signatures & Automate Forms | REST API | Docusign”
  • [claimed-docs] https://developers.docusign.com“Docusign Developer Center | eSignature APIs & Resources | Docusign”
  • [github] https://github.com/docusign/OpenAPI-Specifications“We use OpenAPI/Swagger files to build many of our developer tools including our client SDKs”
  • [github] https://github.com/docusign/OpenAPI-Specifications“We use OpenAPI/Swagger files to build many of our developer tools including our client SDKs using `swagger-codegen`.”
  • [community] https://news.ycombinator.com/item?id=18989744“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 production service managing all our DocuSign integration.”
  • [community] https://news.ycombinator.com/item?id=18989744“We use the v2 REST API creating embedded envelope signing URLs without issues. Documentation is fantastic in its thoroughness - opposite experience of the failed integration described.”
  • [probe] https://developers.docusign.com/llms.txt“PROBE llms.txt: HTTP 404 at https://developers.docusign.com/llms.txt”
  • [probe] https://developers.docusign.com/openapi.json“PROBE openapi: all candidate paths 404 (https://developers.docusign.com/openapi.json, https://developers.docusign.com/swagger.json, https://developers.docusign.com/api/openapi.json, https://developers.docusign.com/.well-known/openapi.json)”

Subscribe to events via webhooksweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Agent-ready = 77.2 ÷ 210 × 100 = 36.8

API quality25.4/100×0.20 of the PA blend

The programmable surface once an agent is there — machine-readable spec, interactive docs, sandbox, versioning discipline.

Explore an interactive API reference with runnable examplesweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

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

Download a machine-readable API spec (OpenAPI or equivalent)weight 2

2 (weight) × 8 (quality) × 1.0 (full) = 16.0 of 20 max

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

Test against a sandbox environment without touching production dataweight 1

1 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 10 max

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Rely on versioned APIs with a documented deprecation policyweight 2

2 (weight) × 3 (quality) × 0.3 (disputed) = 1.8 of 20 max

  • [community] https://news.ycombinator.com/item?id=18989744“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 around the entire account's data. DocuSign's fix required shifting to a legacy API version with no promise against sunsetting.”
  • [community] https://news.ycombinator.com/item?id=18989744“We use the v2 REST API creating embedded envelope signing URLs without issues. Documentation is fantastic in its thoroughness - opposite experience of the failed integration described.”
  • [github] https://github.com/docusign/OpenAPI-Specifications“We use OpenAPI/Swagger files to build many of our developer tools including our client SDKs”
  • [claimed-docs] https://developers.docusign.com/docs/esign-rest-api/“Request Signatures & Automate Forms | REST API | Docusign”

API quality = 17.8 ÷ 70 × 100 = 25.4

Openness8.6/100×0.20 of the PA blend

Can you leave, inspect, or self-host — data export, open source, portability.

Do everything through the API that I can do in the UIweight 2

2 (weight) × 5 (quality) × 0.6 (partial) = 6.0 of 20 max

  • [claimed-docs] https://developers.docusign.com/docs/esign-rest-api/“Request Signatures & Automate Forms | REST API | Docusign”
  • [github] https://github.com/docusign/OpenAPI-Specifications“We use OpenAPI/Swagger files to build many of our developer tools including our client SDKs”
  • [claimed-docs] https://www.docusign.com/blog/developers/claude-docusign-mcp-connector-guide“Retrieve agreement context and metadata... Query agreement status and key dates... Trigger workflow actions through IAM tools”
  • [probe] https://developers.docusign.com/platform/mcp-server/“official MCP server documented at https://developers.docusign.com/platform/mcp-server/”
  • [community] https://news.ycombinator.com/item?id=18989744“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 around the entire account's data. DocuSign's fix required shifting to a legacy API version with no promise against sunsetting.”
  • [claimed-docs] https://www.docusign.com/products/clm“Use a drag-and-drop editor to design contract processes”
  • [claimed-docs] https://www.docusign.com/products/web-forms“Use drag-and-drop functionality and clicks, not code, to build your forms in minutes.”

Export all of my data in open formats and leaveweight 3

3 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 30 max

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Read the product's source under an open licenseweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Self-host the core productweight 3

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Openness = 6.0 ÷ 70 × 100 = 8.6

Built-in AI51.1/100×0.15 of the PA blend

Inside-out: how agentic the product itself is for its users — built-in assistants, autonomous features.

Get AI-generated insights and suggestions from my data inside the productweight 2

2 (weight) × 7 (quality) × 1.0 (full) = 14.0 of 20 max

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

Set up automations that run autonomously in the backgroundweight 2

2 (weight) × 6 (quality) × 0.6 (partial) = 7.2 of 20 max

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

Delegate tasks to a built-in AI assistant inside the productweight 3

3 (weight) × 6 (quality) × 0.6 (partial) = 10.8 of 30 max

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

Operate the product with natural-language commandsweight 2

2 (weight) × 7 (quality) × 1.0 (full) = 14.0 of 20 max

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

Built-in AI = 46.0 ÷ 90 × 100 = 51.1

Automation11.3/100×0.15 of the PA blend

Depth of automation primitives — rules, scheduling, bulk operations, webhooks.

Perform bulk operations across many items at onceweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

  • [claimed-docs] https://developers.docusign.com/docs/esign-rest-api/“Request Signatures & Automate Forms | REST API | Docusign”
  • [claimed-docs] https://github.com/docusign/docusign-esign-node-client“Send, sign, and approve documents using this client.”
  • [claimed-docs] https://www.docusign.com/blog/developers/claude-docusign-mcp-connector-guide“Retrieve agreement context and metadata”
  • [claimed-docs] https://www.docusign.com/blog/developers/claude-docusign-mcp-connector-guide“Trigger workflow actions through IAM tools”
  • [claimed-docs] https://www.docusign.com/blog/developers/claude-docusign-mcp-connector-guide“Retrieve agreement context and metadata... Query agreement status and key dates... Trigger workflow actions through IAM tools”

Define rules that trigger actions automatically on eventsweight 3

3 (weight) × 5 (quality) × 0.6 (partial) = 9.0 of 30 max

  • [claimed-docs] https://www.docusign.com/products/electronic-signature“take advantage of configurable workflows to tackle your trickiest agreement challenges”
  • [claimed-docs] https://www.docusign.com/products/clm“Use a drag-and-drop editor to design contract processes”
  • [claimed-docs] https://www.docusign.com/products/web-forms“implement conditional logic to ensure only relevant fields appear”
  • [claimed-docs] https://www.docusign.com/products/identify“Dynamically adjust the type of verification your signers must complete based on an automated and instant risk assessment with our Risk-Based Verification workflow”
  • [claimed-docs] https://www.docusign.com/blog/developers/claude-docusign-mcp-connector-guide“Trigger workflow actions through IAM tools”
  • [claimed-docs] https://www.docusign.com/blog/developers/claude-docusign-mcp-connector-guide“Retrieve agreement context and metadata... Query agreement status and key dates... Trigger workflow actions through IAM tools”
  • [claimed-docs] https://www.docusign.com/products/clm“Generate contracts in a click with dynamic templates and use AI to flag non-compliant clauses, suggest approved language, and draft new clauses on demand.”

Schedule recurring jobs or workflowsweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Version, review, and roll back my automationsweight 1

1 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 10 max

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Automation = 9.0 ÷ 80 × 100 = 11.3