Docusign vs Beglaubigt.de

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to Beglaubigt.de
   Docusign~partialprobed5/10

   Docusign has no llms.txt (confirmed 404 probe) but does provide agent-oriented documentation such as the Claude MCP connector guide, an official MCP server, and machine-readable OpenAPI specs explicitly described as enabling 'computers to discover and understand the capabilities of the service.' This covers part of the story but lacks the specific llms.txt convention many AI-native tools expect. missing for 10: llms.txt file, dedicated agent-facing doc index, independent confirmation that agents can consume these docs successfully.

   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.docusign.com/llms.txt”
   • [probe] “official MCP server documented at https://developers.docusign.com/platform/mcp-server/”
   • [claimed-docs] “The Docusign Connector in Anthropic Claude via MCP server provides a supported way to connect Claude to Docusign IAM capabilities.”
   • [claimed-docs] “Retrieve agreement context and metadata... Query agreement status and key dates... Trigger workflow actions through IAM tools”
   • [github] “allows both humans and computers to discover and understand the capabilities of the service”

   proof ↗⚑ flag

   Beglaubigt.de✓fullprobed8/10

   Beglaubigt.de has a live llms.txt confirmed via direct probe (HTTP 200) plus an llms-full.txt with detailed API/event docs, and a separate marketing-domain llms.txt listing product capabilities, giving agents a clear entry point into agent-oriented documentation. Missing for 10: no OpenAPI/machine-readable schema (probe shows 404s) and no independent third-party confirmation of agent usage.

   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.beglaubigt.de/llms.txt # Beglaubigt.de API - [Introduction to Beglaubigt.de API](/): Welcome to th…”
   • [claimed-docs] “Digital notarization of legal documents (under 48h)”
   • [claimed-docs] “The `appointment.completed` event is automatically triggered when the notary appointment date has passed.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.beglaubigt.de/openapi.json, https://docs.beglaubigt.de/swagger.json, https://docs.begla…”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round to Docusign
   Docusign~partialcommunity6/10

   Docusign exposes a REST API, official SDKs (e.g., Node.js client) and OpenAPI specs that let developers script sending/signing/approving documents programmatically, and the Gemini CLI + Docusign MCP integration explicitly supports automating agreement processes 'from your terminal.' However, there is no explicit CI/CD documentation, headless-mode guide, or automated pipeline example, and community feedback notes real integration friction (mixed embedded-API experiences). Missing for 10: dedicated CI/headless deployment guide, service-account/automation-focused docs, and independent verification of running the API in automated pipelines without a UI.

   • [claimed-docs] “Request Signatures & Automate Forms | REST API | Docusign”
   • [claimed-docs] “Send, sign, and approve documents using this client.”
   • [claimed-docs] “The Official Docusign Node.js Client Library used to interact with the eSign REST API. Send, sign, and approve documents using this client.”
   • [github] “We use OpenAPI/Swagger files to build many of our developer tools including our client SDKs”
   • [github] “allows both humans and computers to discover and understand the capabilities of the service”
   • [claimed-docs] “Query agreement data and automate agreement processes from your terminal by pairing Gemini CLI with Docusign MCP.”
   • [community] “We did exactly this embedded signing integration and it was fairly seamless - built a POC in Postman in about an hour and a Jr dev built a p…”
   • [community] “We use the v2 REST API creating embedded envelope signing URLs without issues. Documentation is fantastic in its thoroughness - opposite exp…”

   proof ↗⚑ flag

   Beglaubigt.de~partialprobed5/10

   Beglaubigt.de exposes a REST API (incorporation, notarization, translation, tax/trade registration) with webhooks and HMAC-signed events, which is inherently callable headlessly from scripts or CI pipelines. However, there is no explicit CI/automation guidance, SDK, or CLI, and an OpenAPI spec probe returned 404s, so headless integration must be inferred rather than confirmed. Missing for 10: explicit CI/automation documentation, official SDK/CLI, and a machine-readable OpenAPI spec.

   • [claimed-docs] “businesses can submit documents, manage signers, and automate notarization workflows, or incorporate companies in Germany”
   • [claimed-docs] “This endpoint creates an incorporation request for a company in Germany such as a GmbH or UG, including company details, shareholders, and d…”
   • [claimed-docs] “This endpoint creates a notarization request for a document”
   • [claimed-docs] “Real-time updates: Get instant notifications when notarization events are completed.”
   • [claimed-docs] “This signature is generated using the HMAC-SHA256 algorithm and a secret key that is shared exclusively between Beglaubigt and your system.”
   • [claimed-docs] “The `appointment.completed` event is automatically triggered when the notary appointment date has passed.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.beglaubigt.de/openapi.json, https://docs.beglaubigt.de/swagger.json, https://docs.begla…”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round to Docusign
   Docusign✓fullprobed8/10

   Docusign documents an official MCP server (Docusign Connector via Anthropic Claude and Gemini CLI) with a dedicated developer platform page and guide, exposing IAM tools like retrieving agreement context/metadata and triggering workflow actions. Missing for 10: independent/hands-on verification of the MCP server's reliability and broader third-party adoption beyond vendor blog examples.

   • [claimed-docs] “The Docusign Connector in Anthropic Claude via MCP server provides a supported way to connect Claude to Docusign IAM capabilities.”
   • [claimed-docs] “Retrieve agreement context and metadata... Query agreement status and key dates... Trigger workflow actions through IAM tools”
   • [claimed-docs] “Query agreement data and automate agreement processes from your terminal by pairing Gemini CLI with Docusign MCP.”
   • [claimed-docs] “Build agreement workflows: Docusign MCP & Claude”
   • [probe] “official MCP server documented at https://developers.docusign.com/platform/mcp-server/”

   proof ↗⚑ flag

   Beglaubigt.de—none0/10

   Beglaubigt.de offers a REST API and webhooks for notarization/incorporation workflows but no evidence of an official MCP server; probes for OpenAPI/MCP artifacts returned 404s. Missing for 10: any MCP server documentation, endpoint, or SDK enabling agent connection.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.beglaubigt.de/openapi.json, https://docs.beglaubigt.de/swagger.json, https://docs.begla…”
   • [claimed-docs] “businesses can submit documents, manage signers, and automate notarization workflows, or incorporate companies in Germany”

   proof ↗⚑ flag

