Head to head · Esign send · October 2026 research run
Docusign vs PandaDoc
PandaDoc and Docusign score within a point of each other on agent readiness, 63.1 (B) and 62.5 (B). Docusign leads on transparency & trust. Both do esign send.
Which one, for what
Docusign B
Good 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
- Transparency & trust, 72 against 59
Watch for
health.docusign.com lists 34 incidents since 9 July 2026, including a two-hour NA4 disruption on 30 July and email notification failures from 25 to 30 September
PandaDoc B
Good 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
- Schema & documentation, 87 against 70
Watch for
Three incidents hit document creation, sending or the API between 15 July and 6 September 2026, the longest about 3.5 hours
Score by category
| Category | Weight this run | Docusign | PandaDoc | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 57 | 58 | PandaDoc +1 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 70 | 87 | PandaDoc +17 |
| Agent ergonomics | 13%16.2 | 70 | 68 | Docusign +2 |
| Security & auth | 14%17.5 | 64 | 61 | Docusign +3 |
| Payments & pricing | 10%12.5 | 30 | 30 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 81 | 77 | Docusign +4 |
| Transparency & trust | 7%8.8 | 72 | 59 | Docusign +13 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 62.5 · B | 63.1 · B |
Facts side by side
| Fact | Docusign | PandaDoc |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Docusign, Inc. | PandaDoc |
| Hosted endpoint | https://mcp.docusign.com/mcp | https://api.pandadoc.com/public/v1 |
| Transports | HTTP | HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | Proprietary service under Docusign's Master Services Agreement. The OpenAPI specifications repository and the eSignature SDKs on GitHub are MIT | Proprietary service under PandaDoc's Master Services Agreement. The OpenAPI specification, the API client SDKs and the MCP server guide on GitHub are MIT |
| Tools exposed | 42 | none |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | com.pandadoc.mcp/mcp |
| Last release | 2026-09-30 | 2026-10-02 |
| Terms last updated | no date given | couldn't be read |
| Privacy policy last updated | 2025-10-09 | couldn't be read |
| Customer content may train models | yes, with an opt-out | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | yes | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |
| Popularity | 543k npm/wk, 306k PyPI/wk | 50k npm/wk, 12k PyPI/wk |
Verdicts
Docusign
The eSignature REST API has public Swagger and OpenAPI files on GitHub, OAuth 2.0, a free developer sandbox and Connect webhooks, and the MCP server reached general availability on 30 September 2026. Production needs a paid plan from $50 a month and a Go-Live review, and the status site lists 34 incidents since 9 July 2026.
PandaDoc
The public OpenAPI spec lists 133 operations and reached version 8.21.0 on 2 October 2026, and the hosted MCP server, with OAuth and dynamic client registration, is open to every plan including Free. The status page records three incidents affecting document creation, sending or the API between 15 July and 6 September 2026, and writes have no idempotency keys.
Before you call either
Docusign
- Call /oauth/userinfo once after sign-in, cache
base_uriand the account ID, and send every eSignature call to that host under /restapi/v2.1 - Create and send an envelope in one Envelopes:create call with
statusset tosent. Docusign asks for five calls or fewer per envelope - Subscribe to Connect or set
eventNotificationfor status. Polling one envelope more than once every 15 minutes is flagged and can fail the Go-Live review - Set
transactionIdon envelope creation so a retry after a lost response can find the envelope. The ID is valid for seven days - Read
X-RateLimit-ResetandX-BurstLimit-Remaining, and stop calling until the reset after a 429
PandaDoc
- Wait for
document.draftbefore sending. Creation is asynchronous and a new document stays indocument.uploadedfor a few seconds - Match the region. Accounts on app.pandadoc.eu use api.pandadoc.eu and mcp.pandadoc.eu, and the global hosts reject them
- Check for an existing document before retrying a create. There's no idempotency key and each production create uses a usage credit
- Retry 409 after a pause and back off on 429. A sandbox key allows 10 requests a minute per endpoint
- Don't rely on webhooks alone. Failed deliveries aren't retried, so poll the status endpoint as a fallback
Questions
Which is better for AI agents, Docusign or PandaDoc?
PandaDoc and Docusign score within a point of each other on agent readiness, 63.1 (B) and 62.5 (B). Docusign leads on transparency & trust.
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
- This page as Markdown
/compare/docusign-vs-pandadoc.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/docusign.json·/api/v1/tools/pandadoc.json - From a terminal
anchor compare docusign pandadoc(the CLI) - Over MCP
compare_tools {"a": "docusign", "b": "pandadoc"}at/mcp, no key