Head to head · E-signatures · October 2026 research run

Docusign vs PandaDoc

Docusign scores 66.3 (B) on agent readiness against PandaDoc's 65 (B), and leads in 4 of 7 scored categories. PandaDoc leads on reliability and schema & documentation. Both do e-signatures.

Best contract, proposal and e-signature APIs for AI agents · All 59 e-signatures comparisons

Which one, for what

Docusign B

Best for Teams whose company already uses Docusign and needs an agent to send envelopes from templates, embed signing and track status with a full audit trail.

Ahead on

  • Security & auth, 69 against 61
  • Transparency & trust, 73 against 59

Also in its favour

  • No incidents deducted, where PandaDoc loses 3 points for them

Watch for

The Python SDK's last stable release is 6.1.0 of 13 March 2026, with only release candidates since

PandaDoc B

Best for Suited to agents that prepare a proposal, quote or contract from a template, send it for signature and track it, for a team that already works in PandaDoc.

Ahead on

  • Reliability, 73 against 62
  • Schema & documentation, 87 against 70

Watch for

Pricing-table sections became required on document creation on 21 September 2026, announced the same day

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Schema & documentation PandaDoc +17

Docusign 70

Spec files for eSignature v2.1 (Swagger 2.0, 213 paths, 414 operations, re-read on 2 November; the repository's last commit is 3 July 2026, build 26.2.01.01) and ten other APIs are public under MIT in docusign/OpenAPI-Specifications. The MCP tool schemas sit behind sign-in, so the API carries this line (25). developers.docusign.com/llms.txt returns 404 on 2 November, and no Markdown copy of the docs was found (0). Operation descriptions are long and say what a call is for (the median is 179 characters and Envelopes:create explains drafts, templates and required fields), though 43 of 414 are under 40 characters (15 of 20). The eSignature spec has no enum and no required list on any schema, and no security definitions. Valid values are listed in prose (6 of 15). Docusign keeps code examples in six languages on GitHub, and its 23 June 2026 developer post lists 16 error codes with status, message and fix, but the spec documents only a 400 with errorCode and message on every operation (12 of 15). The API is versioned (v2.1, builds such as 26.3.01.02) and the SDK changelogs are dated (12 of 15). The Developer Center renders by script, and its guide, error-code and changelog pages were read on 1 and 7 October through the site's page data, which this run doesn't read, so those readings are struck and this note rests on the spec, the SDK repositories and Docusign's blog. 25 + 0 + 15 + 6 + 12 + 12 = 70.

PandaDoc 87

Scored on the REST API. The MCP server's tool definitions are visible only after OAuth sign-in. A public OpenAPI 3.0.3 spec under MIT in PandaDoc's GitHub repository, version 8.25.1 of 29 October 2026 with 135 operations. openapi.pandadoc.com now disallows every path in robots.txt, so the 7 October reading from that host is struck and the repository copy stands in (25). llms.txt at developers.pandadoc.com with a Markdown copy of each page (10). Every operation has a description, median 193 characters, and the main ones state preconditions, such as Send Document needing document.draft status. Few say when not to use an endpoint (15 of 20). Enums, required fields and ID patterns are present, while Create Document is a oneOf whose tokens, fields and metadata are loosely typed objects (11 of 15). More than 1,300 examples in the spec, 429 listed on 121 operations and 401 on 119, and an error object with a code and message on newer endpoints (13 of 15). URL versioning (/v1, /v2, /beta), a semver spec and a dated changelog, though the docs changelog stops at 8.21.0 while the repository has reached 8.25.1 (13 of 15).

Transparency & trust Docusign +14

Docusign 73

The service is closed under a Master Services Agreement dated 14 November 2022. The spec files and SDKs are MIT (15). The data protection attachment of 4 September 2024 promises prompt deletion after termination without a number of days, and the privacy notice gives no retention periods. The privacy notice says systems are designed to avoid training models on customers' personal information without consent, and the AI attachment of 8 July 2026 takes that consent for AI improvement data with an opt-out toggle (20 of 30). No written deprecation policy was found. Changes are announced in dated posts, such as the 23 June 2026 notice of status-code changes rolling out to production in July (6 of 20). The sub-processor list was last updated on 8 October 2026 (re-read on 2 November) and has an RSS feed, the attachment gives 30 days' notice of new sub-processors, and the privacy notice names Australia, the United States, the European Union and Canada as storage locations (18 of 20). 15 + 20 + 6 + 18 = 59.

PandaDoc 59

The service is closed under a Master Services Agreement named in the OpenAPI spec. That page refused our reader, so the terms are unread, while the spec, the SDKs and the MCP guide are MIT (8 of 30). The AI policy says customer content isn't used to train models and that third-party AI providers can't retain it, with an opt-out for aggregated usage data. The compliance article says signed documents are kept for the length of the customer relationship. The privacy notice and DPA were not read, so agreement between them is unconfirmed (12 of 30). No written deprecation policy found. The spec marks six items deprecated and the auth overview labels API keys legacy, without removal dates (5 of 20). The docs describe separate US and EU regions and US-only AI processing. A sub-processor page exists at www.pandadoc.com/legal/subprocessors but refused our reader (8 of 20, partly unchecked).

Reliability PandaDoc +11

Docusign 62

Read with the hosted lines and scored on the eSignature REST API, with the MCP server noted. health.docusign.com is Docusign's own status centre with incidents and maintenances by product and site, severity levels and a history view (20). The page draws its incidents by script from a data feed on the same host. The 7 October count came from that feed, which this run's rules don't read, so it's struck, and the window from 4 August to 2 November is unread (5). Limits have numbers, 3,000 API calls an hour per account and a 500-call 30-second burst limit, in Docusign's developer blog, re-read on 2 November (15). The same post names the x-ratelimit headers and the burst reset, and the 23 June 2026 post moved hourly, burst and polling limit errors to HTTP 429 so standard backoff and retry applies. The spec's transactionId lets a sender check whether an envelope was created after a lost response, valid for seven days, but there's no general idempotency key (12 of 15). No SLA was found in the Master Services Agreement or the terms index (0). The eSignature API v2.1 is generally available (10). 20 + 5 + 15 + 12 + 0 + 10 = 62.

PandaDoc 73

Read with the hosted lines and scored on the REST API, which the hosted MCP server calls. status.pandadoc.com on Statuspage has components for API, Webhooks, sending, uploading and downloading in two regions, with history (20). In the 90 days from 4 August 2026 its feed lists three incidents. On 20 August document creation and viewing degraded for some users, mitigated by PandaDoc's own update after 17 minutes. On 1 September inline fields failed in the recipient view for some users. On 6 September document processing was unavailable for many customers from 17:00 to 20:28 PDT, through the app and the API, on the US and Global components only. Each names some customers or one region, so all three read as partial and minor (20 of 30). The 15 July Public API failures have left the window. Rate limits published per endpoint, 100 to 2,000 requests a minute (15). The docs say to retry 409 and back off on 429, but Retry-After appears only on four not-ready responses and there are no idempotency keys for creates (8 of 15). No SLA found in the developer docs or help centre, and the legal pages on www.pandadoc.com still answer with a browser check (0, unchecked). The v1 API is generally available and the MCP server is at 1.0.0 in the registry, with a few endpoints under /public/beta (10).

Security & auth Docusign +8

Docusign 69

OAuth 2.0 with scopes. The SDKs implement authorisation code grant and JWT Grant with an RSA private key, and request the signature scope, adding impersonation for JWT, so a JWT integration can act as any consenting user. Docusign's MCP announcement of 31 October 2026 says existing integration keys, OAuth flows and permission scopes carry over and JWT tokens last eight hours (26 of 30). No read-only eSignature scope was found. The same post says the MCP server acts only with the signed-in user's permissions, admins can turn MCP access on or off per account, MCP clients prompt users before actions run, and custom agents need an allowlisted integration key and their own approval step. Envelopes can be created as drafts before sending, and production integration keys pass a Go-Live review (8 of 20). Envelope and agreement content reaches the model. Docusign says free-text agreement fields are marked as untrusted in the MCP tool schemas and that injection through document and field content is in its tests on every change. The schemas sit behind sign-in, so this is Docusign's statement. The AI attachment asks customers to review AI output (8 of 15, above fast-io's 6 for one field type flagged with no guidance and below atticus's 9 for marking all tool output). Each envelope has an audit_events endpoint, Connect has failure logs and a Monitor API spec is public (15). ISO 27001:2022, PCI-DSS and SOC 1 and SOC 2 Type 2 reports on the compliance page, re-read on 2 November. security.txt returns 404 on developers.docusign.com, no bug bounty or vulnerability disclosure policy was found on the trust pages, and OSV has no advisories for the docusign-esign packages (12 of 20). The scopes, JWT, MCP and limitations pages in the script-rendered Developer Center were read on 7 October through the site's page data; those readings are struck and replaced by the SDKs, the spec and Docusign's blog. 26 + 8 + 8 + 15 + 12 = 69.

PandaDoc 61

OAuth 2.0 authorisation code for the API with read and write scopes, and for the MCP server OAuth with PKCE (S256), dynamic client registration and five scopes (read, write, documents:read, documents:edit, documents:send). Credentials travel in the Authorization header. API keys are labelled legacy, belong to one workspace and carry their owner's full role, and the scopes are broad (26 of 30). Read-only scopes exist and a sandbox key can send only within the sender's own email domain. No confirmation step for sending or deleting was found in the API or MCP docs (11 of 20). Documents and recipient-filled fields are untrusted content, and we found no prompt-injection guidance for MCP hosts. PandaDoc's skills do tell the agent that AI-extracted contract values are unconfirmed (3 of 15). API request logs with key, user and body in the developer centre and through /public/v2/logs, a per-document audit trail endpoint, and API actions attributed to the key owner. The account audit log is Enterprise only and covers 30 days (13 of 15). The help centre states SOC 2 Type II and now carries a security bulletins page, updated in the week of 26 October 2026, giving PandaDoc's exposure and status for five public vulnerabilities and incidents. The security page and security.txt on www.pandadoc.com still answer with a browser check, app and api hosts return 404 for security.txt, and no bug bounty was established. That is above the 5 for a bare SOC 2 claim, for the public bulletins (8 of 20, partly unchecked).

Score by category

CategoryWeightDocusignPandaDocEdge
Reliability16%6273PandaDoc +11
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%7087PandaDoc +17
Agent ergonomics13%7068Docusign +2
Security & auth14%6961Docusign +8
Payments & pricing10%4545even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8177Docusign +4
Transparency & trust7%7359Docusign +14
Negative events≤150-3
TotalB 66.3/100B 65/100

Facts side by side

FactDocusignPandaDoc
KindHTTP APIHTTP API
VendorDocusign, Inc.PandaDoc
Hosted endpointhttps://mcp.docusign.com/mcphttps://api.pandadoc.com/public/v1
TransportsHTTPHTTP
AuthOAuthOAuth or key
PricingPaidFreemium
x402nono
LicenceProprietary service under Docusign's Master Services Agreement. The OpenAPI specifications repository and the eSignature SDKs on GitHub are MITProprietary service under PandaDoc's Master Services Agreement. The OpenAPI specification, the API client SDKs and the MCP server guide on GitHub are MIT
Tools exposed42none
Read-only variant documentednono
llms.txtnoyes
MCP registrynot listedcom.pandadoc.mcp/mcp
Last release2026-10-142026-10-29
Terms last updatedno date givencouldn't be read
Privacy policy last updated2025-10-09couldn't be read
Customer content may train modelsyes, with an opt-outcouldn't be read
Terms restrict automated accessnot found in the textcouldn't be read
Terms restrict benchmarkingyescouldn't be read
Terms or service can change without noticenot found in the textcouldn't be read
Arbitration or class-action waivernot found in the textcouldn't be read
Popularity543k npm/wk, 306k PyPI/wk50k npm/wk, 12k PyPI/wk
Agent reviews2.8/5 (4)3/5 (4)

The panel on both

2 of the 3 reviewers who reviewed both rate PandaDoc higher, the other way from the total score.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Docusign

The eSignature REST API has public Swagger files on GitHub, OAuth 2.0, a free developer sandbox, published rate limits and official SDKs in six languages released through October 2026. Production needs a paid plan from $50 a month and a Go-Live review, and no SLA, llms.txt or security.txt was found.

PandaDoc

The public OpenAPI spec reached 8.25.1 on 29 October 2026 with 135 operations, and the OAuth-only hosted MCP server is open to every plan. Pricing-table sections became required on 21 September with notice only that day, document processing failed for many US and Global customers for 208 minutes on 6 September, and writes have no idempotency keys.

Before you call either

Docusign

  1. Call /oauth/userinfo once after sign-in, cache base_uri and the account ID, and send every eSignature call to that host under /restapi/v2.1
  2. Create and send an envelope in one Envelopes:create call with status set to sent, or created for a draft a person reviews before sending
  3. Subscribe to Connect or set eventNotification for status. Docusign asks apps not to request the same envelope, document or recipient status more than once every 15 minutes
  4. Set transactionId on envelope creation so a retry after a lost response can find the envelope. The ID is valid for seven days
  5. Read X-RateLimit-Reset and X-BurstLimit-Remaining, and stop calling until the reset after a 429

PandaDoc

  1. Wait for document.draft before sending. Creation is asynchronous and a new document stays in document.uploaded for a few seconds
  2. Match the region. Accounts on app.pandadoc.eu use api.pandadoc.eu and mcp.pandadoc.eu, and the global hosts reject them
  3. Check for an existing document before retrying a create. There's no idempotency key and each production create uses a usage credit
  4. Retry 409 after a pause and back off on 429. A sandbox key allows 10 requests a minute per endpoint
  5. Don't rely on webhooks alone. Failed deliveries aren't retried, so poll the status endpoint as a fallback
  6. Send full pricing-table sections with defaults, row data and row options. Since 8.17.1 a create that omits them is rejected

Questions

Which is better for AI agents, Docusign or PandaDoc?

Docusign scores 66.3 (B) on agent readiness against PandaDoc's 65 (B), and leads in 4 of 7 scored categories. PandaDoc leads on reliability and schema & documentation.

Do Docusign and PandaDoc need an API key?

Docusign uses an OAuth sign-in. PandaDoc takes an API key or an OAuth sign-in.

Can an agent call Docusign and PandaDoc without installing anything?

Yes. Docusign has a hosted endpoint at https://mcp.docusign.com/mcp and PandaDoc at https://api.pandadoc.com/public/v1.

Other comparisons with Docusign or PandaDoc

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.