4. ai-native userDrive the product through a documented public API

   weight 3 · round drawn
   Docusign✓fullprobed8/10

   Docusign publishes a well-documented public REST API (eSign REST API docs, Developer Center, OpenAPI/Swagger specs used to generate SDKs like the Node.js client), with community confirmation that thorough API-driven integrations (e.g., embedded signing) work well in production. This directly satisfies programmatic/API-driven use, though one community report describes a security workaround requiring a legacy API version, and there's no first-party llms.txt or discoverable openapi.json at the expected probe URLs. Missing for 10: a clean machine-readable OpenAPI spec at a standard endpoint (probe returned 404s) and stronger independent corroboration beyond one HN thread.

   • [claimed-docs] “Request Signatures & Automate Forms | REST API | Docusign”
   • [claimed-docs] “Docusign Developer Center | eSignature APIs & Resources | Docusign”
   • [github] “We use OpenAPI/Swagger files to build many of our developer tools including our client SDKs”
   • [github] “allows both humans and computers to discover and understand the capabilities of the service”
   • [github] “We use OpenAPI/Swagger files to build many of our developer tools including our client SDKs using `swagger-codegen`.”
   • [claimed-docs] “Send, sign, and approve documents using this client.”
   • [claimed-docs] “The Official Docusign Node.js Client Library used to interact with the eSign REST API. Send, sign, and approve documents using this client.”
   • [community] “We did exactly this embedded signing integration and it was fairly seamless - built a POC in Postman in about an hour and a Jr dev built a p…”
   • [community] “We use the v2 REST API creating embedded envelope signing URLs without issues. Documentation is fantastic in its thoroughness - opposite exp…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.docusign.com/openapi.json, https://developers.docusign.com/swagger.json, https://…”

   proof ↗⚑ flag

   Beglaubigt.de✓fullprobed8/10

   Beglaubigt.de publishes a documented public API with clear endpoints for incorporation, notarization, translation, tax and trade registration, webhooks, and signature verification, confirmed live via llms.txt probe (HTTP 200). Missing for 10: a discoverable OpenAPI/Swagger spec (all standard paths 404) and independent third-party corroboration of API usage.

   • [claimed-docs] “businesses can submit documents, manage signers, and automate notarization workflows, or incorporate companies in Germany”
   • [claimed-docs] “This endpoint creates an incorporation request for a company in Germany such as a GmbH or UG, including company details, shareholders, and d…”
   • [claimed-docs] “This endpoint creates a notarization request for a document”
   • [claimed-docs] “POST https://api.beglaubigt.de/v1/trade-registration”
   • [claimed-docs] “This signature is generated using the HMAC-SHA256 algorithm and a secret key that is shared exclusively between Beglaubigt and your system.”
   • [claimed-docs] “The `appointment.completed` event is automatically triggered when the notary appointment date has passed.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.beglaubigt.de/llms.txt # Beglaubigt.de API - [Introduction to Beglaubigt.de API](/): Welcome to th…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.beglaubigt.de/openapi.json, https://docs.beglaubigt.de/swagger.json, https://docs.begla…”

   proof ↗⚑ flag

5. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round drawn
   Docusign—none0/10

   No evidence describes granular, scoped/least-privilege API credentials or OAuth scopes tailored for AI agents; the MCP connector docs mention triggering IAM workflow actions but not credential scoping controls. A community report even describes an API-user permission failure where embedded signing let a single API user's session expose the entire account's data, undermining any claim of fine-grained least-privilege access.

   • [claimed-docs] “The Docusign Connector in Anthropic Claude via MCP server provides a supported way to connect Claude to Docusign IAM capabilities.”
   • [claimed-docs] “Retrieve agreement context and metadata... Query agreement status and key dates... Trigger workflow actions through IAM tools”
   • [community] “We wanted embedded flows with one API user, but discovered that on page refresh, users could break out of the signing page and view/click ar…”

   proof ↗⚑ flag

   Beglaubigt.de—none0/10

   No evidence of API key scoping, permission tiers, or least-privilege credential issuance for agents; docs describe HMAC signature verification for webhooks but nothing about scoped/restricted API credentials. Missing for 10: scoped API key/token creation, permission/role granularity, agent-specific credential management, documentation on least-privilege access control.

   • [claimed-docs] “This signature is generated using the HMAC-SHA256 algorithm and a secret key that is shared exclusively between Beglaubigt and your system.”

   proof ↗⚑ flag

6. ai-native userBuild against official SDKs

   weight 2 · round to Docusign
   Docusign✓fullprobed8/10

   Docusign ships official client SDKs (e.g., docusign-esign-node-client) built from OpenAPI/Swagger specs, backed by a dedicated developer center and REST API docs, and community reports include successful hands-on integrations using the REST API. Missing for 10: independent corroboration of SDK quality/completeness across all supported languages, and machine-discoverable API specs (llms.txt and openapi.json probes both returned 404), plus some community reports of API friction that temper confidence in a flawless experience.

   • [claimed-docs] “Send, sign, and approve documents using this client.”
   • [claimed-docs] “The Official Docusign Node.js Client Library used to interact with the eSign REST API. Send, sign, and approve documents using this client.”
   • [claimed-docs] “Request Signatures & Automate Forms | REST API | Docusign”
   • [claimed-docs] “Docusign Developer Center | eSignature APIs & Resources | Docusign”
   • [github] “We use OpenAPI/Swagger files to build many of our developer tools including our client SDKs”
   • [github] “We use OpenAPI/Swagger files to build many of our developer tools including our client SDKs using `swagger-codegen`.”
   • [community] “We did exactly this embedded signing integration and it was fairly seamless - built a POC in Postman in about an hour and a Jr dev built a p…”
   • [community] “We use the v2 REST API creating embedded envelope signing URLs without issues. Documentation is fantastic in its thoroughness - opposite exp…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.docusign.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.docusign.com/openapi.json, https://developers.docusign.com/swagger.json, https://…”

   proof ↗⚑ flag

   Beglaubigt.de—none0/10

   Evidence shows a REST API with docs and webhooks, but there is no mention of official SDKs, client libraries, or language-specific packages, and the OpenAPI spec probe returned 404s across all candidate paths, suggesting no machine-consumable spec to auto-generate SDKs either.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.beglaubigt.de/openapi.json, https://docs.beglaubigt.de/swagger.json, https://docs.begla…”
   • [claimed-docs] “This signature is generated using the HMAC-SHA256 algorithm and a secret key that is shared exclusively between Beglaubigt and your system.”

   proof ↗⚑ flag

