{ "data": { "a": { "slug": "docusign", "name": "Docusign", "vendor": "Docusign, Inc.", "vendorUrl": "https://www.docusign.com", "kind": "http-api", "category": "e-signatures", "summary": "Docusign is an e-signature and agreement management service. Its eSignature REST API creates envelopes from documents or templates, sends them to signers, embeds signing in an app and reports status. A hosted MCP server exposes a subset as tools.", "url": "https://www.anchorterminal.com/tools/docusign", "markdownUrl": "https://www.anchorterminal.com/tools/docusign.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/docusign.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/docusign.json", "repo": "https://github.com/docusign/OpenAPI-Specifications", "license": "Proprietary service under Docusign's Master Services Agreement. The OpenAPI specifications repository and the eSignature SDKs on GitHub are MIT", "transports": [ "http" ], "remoteUrl": "https://mcp.docusign.com/mcp", "packages": [ { "registry": "npm", "name": "docusign-esign" }, { "registry": "pypi", "name": "docusign-esign" } ], "auth": "oauth", "authNotes": "OAuth 2.0 access tokens only, sent as a Bearer header. A developer creates an integration key in a free developer account and chooses authorisation code grant (with a secret or PKCE), JWT Grant for a service that impersonates a consenting user, or Implicit Grant. Moving to production means a Go-Live review of the key's API activity, a paid account and an administrator. Public integrations must join the partner programme. Since 30 September 2026, a production integration key used with the MCP server also needs Docusign's approval through a form.", "pricing": "paid", "pricingNotes": "Developer API plans start at $50 a month billed annually (Starter, from 40 envelopes a month), then $300 (Intermediate) and $480 (Advanced), with larger plans through sales. A free developer account with no time limit lets an agent build and test in the demo environment without a contract, but envelopes sent there aren't legally binding. Workflow Builder and Agreement Manager need an IAM subscription (checked 2026-10-07).", "priceSummary": "$50 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs, the spec files or the pricing page (checked 2026-10-07).", "endpoints": [] }, "toolCount": 42, "popularity": { "githubStars": null, "npmWeekly": 542682, "pypiWeekly": 305902, "asOf": "2026-10-07" }, "docsUrl": "https://developers.docusign.com", "openapi": "https://raw.githubusercontent.com/docusign/OpenAPI-Specifications/master/esignature.rest.swagger-v2.1.json", "capabilities": [ "esign.send", "esign.templates", "esign.embed", "esign.status", "contracts.generate" ], "tags": [ "hosted", "paid", "sandbox", "oauth", "mcp", "openapi", "webhooks", "node", "python", "java", "csharp", "php", "ruby", "status-page", "soc2", "iso27001" ], "lastRelease": "2026-09-30", "graded": true, "anchor": { "graded": true, "score": 62.5, "grade": "B", "agentReady": false, "rank": 301, "ranked": true, "rankOf": 629, "categoryRank": 5, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 70, "maintenance": 81, "payments": 30, "reliability": 57, "schema": 70, "security": 64, "transparency": 72 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-07" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "Public Spec files under MIT on GitHub for eSignature v2.1 (213 paths, 414 operations) and ten other APIs", "Free developer account with no time limit, on a separate demo environment (demo.docusign.net, mcp-d.docusign.com)", "Rate limits published with numbers (3,000 calls an hour per account, 500 per 30 seconds in production) and returned in response headers", "Each envelope has an audit_events endpoint, and Connect webhooks support HMAC signatures, OAuth and mutual TLS", "Sub-processor list updated 18 September 2026 with an RSS feed, and 30 days' notice of new sub-processors in the data protection attachment" ], "weaknesses": [ "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", "Production access needs a paid account, an admin and a Go-Live review, and MCP integration keys need Docusign's approval since 30 September 2026", "The eSignature spec is Swagger 2.0 with no enums, no required lists and no security definitions. Valid values sit in prose", "The `signature` scope covers most of the eSignature API, and MCP admins can only switch access on or off, with no read or write tool control", "No llms.txt, no security.txt, and no bug bounty, written deprecation policy or SLA found in the pages reviewed" ], "agentNotes": [ "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", "Create and send an envelope in one Envelopes:create call with `status` set to `sent`. Docusign asks for five calls or fewer per envelope", "Subscribe to Connect or set `eventNotification` for status. Polling one envelope more than once every 15 minutes is flagged and can fail the Go-Live review", "Set `transactionId` on envelope creation so a retry after a lost response can find the envelope. The ID is valid for seven days", "Read `X-RateLimit-Reset` and `X-BurstLimit-Remaining`, and stop calling until the reset after a 429" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 62.5 } ], "editorialScores": { "ergonomics": 70, "maintenance": 81, "payments": 30, "reliability": 57, "schema": 70, "security": 64, "transparency": 59 }, "provenanceScore": 85 }, "connect": { "install": "npm install docusign-esign -save" }, "letme": { "capability": "https://letme.dev/esign.send", "tool": "https://letme.dev/docusign" }, "area": "business", "unitPrices": [ { "item": "Starter plan", "unit": "month", "usd": 50, "note": "Starting amount of 40 envelopes a month, $600 billed annually" }, { "item": "Intermediate plan", "unit": "month", "usd": 300, "note": "Starting amount of 100 envelopes a month, $3,600 billed annually" }, { "item": "Advanced plan", "unit": "month", "usd": 480, "note": "Adds PowerForms, Bulk Send, signer attachments and Connect, $5,760 billed annually" } ], "provenance": { "legalEntity": "Docusign, Inc.", "domain": "docusign.com", "domainRegistered": "1999-06-14", "endpointOnVendorDomain": true, "terms": "https://www.docusign.com/legal/terms-and-conditions/msa", "privacy": "https://www.docusign.com/privacy", "statusPage": "https://health.docusign.com", "changelog": "https://developers.docusign.com/changelog/", "securityTxt": "none", "checked": "2026-10-07", "notes": [ "The Master Services Agreement names Docusign, Inc., a Delaware corporation, and is dated 14 November 2022. The privacy notice (effective 9 October 2025) gives 221 Main Street, Suite 800, San Francisco, CA 94105.", "The eSignature API answers at docusign.net hosts, auth at account.docusign.com and the MCP server at mcp.docusign.com. We did not look up the registration of docusign.net.", "www.docusign.com/.well-known/security.txt and developers.docusign.com/.well-known/security.txt return 404.", "status.docusign.com redirects to health.docusign.com, which loads its incidents from a JSON feed on the same host.", "RDAP for docusign.com gives a registration date of 1999-06-14 and MarkMonitor Inc. as registrar." ], "score": 85 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/docusign.json", "live": { "slug": "docusign", "probe": { "target": "https://mcp.docusign.com/mcp", "method": "get", "lastAt": "2026-10-08T18:20:28.95148249Z", "lastOk": true, "lastStatus": 403, "lastMs": 78, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 85, "p95ms24h": 276, "samples24h": 33, "samples30d": 33, "days": [ { "date": "2026-10-08", "probes": 33, "ok": 33 } ] }, "vendorStatus": { "page": "https://health.docusign.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-10-08T17:50:34.016637635Z" }, "versions": [ { "registry": "github", "name": "docusign/OpenAPI-Specifications", "version": "20.1.00", "released": "2020-04-17", "seenAt": "2026-10-08T16:09:01.313876796Z" }, { "registry": "npm", "name": "docusign-esign", "version": "10.0.0", "seenAt": "2026-10-08T16:08:57.83420854Z" }, { "registry": "pypi", "name": "docusign-esign", "version": "6.1.0", "released": "2026-03-13", "seenAt": "2026-10-08T16:09:01.102662485Z" } ], "githubStars": 24, "npmWeekly": 542682, "pypiWeekly": 298433, "securityTxt": { "url": "https://docusign.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:38:29.983479591Z" }, "pages": [ { "url": "https://developers.docusign.com/changelog/", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:17:32.846205768Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "0fbf96791151" } ], "updatedAt": "2026-10-08T18:20:28.95148249Z" } }, "answer": "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 \u0026 pricing.", "b": { "slug": "dropbox-sign", "name": "Dropbox Sign", "vendor": "Dropbox, Inc.", "vendorUrl": "https://sign.dropbox.com", "kind": "http-api", "category": "e-signatures", "summary": "Dropbox Sign (formerly HelloSign) is Dropbox's e-signature service. Its REST API sends documents or templates for signature, embeds signing in an iframe, reports status by webhook and returns signed PDFs with an audit trail.", "url": "https://www.anchorterminal.com/tools/dropbox-sign", "markdownUrl": "https://www.anchorterminal.com/tools/dropbox-sign.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/dropbox-sign.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/dropbox-sign.json", "repo": "https://github.com/hellosign/hellosign-openapi", "license": "Proprietary service under the Dropbox Sign terms of service. The OpenAPI spec repository is Apache 2.0 and the official SDKs are MIT", "transports": [ "http" ], "remoteUrl": "https://api.hellosign.com/v3", "packages": [ { "registry": "npm", "name": "@dropbox/sign" }, { "registry": "pypi", "name": "dropbox-sign" } ], "auth": "mixed", "authNotes": "A self-serve API key from the account's API settings page, sent as the HTTP Basic username with an empty password. Each account can hold up to four keys for rotation, and every key has full access to the account. OAuth 2.0 access tokens (Bearer) act on behalf of other users with seven scopes across two billing models, and OAuth apps need approval by Dropbox Sign support before production. Embedded apps can be self-published in the web app.", "pricing": "paid", "pricingNotes": "Production signature requests need a paid API plan, and the API answers 402 without one. Essentials is $900 a year ($75 a month) from 50 requests a month, Standard $3,000 a year ($250 a month) from 100, and Premium is quoted by sales. Test mode is free on every endpoint from a free account, so an agent can build and test without a contract (checked 2026-10-07).", "priceSummary": "Paid", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the developer docs, the OpenAPI spec or the pricing page (checked 2026-10-07).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 22, "npmWeekly": 149738, "pypiWeekly": null, "asOf": "2026-10-07" }, "docsUrl": "https://developers.hellosign.com", "llmsTxt": "https://developers.hellosign.com/llms.txt", "openapi": "https://raw.githubusercontent.com/hellosign/hellosign-openapi/main/openapi.yaml", "capabilities": [ "esign.send", "esign.templates", "esign.embed", "esign.status" ], "tags": [ "hosted", "closed-source", "api-key", "oauth", "openapi", "llms-txt", "webhooks", "sandbox", "python", "typescript", "java", "php", "ruby", "dotnet", "status-page", "bug-bounty", "soc2" ], "lastRelease": "2026-09-10", "graded": true, "anchor": { "graded": true, "score": 68.9, "grade": "B", "agentReady": false, "rank": 161, "ranked": true, "rankOf": 629, "categoryRank": 1, "methodology": "0.4", "run": "2026-10-01", "scores": { "ergonomics": 72, "maintenance": 85, "payments": 25, "reliability": 75, "schema": 88, "security": 65, "transparency": 68 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-07" }, "negative": 0, "verdict": "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.", "bestFor": "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.", "strengths": [ "Public OpenAPI 3.0.3 spec with 74 operations, plus llms.txt and a Markdown copy of every docs page", "Free test mode works on every endpoint from a free account, with watermarked, non-binding requests that don't count against quota", "Error catalogue of 20 HTTP error names with cause, remediation and a retryable flag, also embedded in the spec as `x-error-codes`", "Rate limits published with numbers (100 a minute standard, 25 on higher-tier endpoints, 10 in test mode) and returned in response headers", "Official SDKs in six languages at version 1.13.0, released 10 September 2026, with semantic versioning" ], "weaknesses": [ "No idempotency keys found in the docs or the spec, so a retried send can create a second signature request", "An API key grants full access to the account, with no scoped or read-only keys. Scopes exist only on OAuth tokens", "OAuth apps need manual approval by Dropbox Sign support before production use", "The terms supply the service as is, and no SLA was found. A major outage on 2 January 2026 lasted 3 hours 12 minutes", "Embedded signing and bulk send need the Standard plan ($3,000 a year), and embedded templates need Premium, priced by quote" ], "agentNotes": [ "Send `test_mode=true` while 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 `metadata` or 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 verify `event_hash`. Ten consecutive failures clear the callback URL", "Treat a 200 from cancel as queued only. Confirmation arrives later as a `signature_request_canceled` event" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.4", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 68.9 } ], "editorialScores": { "ergonomics": 72, "maintenance": 85, "payments": 25, "reliability": 75, "schema": 88, "security": 65, "transparency": 51 }, "provenanceScore": 85 }, "connect": { "install": "npm install @dropbox/sign", "http": "curl \"https://api.hellosign.com/v3/template/list\" \\\n -u \"${API_KEY}:\"" }, "letme": { "capability": "https://letme.dev/esign.send", "tool": "https://letme.dev/dropbox-sign" }, "area": "business", "provenance": { "legalEntity": "Dropbox, Inc.", "domain": "hellosign.com", "domainRegistered": "2004-03-05", "endpointOnVendorDomain": true, "terms": "https://sign.dropbox.com/about/terms", "privacy": "https://sign.dropbox.com/about/privacy", "statusPage": "https://status.hellosign.com", "changelog": "https://developers.hellosign.com/changelog", "securityTxt": "none", "checked": "2026-10-07", "notes": [ "The Dropbox Sign terms (effective 7 January 2025) put the agreement with Dropbox, Inc. for customers in the United States, Canada and Mexico and with Dropbox International Unlimited Company elsewhere.", "The API host is api.hellosign.com and the docs are at developers.hellosign.com. The marketing site is sign.dropbox.com. RDAP gives 2004-03-05 for hellosign.com and 1995-06-28 for dropbox.com.", "sign.dropbox.com/.well-known/security.txt and api.hellosign.com/.well-known/security.txt return 404. www.dropbox.com/.well-known/security.txt serves a plain-text file that names the Intigriti bug bounty and disclosure programmes without the standard Contact and Expires fields.", "The privacy policy is dated 14 January 2025. The data processing agreement at assets.dropbox.com is dated 25 October 2021.", "The sub-processor list at www.dropbox.com/privacy/subprocessor/sign returned only its title to our reader." ], "score": 85 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/dropbox-sign.json", "live": { "slug": "dropbox-sign", "probe": { "target": "https://api.hellosign.com/v3", "method": "get", "lastAt": "2026-10-08T18:20:29.156505354Z", "lastOk": true, "lastStatus": 404, "lastMs": 132, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 142, "p95ms24h": 306, "samples24h": 33, "samples30d": 33, "days": [ { "date": "2026-10-08", "probes": 33, "ok": 33 } ] }, "vendorStatus": { "page": "https://status.hellosign.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-10-08T18:21:56.962032231Z" }, "versions": [ { "registry": "npm", "name": "@dropbox/sign", "version": "1.13.0", "seenAt": "2026-10-08T16:09:21.702754102Z" }, { "registry": "pypi", "name": "dropbox-sign", "version": "1.13.0", "released": "2026-09-10", "seenAt": "2026-10-08T16:09:25.156865046Z" } ], "githubStars": 22, "npmWeekly": 149738, "pypiWeekly": 73874, "securityTxt": { "url": "https://hellosign.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-08T15:39:08.009752876Z" }, "pages": [ { "url": "https://developers.hellosign.com/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-10-08T18:17:43.499814076Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "df5ec179b075" }, { "url": "https://sign.dropbox.com/about/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-08T18:24:17.794548551Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "30f2bccc1007" }, { "url": "https://sign.dropbox.com/about/terms", "kind": "terms", "status": 200, "checkedAt": "2026-10-08T18:24:19.844597175Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "daf78169f086" } ], "updatedAt": "2026-10-08T18:24:19.844597175Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Docusign, Inc.", "b": "Dropbox, Inc.", "name": "Vendor" }, { "a": "https://mcp.docusign.com/mcp", "b": "https://api.hellosign.com/v3", "name": "Hosted endpoint" }, { "a": "HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth", "b": "OAuth or key", "name": "Auth" }, { "a": "Paid", "b": "Paid", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under Docusign's Master Services Agreement. The OpenAPI specifications repository and the eSignature SDKs on GitHub are MIT", "b": "Proprietary service under the Dropbox Sign terms of service. The OpenAPI spec repository is Apache 2.0 and the official SDKs are MIT", "name": "Licence" }, { "a": "42", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-09-30", "b": "2026-09-10", "name": "Last release" }, { "a": "no date given", "b": "2025-01-07", "name": "Terms last updated" }, { "a": "2025-10-09", "b": "2025-01-14", "name": "Privacy policy last updated" }, { "a": "yes, with an opt-out", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "yes", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "543k npm/wk, 306k PyPI/wk", "b": "22 stars, 150k npm/wk", "name": "Popularity" } ], "faq": [ { "answer": "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 \u0026 pricing.", "question": "Which is better for AI agents, Docusign or Dropbox Sign?" }, { "answer": "Docusign uses an OAuth sign-in. Dropbox Sign takes an API key or an OAuth sign-in.", "question": "Do Docusign and Dropbox Sign need an API key?" }, { "answer": "Yes. Docusign has a hosted endpoint at https://mcp.docusign.com/mcp and Dropbox Sign at https://api.hellosign.com/v3.", "question": "Can an agent call Docusign and Dropbox Sign without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 30 against 25" ], "also": null, "goodFor": "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.", "slug": "docusign", "watchFor": "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" }, { "aheadOn": [ "Reliability, 75 against 57", "Schema \u0026 documentation, 88 against 70" ], "also": null, "goodFor": "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.", "slug": "dropbox-sign", "watchFor": "No idempotency keys found in the docs or the spec, so a retried send can create a second signature request" } ], "job": { "capability": "esign.send", "name": "Esign send" }, "others": [ { "json": "https://www.anchorterminal.com/compare/documenso-vs-docusign.json", "title": "Documenso vs Docusign", "url": "https://www.anchorterminal.com/compare/documenso-vs-docusign" }, { "json": "https://www.anchorterminal.com/compare/documenso-vs-dropbox-sign.json", "title": "Documenso vs Dropbox Sign", "url": "https://www.anchorterminal.com/compare/documenso-vs-dropbox-sign" }, { "json": "https://www.anchorterminal.com/compare/docusign-vs-pandadoc.json", "title": "Docusign vs PandaDoc", "url": "https://www.anchorterminal.com/compare/docusign-vs-pandadoc" }, { "json": "https://www.anchorterminal.com/compare/docusign-vs-signnow.json", "title": "Docusign vs airSlate SignNow", "url": "https://www.anchorterminal.com/compare/docusign-vs-signnow" }, { "json": "https://www.anchorterminal.com/compare/dropbox-sign-vs-pandadoc.json", "title": "Dropbox Sign vs PandaDoc", "url": "https://www.anchorterminal.com/compare/dropbox-sign-vs-pandadoc" }, { "json": "https://www.anchorterminal.com/compare/dropbox-sign-vs-signnow.json", "title": "Dropbox Sign vs airSlate SignNow", "url": "https://www.anchorterminal.com/compare/dropbox-sign-vs-signnow" } ], "scores": [ { "by": 18, "docusign": 57, "dropbox-sign": 75, "edge": "dropbox-sign", "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 18, "docusign": 70, "dropbox-sign": 88, "edge": "dropbox-sign", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 2, "docusign": 70, "dropbox-sign": 72, "edge": "dropbox-sign", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "by": 1, "docusign": 64, "dropbox-sign": 65, "edge": "dropbox-sign", "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "by": 5, "docusign": 30, "dropbox-sign": 25, "edge": "docusign", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 4, "docusign": 81, "dropbox-sign": 85, "edge": "dropbox-sign", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 4, "docusign": 72, "dropbox-sign": 68, "edge": "docusign", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "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 \u0026 pricing. Both do esign send.", "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." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/docusign-vs-dropbox-sign", "json": "https://www.anchorterminal.com/compare/docusign-vs-dropbox-sign.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/docusign-vs-dropbox-sign.md", "slim": "https://www.anchorterminal.com/compare/docusign-vs-dropbox-sign.min.md" }, "markdown": "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 \u0026 pricing. Both do esign send.\n\n- Docusign: grade B, 62.5/100, rank #301 of 629. Markdown https://www.anchorterminal.com/tools/docusign.md · JSON https://www.anchorterminal.com/api/v1/tools/docusign.json\n- Dropbox Sign: grade B, 68.9/100, rank #161 of 629. Markdown https://www.anchorterminal.com/tools/dropbox-sign.md · JSON https://www.anchorterminal.com/api/v1/tools/dropbox-sign.json\n\n## Which one, for what\n\n### Docusign (B)\n\nGood 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.\n\nAhead on:\n- Payments \u0026 pricing, 30 against 25\n\nWatch 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\n\n### Dropbox Sign (B)\n\nGood 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.\n\nAhead on:\n- Reliability, 75 against 57\n- Schema \u0026 documentation, 88 against 70\n\nWatch for: No idempotency keys found in the docs or the spec, so a retried send can create a second signature request\n\n\n## Score by category\n\n| Category | Weight | Docusign | Dropbox Sign | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 57 | 75 | Dropbox Sign +18 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 70 | 88 | Dropbox Sign +18 |\n| Agent ergonomics | 13% (16.2 this run) | 70 | 72 | Dropbox Sign +2 |\n| Security \u0026 auth | 14% (17.5 this run) | 64 | 65 | Dropbox Sign +1 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 25 | Docusign +5 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 81 | 85 | Dropbox Sign +4 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 72 | 68 | Docusign +4 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **62.5 · B** | **68.9 · B** | |\n\n## Facts side by side\n\n| Fact | Docusign | Dropbox Sign |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Docusign, Inc. | Dropbox, Inc. |\n| Hosted endpoint | `https://mcp.docusign.com/mcp` | `https://api.hellosign.com/v3` |\n| Transports | HTTP | HTTP |\n| Auth | OAuth | OAuth or key |\n| Pricing | Paid | Paid |\n| x402 | no | no |\n| 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 |\n| Tools exposed | 42 | none |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | 2026-09-30 | 2026-09-10 |\n| Terms last updated | no date given | 2025-01-07 |\n| Privacy policy last updated | 2025-10-09 | 2025-01-14 |\n| Customer content may train models | yes, with an opt-out | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | yes | yes |\n| Terms or service can change without notice | not found in the text | yes |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Popularity | 543k npm/wk, 306k PyPI/wk | 22 stars, 150k npm/wk |\n\n## Verdicts\n\n**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.\n\n**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.\n\n## Before you call either\n\n### Docusign\n\n1. 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\n2. Create and send an envelope in one Envelopes:create call with `status` set to `sent`. Docusign asks for five calls or fewer per envelope\n3. Subscribe to Connect or set `eventNotification` for status. Polling one envelope more than once every 15 minutes is flagged and can fail the Go-Live review\n4. Set `transactionId` on envelope creation so a retry after a lost response can find the envelope. The ID is valid for seven days\n5. Read `X-RateLimit-Reset` and `X-BurstLimit-Remaining`, and stop calling until the reset after a 429\n\n### Dropbox Sign\n\n1. Send `test_mode=true` while building. Test requests are free, watermarked and not legally binding, and are limited to 10 requests a minute\n2. Don't blind-retry a send after a timeout. No idempotency key exists, so list requests by `metadata` or title first to check whether it was created\n3. 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\n4. Answer every webhook with HTTP 200 and the body `Hello API Event Received`, and verify `event_hash`. Ten consecutive failures clear the callback URL\n5. Treat a 200 from cancel as queued only. Confirmation arrives later as a `signature_request_canceled` event\n\n## Questions\n\n### Which is better for AI agents, Docusign or Dropbox Sign?\n\nDropbox 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 \u0026 pricing.\n\n### Do Docusign and Dropbox Sign need an API key?\n\nDocusign uses an OAuth sign-in. Dropbox Sign takes an API key or an OAuth sign-in.\n\n### Can an agent call Docusign and Dropbox Sign without installing anything?\n\nYes. Docusign has a hosted endpoint at https://mcp.docusign.com/mcp and Dropbox Sign at https://api.hellosign.com/v3.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/docusign-vs-dropbox-sign.json, and with the fewest tokens: https://www.anchorterminal.com/compare/docusign-vs-dropbox-sign.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"docusign\", \"b\": \"dropbox-sign\"}`. From a terminal: `anchor compare docusign dropbox-sign`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/docusign.json and https://www.anchorterminal.com/api/v1/tools/dropbox-sign.json\n\n## Other comparisons with Docusign or Dropbox Sign\n\n- [Documenso vs Docusign](https://www.anchorterminal.com/compare/documenso-vs-docusign.md)\n- [Documenso vs Dropbox Sign](https://www.anchorterminal.com/compare/documenso-vs-dropbox-sign.md)\n- [Docusign vs PandaDoc](https://www.anchorterminal.com/compare/docusign-vs-pandadoc.md)\n- [Docusign vs airSlate SignNow](https://www.anchorterminal.com/compare/docusign-vs-signnow.md)\n- [Dropbox Sign vs PandaDoc](https://www.anchorterminal.com/compare/dropbox-sign-vs-pandadoc.md)\n- [Dropbox Sign vs airSlate SignNow](https://www.anchorterminal.com/compare/dropbox-sign-vs-signnow.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.4", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Docusign vs Dropbox Sign", "url": "" } ], "description": "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 \u0026 pricing. Both do esign send. Category scores, facts, verdicts and agent notes side by side.", "facts": [ "Docusign B 62.5", "Dropbox Sign B 68.9", "scores" ], "h1": "Docusign vs Dropbox Sign", "image": "https://www.anchorterminal.com/assets/og/compare-docusign-vs-dropbox-sign.png", "path": "/compare/docusign-vs-dropbox-sign", "published": "2026-10-01", "section": "tools", "title": "Docusign vs Dropbox Sign for AI agents, B 62.5 vs B 68.9", "toc": null, "updated": "2026-10-08", "url": "https://www.anchorterminal.com/compare/docusign-vs-dropbox-sign" }, "tokens": { "markdown": 2000, "slim": 680 }, "version": 1 }