Head to head · Esign send · October 2026 research run
Docusign vs Dropbox Sign
Dropbox Sign scores 68.9 (B) on agent readiness against Docusign's 62.5 (B), and leads in 5 of 7 scored categories. Docusign leads on payments & pricing. 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
- Payments & pricing, 30 against 25
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
Good for An agent that sends a prepared PDF or a saved template for signature from one company account and tracks it to completion by webhook or polling, with the signed PDF and audit trail at the end.
Ahead on
- Reliability, 75 against 57
- Schema & documentation, 88 against 70
Watch for
No idempotency keys found in the docs or the spec, so a retried send can create a second signature request
Score by category
| Category | Weight this run | Docusign | Dropbox Sign | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 57 | 75 | Dropbox Sign +18 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 70 | 88 | Dropbox Sign +18 |
| Agent ergonomics | 13%16.2 | 70 | 72 | Dropbox Sign +2 |
| Security & auth | 14%17.5 | 64 | 65 | Dropbox Sign +1 |
| Payments & pricing | 10%12.5 | 30 | 25 | Docusign +5 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 81 | 85 | Dropbox Sign +4 |
| Transparency & trust | 7%8.8 | 72 | 68 | Docusign +4 |
| Negative events | ≤15 | 0 | 0 | |
| Total | 62.5 · B | 68.9 · B |
Facts side by side
| Fact | Docusign | Dropbox Sign |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Docusign, Inc. | Dropbox, Inc. |
| Hosted endpoint | https://mcp.docusign.com/mcp | https://api.hellosign.com/v3 |
| Transports | HTTP | HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Paid | Paid |
| 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 the Dropbox Sign terms of service. The OpenAPI spec repository is Apache 2.0 and the official SDKs are MIT |
| Tools exposed | 42 | none |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-09-30 | 2026-09-10 |
| Terms last updated | no date given | 2025-01-07 |
| Privacy policy last updated | 2025-10-09 | 2025-01-14 |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 543k npm/wk, 306k PyPI/wk | 22 stars, 150k npm/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.
Dropbox Sign
A public OpenAPI 3.0.3 spec, llms.txt, six official SDKs and a free test mode let an agent build the whole flow before paying. Production sends need a paid plan from $900 a year, the API key has full account access, and no idempotency keys were found in the reviewed documentation.
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
Dropbox Sign
- Send
test_mode=truewhile building. Test requests are free, watermarked and not legally binding, and are limited to 10 requests a minute - Don't blind-retry a send after a timeout. No idempotency key exists, so list requests by
metadataor title first to check whether it was created - Authenticate with HTTP Basic, the API key as username and an empty password. Keep the key out of URLs, although the docs show that form
- Answer every webhook with HTTP 200 and the body
Hello API Event Received, and verifyevent_hash. Ten consecutive failures clear the callback URL - Treat a 200 from cancel as queued only. Confirmation arrives later as a
signature_request_canceledevent
Questions
Which is better for AI agents, Docusign or Dropbox Sign?
Dropbox Sign scores 68.9 (B) on agent readiness against Docusign's 62.5 (B), and leads in 5 of 7 scored categories. Docusign leads on payments & pricing.
Do Docusign and Dropbox Sign need an API key?
Docusign uses an OAuth sign-in. Dropbox Sign takes an API key or an OAuth sign-in.
Can an agent call Docusign and Dropbox Sign without installing anything?
Yes. Docusign has a hosted endpoint at https://mcp.docusign.com/mcp and Dropbox Sign at https://api.hellosign.com/v3.
Other comparisons with Docusign or Dropbox Sign
Machine-readable
- This page as Markdown
/compare/docusign-vs-dropbox-sign.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/docusign.json·/api/v1/tools/dropbox-sign.json - From a terminal
anchor compare docusign dropbox-sign(the CLI) - Over MCP
compare_tools {"a": "docusign", "b": "dropbox-sign"}at/mcp, no key