7. ai-native userSubscribe to events via webhooks

   weight 2 · round to Beglaubigt.de
   Docusign—none0/10

   The evidence pack never mentions webhooks, event subscriptions, or DocuSign Connect (the product's known webhook feature); only REST APIs, SDKs, MCP connector, and unrelated product features are cited. Since webhook support is a plausible axis for an API-driven product like Docusign, absence of evidence makes this 'none' rather than 'na'.

   ⚑ flag

   Beglaubigt.de~partialclaimed6/10

   Docs describe webhook events (e.g., appointment.completed), real-time notarization notifications, and HMAC-SHA256 signature verification for incoming webhook payloads, indicating an event-driven webhook system exists. However, there's no explicit documentation of a subscription/registration endpoint or full event catalog for AI-native automation. Missing for 10: explicit webhook subscription/management API, full list of subscribable event types, and independent confirmation of webhook reliability.

   • [claimed-docs] “Real-time updates: Get instant notifications when notarization events are completed.”
   • [claimed-docs] “This signature is generated using the HMAC-SHA256 algorithm and a secret key that is shared exclusively between Beglaubigt and your system.”
   • [claimed-docs] “The `appointment.completed` event is automatically triggered when the notary appointment date has passed.”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Docusign
   Docusign✓fullclaimed7/10

   Docusign documents multiple AI-generated insight features directly in-product: AI-Assisted Summary and Q&A for signers, AI-Assisted Review that flags risky language, suggests redlines, and drafts new clauses against playbooks, and CLM's AI clause-compliance flagging and drafting. These are first-party vendor claims with no independent hands-on corroboration of the AI quality itself. Missing for 10: independent/third-party validation of AI insight accuracy, and no community evidence confirming these AI features work as described in practice.

   • [claimed-docs] “Our AI-Assisted Summary and Q&A features increase trust in agreements”
   • [claimed-docs] “Review and analyze agreements, flag potentially risky language, suggest surgical edits, and draft new language from an intuitive AI-powered …”
   • [claimed-docs] “Review agreements against your playbooks and ready-to-deploy agents and get suggested redlines to align terms with your requirements.”
   • [claimed-docs] “Docusign AI-Assisted Review integrates into MS Word to analyze, redline, and draft language based on your playbooks.”
   • [claimed-docs] “use AI to flag non-compliant clauses, suggest approved language, and draft new clauses on demand”
   • [claimed-docs] “AI-generated summaries and built-in Q&A give signers clarity faster so they can sign with confidence.”
   • [claimed-docs] “Leverage AI to easily create new contract review playbooks based on your standard templates or other reference documents.”

   proof ↗⚑ flag

   Beglaubigt.de—none0/10

   Beglaubigt.de is a notarization/incorporation workflow API; the only AI-related mention is signature/date field auto-detection during document processing (beglaubigt-docs-5), which is a document-parsing feature, not AI-generated insights or suggestions surfaced to the user from their data. No evidence of dashboards, analytics, recommendations, or generative insights derived from user data.

   • [claimed-docs] “Signature and location/date fields will be automatically identified across the entire document using AI-powered detection.”

   proof ↗⚑ flag

2. ai-native userSet up automations that run autonomously in the background

   weight 2 · round to Docusign
   Docusign~partialprobed6/10

   Docusign offers configurable workflows, CLM automation, and an official MCP server that lets AI agents (e.g., Claude) trigger workflow actions and retrieve agreement context, which supports agentic automation. However, there's no explicit evidence of scheduled, unattended, or fully autonomous background execution (e.g., cron-like triggers, webhooks, or agent-initiated jobs without a live AI session) — missing for 10: documented background/scheduled automation, webhook/event-driven triggers, and independent confirmation that MCP-driven workflows run without active human/agent supervision.

   • [claimed-docs] “take advantage of configurable workflows to tackle your trickiest agreement challenges”
   • [claimed-docs] “Trigger workflow actions through IAM tools”
   • [claimed-docs] “The Docusign Connector in Anthropic Claude via MCP server provides a supported way to connect Claude to Docusign IAM capabilities.”
   • [probe] “official MCP server documented at https://developers.docusign.com/platform/mcp-server/”
   • [claimed-docs] “Generate contracts in a click with dynamic templates and use AI to flag non-compliant clauses, suggest approved language, and draft new clau…”

   proof ↗⚑ flag

   Beglaubigt.de~partialclaimed5/10

   The API supports triggering document workflows (incorporation, notarization, translation, tax registration) and emits webhook events like appointment.completed with HMAC-signed real-time notifications, which together allow building background automations that react to business events without manual polling — docs explicitly claim businesses can 'automate notarization workflows'. However there is no evidence of a built-in scheduler, multi-step workflow builder, or agent-triggered chaining beyond basic API+webhook usage. Missing for 10: evidence of a no-code/automation builder, orchestration across multiple document types, third-party automation platform integrations, and independent confirmation that webhooks reliably drive autonomous flows.

   • [claimed-docs] “businesses can submit documents, manage signers, and automate notarization workflows, or incorporate companies in Germany”
   • [claimed-docs] “Real-time updates: Get instant notifications when notarization events are completed.”
   • [claimed-docs] “This signature is generated using the HMAC-SHA256 algorithm and a secret key that is shared exclusively between Beglaubigt and your system.”
   • [claimed-docs] “The `appointment.completed` event is automatically triggered when the notary appointment date has passed.”

   proof ↗⚑ flag

3. ai-native userOperate the product with natural-language commands

   weight 2 · round to Docusign
   Docusign✓fullprobed7/10

   Docusign documents a supported MCP connector enabling Claude, Gemini CLI, and Copilot Studio to query agreement status/metadata and trigger IAM workflow actions via natural-language commands, plus AI-powered chat interfaces for contract review and summaries. This directly shows natural-language operation of core agreement workflows through agentic integrations. Missing for 10: independent/hands-on user verification of the MCP connector's reliability and breadth of NL command coverage beyond vendor blog examples.

   • [claimed-docs] “Retrieve agreement context and metadata”
   • [claimed-docs] “Trigger workflow actions through IAM tools”
   • [claimed-docs] “The Docusign Connector in Anthropic Claude via MCP server provides a supported way to connect Claude to Docusign IAM capabilities.”
   • [claimed-docs] “Retrieve agreement context and metadata... Query agreement status and key dates... Trigger workflow actions through IAM tools”
   • [claimed-docs] “Query agreement data and automate agreement processes from your terminal by pairing Gemini CLI with Docusign MCP.”
   • [claimed-docs] “Build agreement workflows: Docusign MCP & Claude”
   • [claimed-docs] “Internal enterprise GitHub Copilot”
   • [probe] “official MCP server documented at https://developers.docusign.com/platform/mcp-server/”
   • [claimed-docs] “Review and analyze agreements, flag potentially risky language, suggest surgical edits, and draft new language from an intuitive AI-powered …”

   proof ↗⚑ flag

   Beglaubigt.de—none0/10

   Evidence shows only structured REST API endpoints (incorporation, notarization, translation, tax registration) and llms.txt files aimed at helping AI agents read documentation — there is no chat interface, NL command parser, or agentic control surface letting an end user type natural-language instructions to operate the product.

   • [claimed-docs] “businesses can submit documents, manage signers, and automate notarization workflows, or incorporate companies in Germany”
   • [claimed-docs] “This endpoint creates an incorporation request for a company in Germany such as a GmbH or UG, including company details, shareholders, and d…”
   • [claimed-docs] “This endpoint creates a notarization request for a document”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.beglaubigt.de/llms.txt # Beglaubigt.de API - [Introduction to Beglaubigt.de API](/): Welcome to th…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.beglaubigt.de/openapi.json, https://docs.beglaubigt.de/swagger.json, https://docs.begla…”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round drawn
   Docusign—none0/10

   Evidence only shows a general Developer Center and REST API docs page plus an OpenAPI/Swagger spec repo, but nothing indicates an interactive, runnable API console; probes actually found 404s for openapi.json/llms.txt at the developer site, suggesting no readily discoverable interactive reference.

   • [claimed-docs] “Request Signatures & Automate Forms | REST API | Docusign”
   • [claimed-docs] “Docusign Developer Center | eSignature APIs & Resources | Docusign”
   • [github] “We use OpenAPI/Swagger files to build many of our developer tools including our client SDKs”
   • [github] “allows both humans and computers to discover and understand the capabilities of the service”
   • [probe] “PROBE llms.txt: HTTP 404 at https://developers.docusign.com/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.docusign.com/openapi.json, https://developers.docusign.com/swagger.json, https://…”

   proof ↗⚑ flag

   Beglaubigt.de—none0/10

   The docs describe endpoints (POST/GET) for incorporation, notarization, translation, etc., but there is no evidence of an interactive API reference with runnable examples (e.g., embedded try-it console, SDK code snippets executable in-browser). A probe explicitly found no OpenAPI/Swagger spec at common paths, undermining any interactive reference tooling. Missing for 10: interactive 'try it' console, runnable code samples, OpenAPI/Swagger spec availability.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.beglaubigt.de/openapi.json, https://docs.beglaubigt.de/swagger.json, https://docs.begla…”
   • [claimed-docs] “This endpoint creates an incorporation request for a company in Germany such as a GmbH or UG, including company details, shareholders, and d…”
   • [claimed-docs] “This endpoint creates a notarization request for a document”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round to Docusign
   Docusign✓fullprobed8/10

   Docusign publishes and maintains a dedicated GitHub repository of OpenAPI/Swagger specifications used to generate their client SDKs, explicitly stated to let 'humans and computers discover and understand the capabilities of the service', plus a REST API developer docs site. Missing for 10: a directly discoverable openapi.json/swagger.json at the main developer site (probe found 404s at common well-known paths), so users must know to find the GitHub repo rather than a single canonical spec URL.

   • [github] “We use OpenAPI/Swagger files to build many of our developer tools including our client SDKs”
   • [github] “allows both humans and computers to discover and understand the capabilities of the service”
   • [github] “We use OpenAPI/Swagger files to build many of our developer tools including our client SDKs using `swagger-codegen`.”
   • [claimed-docs] “Request Signatures & Automate Forms | REST API | Docusign”
   • [claimed-docs] “Docusign Developer Center | eSignature APIs & Resources | Docusign”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.docusign.com/openapi.json, https://developers.docusign.com/swagger.json, https://…”

   proof ↗⚑ flag

   Beglaubigt.de—none0/10

   A direct probe for OpenAPI/Swagger spec files at common paths returned 404 on all candidates, and no evidence pack item references a downloadable machine-readable API spec — only an llms.txt (plain text docs index) exists, which is not an OpenAPI-equivalent schema.

   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.beglaubigt.de/openapi.json, https://docs.beglaubigt.de/swagger.json, https://docs.begla…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.beglaubigt.de/llms.txt # Beglaubigt.de API - [Introduction to Beglaubigt.de API](/): Welcome to th…”

   proof ↗⚑ flag

3. ai-native userTest against a sandbox environment without touching production data

   weight 1 · round drawn
   Docusign—none0/10

   The evidence pack contains no mention of a developer/demo sandbox account, test environment, or non-production testing capability for Docusign's API or MCP connector; only production docs, SDKs, and integration guides are cited. missing for 10: explicit sandbox/demo account documentation, guidance on testing without production data, any developer-center reference to a sandbox environment.

   ⚑ flag

   Beglaubigt.de—none0/10

   No evidence of any sandbox, test-mode, or staging environment is mentioned anywhere in the docs or probes; all documented endpoints relate to live notarization, incorporation, and tax registration workflows involving real legal documents. Given the legal/notarial nature of the product, a sandbox axis is plausible for API testing, but the evidence pack shows no such offering.

   • [claimed-docs] “businesses can submit documents, manage signers, and automate notarization workflows, or incorporate companies in Germany”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.beglaubigt.de/llms.txt # Beglaubigt.de API - [Introduction to Beglaubigt.de API](/): Welcome to th…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.beglaubigt.de/openapi.json, https://docs.beglaubigt.de/swagger.json, https://docs.begla…”

   proof ↗⚑ flag

4. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round to Docusign
   Docusign!disputedcontradicted3/10

   Docusign does expose versioned REST APIs (e.g. v2 eSignature API, OpenAPI/Swagger specs on GitHub) that could support a deprecation policy story, but no documented deprecation/versioning policy page is present, and a hands-on account describes being forced onto a 'legacy API version with no promise against sunsetting' after a security fix, directly contradicting reliable API lifecycle guarantees. missing for 10: an explicit deprecation-policy document, versioning changelog, and independent confirmation that old API versions are sunset predictably.

   • [community] “We wanted embedded flows with one API user, but discovered that on page refresh, users could break out of the signing page and view/click ar…”
   • [community] “We use the v2 REST API creating embedded envelope signing URLs without issues. Documentation is fantastic in its thoroughness - opposite exp…”
   • [github] “We use OpenAPI/Swagger files to build many of our developer tools including our client SDKs”
   • [claimed-docs] “Request Signatures & Automate Forms | REST API | Docusign”

   proof ↗⚑ flag

   Beglaubigt.de—none0/10

   The API endpoints use a /v1/ prefix suggesting some versioning, but there is no documented deprecation policy, versioning strategy, or changelog anywhere in the evidence; OpenAPI spec probes even returned 404s. missing for 10: documented versioning scheme, deprecation policy, changelog, migration guidance.

   • [claimed-docs] “POST https://api.beglaubigt.de/v1/trade-registration”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.beglaubigt.de/openapi.json, https://docs.beglaubigt.de/swagger.json, https://docs.begla…”

   proof ↗⚑ flag

Audit

1. legal-ops leadRely on a tamper-evident audit trail and completion certificate for every signed document

   weight 2 · round to Beglaubigt.de
   Docusign—none0/10

   The evidence pack contains no mention of a tamper-evident audit trail, certificate of completion, or any compliance/audit documentation for signed envelopes — only generic e-signature marketing copy, integrations, and AI features. Although this is a core, expected capability for an e-signature platform (so the axis applies), nothing in the provided docs, GitHub, or community sources substantiates it. missing for 10: documentation of Certificate of Completion, audit trail/tamper-evidence mechanism (e.g., hash-sealing, timestamping), and any independent verification of its integrity.

   ⚑ flag

   Beglaubigt.de~partialclaimed4/10

   Beglaubigt.de documents webhook events (e.g. appointment.completed) with HMAC-SHA256 signature verification, which provides some tamper-evidence for API notifications, and its notarization process implies an eventual notarized/certified output. However, there is no explicit documentation of a dedicated audit-trail feature or a formal 'completion certificate' artifact for each signed document. Missing for 10: explicit audit-trail export/report, a documented completion certificate deliverable, and independent verification of tamper-evidence claims.

   • [claimed-docs] “Real-time updates: Get instant notifications when notarization events are completed.”
   • [claimed-docs] “This signature is generated using the HMAC-SHA256 algorithm and a secret key that is shared exclusively between Beglaubigt and your system.”
   • [claimed-docs] “The `appointment.completed` event is automatically triggered when the notary appointment date has passed.”
   • [claimed-docs] “This endpoint creates a notarization request for a document”

   proof ↗⚑ flag

2. legal-ops leadRequire stronger signer identity verification (SMS, ID check, knowledge-based) on sensitive documents

   weight 1 · round to Docusign
   Docusign✓fullclaimed8/10

   Docusign Identify offers multiple ID verification methods explicitly (SMS one-time-passcode, government ID + biometric check, knowledge-based/risk-based verification) and a Risk-Based Verification workflow that dynamically escalates verification strength based on risk — directly matching the legal-ops need for stronger identity checks on sensitive documents. The pricing page also confirms '5 identity verifications' as a configurable feature tier. Missing for 10: independent/hands-on third-party validation of these verification flows in practice and clearer documentation on per-document/per-envelope configuration granularity.

   • [claimed-docs] “Check the authenticity of government issue identity documents or verify recipient identities in less than a minute.”
   • [claimed-docs] “Enable repeat users to verify their identity by entering a one-time-passcode sent to their phone in seconds.”
   • [claimed-docs] “Dynamically adjust the type of verification your signers must complete based on an automated and instant risk assessment with our Risk-Based…”
   • [claimed-docs] “Require recipients to upload a photo of their government ID & complete a quick biometric challenge.”
   • [claimed-docs] “Reduce fraud risk with 5 identity verifications”

   proof ↗⚑ flag

   Beglaubigt.de~partialclaimed3/10

   Docs mention remote identity verification via eID or video as part of notarization, which is a form of stronger identity check, but there is no evidence of SMS verification, knowledge-based authentication, or a legal-ops control to selectively require stronger verification tiers per document. Missing for 10: SMS verification option, knowledge-based authentication, and an API/UI setting letting legal-ops choose verification strength per document.

   • [claimed-docs] “Complete identity verification remotely (eID or video)”
   • [claimed-docs] “This endpoint creates a notarization request for a document”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round drawn
   Docusign—none0/10

   The evidence pack shows Docusign has a REST API, SDKs, and an MCP connector for triggering workflow actions, but nothing explicitly describes bulk/batch operations (e.g., a bulk-send feature, batch API endpoint, or multi-item automation) that would let an AI-native user act on many items at once. Missing for 10: any explicit bulk-send/batch-processing feature, batch API endpoint documentation, or evidence of MCP/agent tools operating on multiple envelopes/agreements simultaneously.

   • [claimed-docs] “Request Signatures & Automate Forms | REST API | Docusign”
   • [claimed-docs] “Send, sign, and approve documents using this client.”
   • [claimed-docs] “Retrieve agreement context and metadata”
   • [claimed-docs] “Trigger workflow actions through IAM tools”
   • [claimed-docs] “Retrieve agreement context and metadata... Query agreement status and key dates... Trigger workflow actions through IAM tools”

   proof ↗⚑ flag

   Beglaubigt.de—none0/10

   The API supports creating individual notarization, translation, incorporation, and tax-registration requests, and translation requests can include 'one or multiple documents,' but there is no evidence of batch/bulk endpoints, list-based submission across many items, or bulk status operations. No documentation of pagination-based bulk retrieval, batch job submission, or CSV/array-based multi-record processing was found.

   • [claimed-docs] “This endpoint creates a translation request for one or multiple documents.”
   • [claimed-docs] “This endpoint creates a notarization request for a document”
   • [claimed-docs] “This endpoint creates an incorporation request for a company in Germany such as a GmbH or UG, including company details, shareholders, and d…”

   proof ↗⚑ flag

2. ai-native userDefine rules that trigger actions automatically on events

   weight 3 · round drawn
   Docusign~partialclaimed5/10

   Docusign advertises 'configurable workflows,' conditional logic in web forms, and CLM's drag-and-drop workflow builder, plus MCP-based 'trigger workflow actions through IAM tools,' suggesting some rule-based automation exists. However there's no concrete documentation of an event-trigger/webhook rule engine (e.g., Docusign Connect-style event listeners) or examples of automatically firing actions on defined events. Missing for 10: explicit event/trigger API or webhook docs, examples of rule definitions, independent verification that automation runs reliably without manual intervention.

   • [claimed-docs] “take advantage of configurable workflows to tackle your trickiest agreement challenges”
   • [claimed-docs] “Use a drag-and-drop editor to design contract processes”
   • [claimed-docs] “implement conditional logic to ensure only relevant fields appear”
   • [claimed-docs] “Dynamically adjust the type of verification your signers must complete based on an automated and instant risk assessment with our Risk-Based…”
   • [claimed-docs] “Trigger workflow actions through IAM tools”
   • [claimed-docs] “Retrieve agreement context and metadata... Query agreement status and key dates... Trigger workflow actions through IAM tools”
   • [claimed-docs] “Generate contracts in a click with dynamic templates and use AI to flag non-compliant clauses, suggest approved language, and draft new clau…”

   proof ↗⚑ flag

   Beglaubigt.de~partialclaimed5/10

   Beglaubigt.de exposes webhook-style events (e.g. `appointment.completed`, notarization completion notifications) with HMAC signature verification, letting external systems react automatically to platform events — a foundation for automation-on-event. However there is no evidence of an in-product rule-definition UI or conditional logic engine; users must build the 'if event, then action' logic themselves in their own system. Missing for 10: a native rules/trigger builder, support for multiple event-condition combinations, and documentation of a broader event catalog beyond a couple of named events.

   • [claimed-docs] “Real-time updates: Get instant notifications when notarization events are completed.”
   • [claimed-docs] “This signature is generated using the HMAC-SHA256 algorithm and a secret key that is shared exclusively between Beglaubigt and your system.”
   • [claimed-docs] “The `appointment.completed` event is automatically triggered when the notary appointment date has passed.”

   proof ↗⚑ flag

Compliance

1. legal-ops leadSee a compliance calendar of upcoming filing deadlines and get reminders before each one

   weight 2 · round drawn
   Docusign—none0/10

   No evidence in the pack references a compliance calendar, filing deadlines, or deadline reminder features; Docusign's evidence covers e-signature, CLM, AI review, identity verification, and integrations but nothing about tracking regulatory/filing deadlines or proactive reminders for legal-ops compliance calendars.

   ⚑ flag

   Beglaubigt.de—none0/10

   Beglaubigt.de offers notarization, incorporation, and registration APIs with event webhooks, but there is no evidence of a compliance calendar view or proactive deadline reminders for legal-ops tracking of filing deadlines. Event webhooks like appointment.completed are transactional notifications, not a forward-looking deadline calendar.

   • [claimed-docs] “Real-time updates: Get instant notifications when notarization events are completed.”
   • [claimed-docs] “The `appointment.completed` event is automatically triggered when the notary appointment date has passed.”

   proof ↗⚑ flag

Compliance agentic

1. ai-native userDelegate an annual report or compliance filing to an agent that prepares it through the platform with minimal human input

   weight 2 · round to Beglaubigt.de
   Docusign~partialprobed4/10

   Docusign's MCP connector lets an agent (e.g. Claude) retrieve agreement context, query status, and trigger IAM workflow actions, and its CLM/AI-Assisted Review features can flag non-compliant clauses and draft language, suggesting a path toward agent-driven contract/compliance workflows. However, there is no evidence of an agent autonomously preparing a full 'annual report' or 'compliance filing' end-to-end with minimal human input — the evidence only covers discrete building blocks (signing, clause review, status queries) rather than a demonstrated compliance-filing delegation flow. Missing for 10: concrete example of an agent completing a compliance filing/annual report task autonomously, evidence of minimal-human-input completion, and independent corroboration beyond vendor blog/docs.

   • [claimed-docs] “The Docusign Connector in Anthropic Claude via MCP server provides a supported way to connect Claude to Docusign IAM capabilities.”
   • [claimed-docs] “Retrieve agreement context and metadata... Query agreement status and key dates... Trigger workflow actions through IAM tools”
   • [claimed-docs] “use AI to flag non-compliant clauses, suggest approved language, and draft new clauses on demand”
   • [claimed-docs] “Review and analyze agreements, flag potentially risky language, suggest surgical edits, and draft new language from an intuitive AI-powered …”
   • [claimed-docs] “Review agreements against your playbooks and ready-to-deploy agents and get suggested redlines to align terms with your requirements.”
   • [claimed-docs] “Build agreement workflows: Docusign MCP & Claude”
   • [probe] “official MCP server documented at https://developers.docusign.com/platform/mcp-server/”

   proof ↗⚑ flag

   Beglaubigt.de~partialclaimed5/10

   Beglaubigt.de exposes APIs for tax-registration, trade-registration, incorporation and notarization with webhooks (e.g. appointment.completed) that could plausibly be orchestrated by an agent with minimal human input, but there is no evidence of an 'annual report' filing endpoint or of any product feature specifically marketed as agent-delegated compliance preparation. missing for 10: explicit annual report/Jahresabschluss filing capability, evidence of an actual autonomous agent workflow completing filings end-to-end, and confirmation that human signatures/appointments aren't still required as bottlenecks.

   • [claimed-docs] “Submit a company's details to start its tax registration. An ELSTER XML document will be generated and sent the tax office”
   • [claimed-docs] “POST https://api.beglaubigt.de/v1/trade-registration”
   • [claimed-docs] “Real-time updates: Get instant notifications when notarization events are completed.”
   • [claimed-docs] “The `appointment.completed` event is automatically triggered when the notary appointment date has passed.”
   • [claimed-docs] “Wir übernehmen die Pflichtmeldungen nach Gründung: Transparenzregister-Eintrag, Gewerbeanmeldung und Anmeldung beim Finanzamt.”

   proof ↗⚑ flag

Doc api

1. ai-native userHave an agent draft an NDA and route it for signature end-to-end via the product's API or MCP server

   weight 3 · round to Docusign
   Docusign~partialprobed6/10

   Docusign provides real building blocks: a REST/eSign API to create envelopes and route documents for signature (docusign-docs-21, docusign-docs-40), an official MCP server connector for Claude that can retrieve agreement context and 'trigger workflow actions through IAM tools' (docusign-docs-47, docusign-probe-3), and AI-assisted drafting/redlining features (docusign-docs-16, docusign-docs-20, docusign-docs-44) that could draft NDA language. However, no single documented workflow shows an agent drafting an NDA and then routing it end-to-end for signature purely via the MCP server or API in one flow — drafting lives in CLM/AI-Assisted Review while signature routing lives in eSignature API/MCP triggers, and there's no first-party or independent example stitching these together for a document like an NDA. missing for 10: an explicit worked example (docs or hands-on) of drafting+signature routing combined via MCP/API, independent confirmation the MCP trigger actions actually send envelopes, and any real-world demo showing this specific NDA-drafting-to-signature pipeline.

   • [claimed-docs] “Request Signatures & Automate Forms | REST API | Docusign”
   • [claimed-docs] “The Official Docusign Node.js Client Library used to interact with the eSign REST API. Send, sign, and approve documents using this client.”
   • [claimed-docs] “Retrieve agreement context and metadata... Query agreement status and key dates... Trigger workflow actions through IAM tools”
   • [claimed-docs] “use AI to flag non-compliant clauses, suggest approved language, and draft new clauses on demand”
   • [claimed-docs] “Review and analyze agreements, flag potentially risky language, suggest surgical edits, and draft new language from an intuitive AI-powered …”
   • [probe] “official MCP server documented at https://developers.docusign.com/platform/mcp-server/”
   • [claimed-docs] “Build agreement workflows: Docusign MCP & Claude”

   proof ↗⚑ flag

   Beglaubigt.de—none0/10

   Beglaubigt.de's docs show a notarization API for submitting existing documents, managing signers, and detecting signature fields, but there is no evidence of AI drafting of contract content (e.g., an NDA) nor of any MCP server or agent-facing interface — only a REST API for notarization/incorporation/translation workflows. The story's core capabilities (AI drafting + MCP server) are unevidenced.

   • [claimed-docs] “This endpoint creates a notarization request for a document”
   • [claimed-docs] “Signature and location/date fields will be automatically identified across the entire document using AI-powered detection.”
   • [claimed-docs] “Real-time updates: Get instant notifications when notarization events are completed.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.beglaubigt.de/openapi.json, https://docs.beglaubigt.de/swagger.json, https://docs.begla…”

   proof ↗⚑ flag

2. developerGenerate, populate, and send legal documents programmatically through a documented API

   weight 3 · round to Beglaubigt.de
   Docusign!disputedcontradicted6/10

   Docusign ships a well-documented REST API, official OpenAPI specs, and client SDKs (e.g. Node.js) explicitly for generating, populating, and sending agreements programmatically, and some developers report smooth, well-documented integrations. However, other hands-on reports describe the API as an 'afterthought' compared to competitors, cite a security flaw in embedded signing flows, and describe failed/costly integration attempts, directly contradicting the polished vendor narrative. missing for 10: consistent independent confirmation without contradicting failure reports, and a working openapi.json/llms.txt discovery endpoint (both probes 404).

   • [claimed-docs] “Request Signatures & Automate Forms | REST API | Docusign”
   • [claimed-docs] “Docusign Developer Center | eSignature APIs & Resources | Docusign”
   • [github] “We use OpenAPI/Swagger files to build many of our developer tools including our client SDKs”
   • [claimed-docs] “Send, sign, and approve documents using this client.”
   • [community] “We did exactly this embedded signing integration and it was fairly seamless - built a POC in Postman in about an hour and a Jr dev built a p…”
   • [community] “We use the v2 REST API creating embedded envelope signing URLs without issues. Documentation is fantastic in its thoroughness - opposite exp…”
   • [community] “We wanted embedded flows with one API user, but discovered that on page refresh, users could break out of the signing page and view/click ar…”
   • [community] “If you're trying to wrap an e-sign provider within your application, I would recommend HelloSign 1000x. HelloSign's API is a first class cit…”
   • [community] “I once worked at a company that dealt with DocuSign integration; rumors were we paid more than double $20,000, and the integration never rea…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developers.docusign.com/openapi.json, https://developers.docusign.com/swagger.json, https://…”

   proof ↗⚑ flag

   Beglaubigt.de✓fullprobed7/10

   Documentation shows concrete POST endpoints for creating incorporation, notarization, translation, tax-registration, and trade-registration requests, plus GET endpoints and webhook events, indicating a genuine programmatic API for populating/sending legal documents. However, missing for 10: a discoverable OpenAPI/Swagger spec (probe found all candidate spec URLs 404), independent developer corroboration or third-party usage reports, and detail on request/response schemas or SDKs.

   • [claimed-docs] “This endpoint creates an incorporation request for a company in Germany such as a GmbH or UG, including company details, shareholders, and d…”
   • [claimed-docs] “This endpoint retrieves the details of an incorporation”
   • [claimed-docs] “This endpoint creates a notarization request for a document”
   • [claimed-docs] “This endpoint creates a translation request for one or multiple documents.”
   • [claimed-docs] “Submit a company's details to start its tax registration. An ELSTER XML document will be generated and sent the tax office”
   • [claimed-docs] “POST https://api.beglaubigt.de/v1/trade-registration”
   • [claimed-docs] “Real-time updates: Get instant notifications when notarization events are completed.”
   • [claimed-docs] “The `appointment.completed` event is automatically triggered when the notary appointment date has passed.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.beglaubigt.de/openapi.json, https://docs.beglaubigt.de/swagger.json, https://docs.begla…”

   proof ↗⚑ flag

Governance

1. legal-ops leadPrepare board consents and resolutions and collect approvals online

   weight 2 · round to Docusign
   Docusign✓fullcommunity7/10

   Docusign's core eSignature product supports creating reusable templates, configurable workflows, and routing for multi-party sign-off, which covers preparing and circulating documents like board consents/resolutions and collecting approvals online. However, there is no evidence of legal-ops-specific board-resolution templates or governance-specific workflow features, and community feedback flags integration/security friction that could affect legal-ops implementations. Missing for 10: dedicated board-resolution/corporate-governance templates, evidence of legal-ops specific approval chains (e.g., quorum tracking), and independent validation of reliability for this exact use case.

   • [claimed-docs] “take advantage of configurable workflows to tackle your trickiest agreement challenges”
   • [claimed-docs] “Save hours of manual setup with reusable templates”
   • [claimed-docs] “Standardize agreements by sharing templates with your team”
   • [claimed-docs] “Avoid delays by enabling delegated signing”
   • [claimed-docs] “Securely store and access all your agreements in one place”
   • [community] “We use the v2 REST API creating embedded envelope signing URLs without issues. Documentation is fantastic in its thoroughness - opposite exp…”

   proof ↗⚑ flag

   Beglaubigt.de~partialclaimed3/10

   Beglaubigt.de offers generic document submission, signer management, and notarization workflows (with signature-field auto-detection and appointment/event webhooks) that could technically be applied to notarize a board resolution, but there is no evidence of board-consent/resolution templates, multi-party approval tracking, or governance-specific workflows tailored to equity fundraising. Missing for 10: dedicated board-resolution/consent templates, multi-signer approval sequencing/voting, and any governance-specific use case documentation.

   • [claimed-docs] “businesses can submit documents, manage signers, and automate notarization workflows, or incorporate companies in Germany”
   • [claimed-docs] “This endpoint creates a notarization request for a document”
   • [claimed-docs] “Signature and location/date fields will be automatically identified across the entire document using AI-powered detection.”
   • [claimed-docs] “Real-time updates: Get instant notifications when notarization events are completed.”

   proof ↗⚑ flag

Hiring

1. legal-ops leadRun hiring and equity paperwork — offer letters, confidentiality/IP agreements, and option grants — through the platform

   weight 2 · round to Docusign
   Docusign~partialclaimed5/10

   Docusign's generic eSignature and template/workflow features (reusable templates, configurable workflows, real-time collaboration, Salesforce integration) could be used to send and sign offer letters, IP agreements, or option grants, but there is no evidence of equity/HR-specific templates, cap-table or option-grant management integration, or hiring-specific workflow support. Missing for 10: dedicated offer-letter/option-grant templates, HR/equity system integrations (e.g., cap table tools like Carta), and any case study or docs specifically covering hiring/equity paperwork use cases.

   • [claimed-docs] “Save hours of manual setup with reusable templates”
   • [claimed-docs] “Standardize agreements by sharing templates with your team”
   • [claimed-docs] “take advantage of configurable workflows to tackle your trickiest agreement challenges”
   • [claimed-docs] “Easily integrate your agreements with your apps of choice, including Salesforce, Microsoft, Google, Zoom and more.”
   • [claimed-docs] “Send, sign, and succeed with the world’s #1 eSignature solution and the world’s #1 CRM, together.”

   proof ↗⚑ flag

   Beglaubigt.de—none0/10

   Beglaubigt.de's documented capabilities cover generic document notarization, translation, incorporation, tax/trade registration, and apostilles for German companies — but no evidence pack item mentions offer letters, confidentiality/IP agreements, or option grants, nor any equity/HR paperwork workflow support. The evidence shows only signature-field detection on arbitrary uploaded documents, which is not the same as a legal-ops equity/hiring document suite.

   • [claimed-docs] “businesses can submit documents, manage signers, and automate notarization workflows, or incorporate companies in Germany”
   • [claimed-docs] “This endpoint creates a notarization request for a document”
   • [claimed-docs] “Signature and location/date fields will be automatically identified across the entire document using AI-powered detection.”

   proof ↗⚑ flag

Esign

1. founderSend a document for legally binding e-signature to multiple recipients with routing

   weight 3 · round to Docusign
   Docusign✓fullcommunity8/10

   Docusign's core eSignature product explicitly supports configurable workflows, delegated signing, and sending to multiple recipients with routing, backed by extensive first-party docs and a mature REST API/SDKs for building signing flows. Community evidence (comm-4, comm-5) corroborates that embedded/API-based signing works smoothly in practice, though other community reports focus on unrelated integration/security complaints rather than the routing feature itself. Missing for 10: independent hands-on confirmation specifically of multi-recipient sequential/parallel routing behavior (most community evidence discusses embedded signing or security, not routing order).

   • [claimed-docs] “Send, sign and manage all your agreements for free.”
   • [claimed-docs] “take advantage of configurable workflows to tackle your trickiest agreement challenges”
   • [claimed-docs] “Avoid delays by enabling delegated signing”
   • [claimed-docs] “Request Signatures & Automate Forms | REST API | Docusign”
   • [community] “We did exactly this embedded signing integration and it was fairly seamless - built a POC in Postman in about an hour and a Jr dev built a p…”
   • [community] “We use the v2 REST API creating embedded envelope signing URLs without issues. Documentation is fantastic in its thoroughness - opposite exp…”

   proof ↗⚑ flag

   Beglaubigt.de~partialclaimed3/10

   Beglaubigt.de's docs mention submitting documents and managing signers for notarization requests with AI-detected signature fields, which implies some multi-signer capability, but there is no evidence of routing logic (sequential/parallel order, per-recipient roles) for standard e-signature workflows — the platform's core focus is notarization/incorporation, not generic e-signature routing. Missing for 10: explicit routing/order configuration for multiple recipients, confirmation that signatures are 'legally binding e-signatures' rather than tied only to notarization appointments, and any independent corroboration of multi-recipient workflows.

   • [claimed-docs] “businesses can submit documents, manage signers, and automate notarization workflows, or incorporate companies in Germany”
   • [claimed-docs] “This endpoint creates a notarization request for a document”
   • [claimed-docs] “Signature and location/date fields will be automatically identified across the entire document using AI-powered detection.”

   proof ↗⚑ flag

Esign embed

1. developerEmbed the signing experience inside my own app or website

   weight 2 · round to Docusign
   Docusign!disputedcontradicted6/10

   Docusign's docs and API support embedding signing/forms into apps (docusign-docs-43 embed forms, docusign-docs-21/22 REST API for building custom flows), and community reports confirm working embedded signing integrations built via the REST API (docusign-comm-4, docusign-comm-5). However, a separate hands-on account documents a concrete security flaw in the embedded signing flow — users could break out of the signing iframe and access the whole account, forcing a downgrade to a legacy API (docusign-comm-1) — a documented counter-example that contradicts the claim of a clean embed experience. Missing for 10: first-party embedded-signing quickstart/tutorial evidence, resolution confirmation of the reported security issue, and independent recent corroboration beyond a single old HN thread.

   • [claimed-docs] “Embed forms directly into your business applications, so your customers get the consistent user experience and look they expect from your br…”
   • [claimed-docs] “Request Signatures & Automate Forms | REST API | Docusign”
   • [community] “We wanted embedded flows with one API user, but discovered that on page refresh, users could break out of the signing page and view/click ar…”
   • [community] “We did exactly this embedded signing integration and it was fairly seamless - built a POC in Postman in about an hour and a Jr dev built a p…”
   • [community] “We use the v2 REST API creating embedded envelope signing URLs without issues. Documentation is fantastic in its thoroughness - opposite exp…”
   • [community] “If you're trying to wrap an e-sign provider within your application, I would recommend HelloSign 1000x. HelloSign's API is a first class cit…”

   proof ↗⚑ flag

   Beglaubigt.de—none0/10

   Beglaubigt.de exposes API endpoints for notarization, translation, incorporation, etc., but there is no evidence of any embeddable widget, iframe, or SDK for embedding a signing UI inside a third-party app or website — the evidence pack only shows backend API calls and webhook events. missing for 10: embeddable signing widget/iframe, front-end SDK or JS component, hosted signing page for embedding, customization/branding options for embedded flow.

   • [claimed-docs] “This endpoint creates a notarization request for a document”
   • [claimed-docs] “Signature and location/date fields will be automatically identified across the entire document using AI-powered detection.”
   • [claimed-docs] “Real-time updates: Get instant notifications when notarization events are completed.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://docs.beglaubigt.de/llms.txt # Beglaubigt.de API - [Introduction to Beglaubigt.de API](/): Welcome to th…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.beglaubigt.de/openapi.json, https://docs.beglaubigt.de/swagger.json, https://docs.begla…”

   proof ↗⚑ flag

Esign scale

1. legal-ops leadBulk-send the same document to many recipients at once

   weight 1 · round drawn
   Docusign—none0/10

   The evidence pack describes templates, workflows, branding, identity verification, and AI features but never mentions a bulk-send/mass-mail capability for sending one document to many recipients simultaneously. Missing for 10: any documentation of a 'bulk send' or mass-recipient distribution feature, recipient list upload, or per-recipient tracking at scale.

   ⚑ flag

   Beglaubigt.de—none0/10

   Beglaubigt.de's docs describe creating a single notarization/translation/incorporation request and managing signers on that request, but there is no mention of a bulk-send or mass-distribution feature for sending one document to many recipients at once. Missing for 10: any bulk-send/batch-recipient API or UI capability, evidence of multi-recipient campaign sending.

   • [claimed-docs] “businesses can submit documents, manage signers, and automate notarization workflows, or incorporate companies in Germany”
   • [claimed-docs] “This endpoint creates a notarization request for a document”

   proof ↗⚑ flag

2. legal-ops leadSet signing order, automatic reminders, and expirations on outstanding signature requests

   weight 1 · round to Docusign
   Docusign~partialclaimed3/10

   Evidence only vaguely references 'configurable workflows' and 'delegated signing' for agreement flows, with no explicit documentation of signing order/routing, automatic reminder scheduling, or envelope expiration settings, which are the specific capabilities the story asks about. Missing for 10: explicit docs on setting signer routing order, reminder frequency/timing configuration, and expiration date settings for envelopes.

   • [claimed-docs] “take advantage of configurable workflows to tackle your trickiest agreement challenges”
   • [claimed-docs] “Avoid delays by enabling delegated signing”

   proof ↗⚑ flag

   Beglaubigt.de—none0/10

   Beglaubigt.de's docs describe managing signers and notarization/appointment events (e.g., appointment.completed webhooks) but nowhere mention configurable signing order, automatic reminders, or expiration settings on signature requests.

   • [claimed-docs] “businesses can submit documents, manage signers, and automate notarization workflows, or incorporate companies in Germany”
   • [claimed-docs] “Real-time updates: Get instant notifications when notarization events are completed.”
   • [claimed-docs] “The `appointment.completed` event is automatically triggered when the notary appointment date has passed.”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Beglaubigt.de
   Docusign~partialprobed5/10

   Docusign publishes a comprehensive eSignature REST API, SDKs, OpenAPI specs, and an MCP server enabling programmatic sending, signing, and workflow triggering (docusign-docs-21, docusign-gh-1, docusign-docs-47, docusign-probe-3), but several UI-only capabilities (CLM drag-and-drop process builder, web-forms drag-and-drop editor, AI-assisted review chat) are marketed as click/drag experiences without documented API equivalents. Community reports also describe real API limitations/security issues in embedded signing flows that forced a downgrade to a legacy API (docusign-comm-1), undercutting full UI/API parity. Missing for 10: explicit API endpoints for CLM workflow design, web-forms builder, and AI-review features, plus independent confirmation that all UI actions are API-reachable without workarounds.

   • [claimed-docs] “Request Signatures & Automate Forms | REST API | Docusign”
   • [github] “We use OpenAPI/Swagger files to build many of our developer tools including our client SDKs”
   • [claimed-docs] “Retrieve agreement context and metadata... Query agreement status and key dates... Trigger workflow actions through IAM tools”
   • [probe] “official MCP server documented at https://developers.docusign.com/platform/mcp-server/”
   • [community] “We wanted embedded flows with one API user, but discovered that on page refresh, users could break out of the signing page and view/click ar…”
   • [claimed-docs] “Use a drag-and-drop editor to design contract processes”
   • [claimed-docs] “Use drag-and-drop functionality and clicks, not code, to build your forms in minutes.”

   proof ↗⚑ flag

   Beglaubigt.de~partialprobed6/10

   The docs show a genuine API-first design covering the core workflows also available in the UI—incorporation, notarization, translation, tax registration, and trade registration (docs-2,4,6,7,8), plus webhooks/signature verification for automation (docs-9,10,11), and the company explicitly markets itself as the first in Germany to offer incorporation via API (docs-22). However, some UI-surfaced conveniences (free business account bundling, company-name availability check, package selection in docs-17/18) aren't confirmed as API endpoints, and no discoverable OpenAPI/swagger spec was found (probe-2 all 404), making full UI/API parity unverifiable. Missing for 10: confirmed API endpoints for all UI-only conveniences (name check, account bundling), and a published machine-readable OpenAPI spec.

   • [claimed-docs] “This endpoint creates an incorporation request for a company in Germany such as a GmbH or UG, including company details, shareholders, and d…”
   • [claimed-docs] “This endpoint creates a notarization request for a document”
   • [claimed-docs] “This endpoint creates a translation request for one or multiple documents.”
   • [claimed-docs] “Submit a company's details to start its tax registration. An ELSTER XML document will be generated and sent the tax office”
   • [claimed-docs] “POST https://api.beglaubigt.de/v1/trade-registration”
   • [claimed-docs] “Real-time updates: Get instant notifications when notarization events are completed.”
   • [claimed-docs] “beglaubigt.de bietet als erstes Unternehmen in Deutschland eine API-Schnittstelle zur UG / GmbH Gründung in Zusammenarbeit mit Notaren.”
   • [claimed-docs] “Prüfe, ob dein Wunschname verfügbar ist – und gründe in wenigen Minuten”
   • [claimed-docs] “Erhalte ein kostenloses Geschäftskonto zu jeder Unternehmensgründung”
   • [probe] “PROBE openapi: all candidate paths 404 (https://docs.beglaubigt.de/openapi.json, https://docs.beglaubigt.de/swagger.json, https://docs.begla…”

   proof ↗⚑ flag

2. ai-native userExport all of my data in open formats and leave

   weight 3 · round drawn
   Docusign—none0/10

   The evidence pack shows Docusign APIs for sending/retrieving individual agreements and metadata, but no documented bulk data-export tool, account-closure export, or open-format portability feature that would let a user extract all their data and leave the platform.

   ⚑ flag

   Beglaubigt.de—none0/10

   Beglaubigt.de is a notarization/incorporation API service, not a data-storage platform, but the story asks whether users can export their own data (documents, records) in open formats and leave — no evidence of any export/download-all-data feature or data portability mechanism appears anywhere in the docs. This is a fair question since users submit sensitive documents and company data that they'd reasonably want to retrieve or migrate away with, so the axis applies, and no evidence of such a capability exists.

   • [claimed-docs] “businesses can submit documents, manage signers, and automate notarization workflows, or incorporate companies in Germany”
   • [claimed-docs] “This endpoint creates a notarization request for a document”
   • [claimed-docs] “This endpoint creates a translation request for one or multiple documents.”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Docusign—none0/10

   No evidence in the pack addresses data residency, regional storage options, or geographic data controls for Docusign; all citations focus on e-signature features, AI capabilities, integrations, and unrelated community complaints. Missing for 10: any mention of data center regions, EU/US data residency options, or customer-selectable storage location settings.

   ⚑ flag

   Beglaubigt.de—none0/10

   No evidence anywhere in the pack about data residency options, region selection, or data storage location controls; the product is a German notarization/incorporation API but nothing addresses configurable data storage region for AI-native users.

   ⚑ flag

2. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Docusign—none0/10

   No evidence in the pack addresses data retention policies, deletion controls, or configurable data lifecycle management for AI/agent interactions; the evidence covers e-signature, CLM, identity verification, and MCP connector features but nothing about retention/deletion settings.

   ⚑ flag

   Beglaubigt.de—none0/10

   No evidence of any data retention controls, deletion endpoints, or privacy/data lifecycle settings in the docs; the evidence pack covers notarization, incorporation, translation, and webhook features only.

   ⚑ flag