Dropbox Sign vs Youtrust

Dropbox Sign 85

Python SDK 2.0.0 was tagged on 21 October 2026 (with 1.14.0 on 12 October and 1.14.1 on 20 October) and Node SDK 1.15.0 on 13 October, and the spec repository had commits through 27 October (30). Dated changelog entries on 19 August, 3 September and 6 October 2026, plus SDK 1.13.0 on 10 September and the October releases (20). A closed service with a public changelog, an API support address (apisupport@hellosign.com), a help centre and public GitHub issues, nine open on the spec repository per the 7 October check. We didn't test response times (11 of 15). Current official SDKs for Python, Node, PHP, Java, Ruby and .NET, with every generator moved to OpenAPI Generator 7.26.0 between 13 and 26 October (15). CI in the spec repository builds the spec and each SDK and fails on uncommitted generated code (9 of 10). Release dates are from the SDK repositories' tags. The 7 October PyPI reading used a JSON path pypi.org disallows and is struck.

Youtrust 61

Read as a closed service. The changelog's newest entries are dated 21 October 2026 (30). Ten entries between 13 and 21 October 2026 (20). A help centre, contact@youtrust.com in the OpenAPI contact block, a changelog RSS feed and a feedback form for the AI connector. No public issue tracker (8 of 15). No official SDK; the GitHub organisation holds no client library and the docs point to generators and Postman (0 of 15). The OpenAPI file is current with the October changes and the MCP setup page was updated on 7 September 2026 (3 of 10). 30 + 20 + 8 + 0 + 3 = 61.

Dropbox Sign 65

Read with the hosted lines and scored on the public REST API at api.hellosign.com, the surface an agent would call. status.hellosign.com on Statuspage lists 9 components in four groups (Core, Web, API, Integrations) with incident history (20). The history feed, read on 1 November 2026, has in the 90 days an unannounced emergency maintenance on 21 October 2026 that took the service offline "due to vulnerabilities in PHP" from 07:19 to 09:13 PDT (1 h 54 min), affecting every component including Send signature requests and API callbacks, read as one major. File upload problems on 31 August (54 min) were partial. The 21 August Salesforce integration fault doesn't touch the API and isn't counted, and the 22 September and 13 October windows were announced maintenance (10 of 30). Rate limits with numbers, 100 requests a minute standard, 25 on 17 higher-tier endpoints and 10 in test mode, although the header table describes the limit as hourly (15). The docs describe 429 with X-Ratelimit headers, tell clients to respect Retry-After and back off, and the error catalogue marks each error retryable or not. No idempotency keys or safe-retry guidance for sends were found (10 of 15). The terms supply the service as is and as available, and no SLA was found (0). The API is at v3 and generally available (10). The 7 October reading came from the Statuspage /api/v2/ path, which status.hellosign.com's robots.txt disallows. It is struck and replaced by history.atom.

Youtrust 85

Read with the hosted lines and scored on the Public API v3 at api.yousign.app, the surface both MCP servers call. yousign.statuspage.io on Atlassian Statuspage has an incident history and a feed (20). Between 5 August and 3 November 2026 the feed records HTTP 500 errors on the public API from 11:24 to 11:35 and 14:42 to 15:19 CEST on 7 October, caused by an infrastructure provider; about 45 minutes of delayed advanced and unavailable qualified signatures on 13 August; identity verification delays at a third-party provider on 1 September (most of a day), 2 September, 14 September and 16 October (33 minutes); 16 minutes of delayed seals on 16 October; email delays to Microsoft mailboxes on 4 September; and Orange network routing on 2 October. Several incidents, mostly at identity providers, and no outage of the core API over an hour (20). Rate limits are published per minute and hour for each environment (15). 429 answers Too many requests with x-ratelimit headers and a Ratelimit-Reset in seconds, the docs say to slow down and increase the delay, and there are no idempotency keys and no Retry-After (10 of 15). The API pricing page states 99 per cent and 99.9 per cent SLAs on the Plus and Pro plans (10). v3 is generally available (10). 20 + 20 + 15 + 10 + 10 + 10 = 85.

Dropbox Sign 25

Read with the hosted rubric. No x402, MPP or L402 (0). Plan prices are public, Essentials at $900 a year from 50 requests a month and Standard at $3,000 a year from 100, with larger volumes on a selector and Premium by quote. That is plan pricing, not a per-request price (10 of 20). Test mode is free on every endpoint from a free account, but its requests aren't legally binding, and the pages we read don't say whether signup needs a card (15 of 20). A person has to create the account and copy the key from the web app, and production needs a paid plan (0).

Youtrust 40

Read with the hosted rubric. No x402, MPP or L402 (0). API plan prices are public without login, Plus from €104 a month and Pro from €129 with €2 per extra signature (20). The sandbox trial lasts 40 days and needs no credit card per the API pricing page (20). A person signs up in a browser and an Admin creates the key there (0). 0 + 20 + 20 + 0 = 40.

Dropbox Sign 72

List calls take page_size from 1 to 100 (default 20), and files are fetched by separate calls as binary, data URI or URL, so status checks stay small. No field selection was found (15 of 25). Page-number pagination with totals in list_info, and a query search language over title, signer, sender, dates, completion state and metadata. The docs warn of a short indexing delay after creation (18 of 20). Errors carry error_name and error_msg, with 20 documented names, a remediation line each and a retryable flag, plus warnings in successful responses (20). No idempotency keys in the docs or spec, so a retried send can create a duplicate. Cancel returns 200 when queued and confirms by event. The retryable flags are the only safe-retry aid (4 of 20). A template send needs only template_ids and signers, test_mode is a single flag, and official SDKs cover six languages (15).

Youtrust 63

List calls take limit and filters, and a signature request's documents, signers and fields are fetched by their own calls, so responses stay moderate. No field selection (14 of 25). Cursor pagination with limit and after on 26 list operations, with status, workspace_id, created_at and date range filters (20). Errors carry a type an agent can branch on, a detail and invalid_params naming the field and reason, with guidance to retry only 500 and 503 (17 of 20). No idempotency keys. A request is a draft until activate, pause and cancel are explicit calls, and the MCP tools' annotations couldn't be read (6 of 20). A first send takes four calls (create, add document, add signer with fields, activate), identity and seal options add more, and there is no official SDK in any language (6 of 15). 14 + 20 + 17 + 6 + 6 = 63.