[ { "productId": "beglaubigt", "storyId": "agent-drafts-routes-nda", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "beglaubigt-docs-4", "beglaubigt-docs-5", "beglaubigt-docs-9", "beglaubigt-probe-2" ] }, { "productId": "beglaubigt", "storyId": "agent-files-annual-report", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "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.", "evidenceIds": [ "beglaubigt-docs-7", "beglaubigt-docs-8", "beglaubigt-docs-9", "beglaubigt-docs-11", "beglaubigt-docs-24" ] }, { "productId": "beglaubigt", "storyId": "agent-monitors-renewals", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Beglaubigt.de is a transactional API for notarization, incorporation, translation, apostille and tax registration — one-off legal document workflows, not an ongoing contract-lifecycle/renewal-tracking product. There is no concept of recurring contracts, renewal dates, or deadline monitoring in the evidence, making this axis a category mismatch rather than a missing feature.", "evidenceIds": [] }, { "productId": "beglaubigt", "storyId": "agentic-agent-docs", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "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.", "evidenceIds": [ "beglaubigt-probe-1", "beglaubigt-docs-12", "beglaubigt-docs-11", "beglaubigt-probe-2" ] }, { "productId": "beglaubigt", "storyId": "agentic-ai-insights", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [ "beglaubigt-docs-5" ] }, { "productId": "beglaubigt", "storyId": "agentic-autonomous-automation", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "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.", "evidenceIds": [ "beglaubigt-docs-1", "beglaubigt-docs-9", "beglaubigt-docs-10", "beglaubigt-docs-11" ] }, { "productId": "beglaubigt", "storyId": "agentic-builtin-assistant", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Beglaubigt.de is a notarization/incorporation API and document-workflow service, not an AI-agent product; there's no built-in AI assistant to delegate tasks to (only mentions of AI-powered field detection in documents). This axis is a category error for this product type.", "evidenceIds": [] }, { "productId": "beglaubigt", "storyId": "agentic-headless", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "beglaubigt-docs-1", "beglaubigt-docs-2", "beglaubigt-docs-4", "beglaubigt-docs-9", "beglaubigt-docs-10", "beglaubigt-docs-11", "beglaubigt-probe-2" ] }, { "productId": "beglaubigt", "storyId": "agentic-mcp-client", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Beglaubigt.de is a notarization/incorporation SaaS API, not an AI agent or assistant product; the evidence pack contains no MCP client capability, and consuming MCP servers is a client-side agent role that doesn't apply to this kind of product. This differs from publishing an MCP server (which would be applicable to a SaaS product) — here the story is about the product acting as an MCP client, which is not a fit for its category.", "evidenceIds": [] }, { "productId": "beglaubigt", "storyId": "agentic-mcp-server", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "beglaubigt-probe-2", "beglaubigt-docs-1" ] }, { "productId": "beglaubigt", "storyId": "agentic-nl-commands", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [ "beglaubigt-docs-1", "beglaubigt-docs-2", "beglaubigt-docs-4", "beglaubigt-probe-1", "beglaubigt-probe-2" ] }, { "productId": "beglaubigt", "storyId": "agentic-official-cli", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Beglaubigt.de is a notarization/legal-document API/SaaS product, not a developer tool or CLI-oriented platform where an official CLI would be a natural offering; there is no CLI mentioned anywhere and the product's interface is API/web-based only, making a CLI axis a category mismatch rather than a missing feature.", "evidenceIds": [] }, { "productId": "beglaubigt", "storyId": "agentic-public-api", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "beglaubigt-docs-1", "beglaubigt-docs-2", "beglaubigt-docs-4", "beglaubigt-docs-8", "beglaubigt-docs-10", "beglaubigt-docs-11", "beglaubigt-probe-1", "beglaubigt-probe-2" ] }, { "productId": "beglaubigt", "storyId": "agentic-scoped-keys", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [ "beglaubigt-docs-10" ] }, { "productId": "beglaubigt", "storyId": "agentic-sdks", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "beglaubigt-probe-2", "beglaubigt-docs-10" ] }, { "productId": "beglaubigt", "storyId": "agentic-webhooks", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "beglaubigt-docs-9", "beglaubigt-docs-10", "beglaubigt-docs-11" ] }, { "productId": "beglaubigt", "storyId": "annual-report-filings", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows only one-time post-incorporation filings (tax registration via ELSTER, trade registration, transparency register entry) at company formation, not recurring annual report or franchise-tax filing services on an ongoing basis. Missing for 10: any evidence of recurring/annual compliance filing, franchise tax handling, or ongoing registered-agent style maintenance work.", "evidenceIds": [ "beglaubigt-docs-7", "beglaubigt-docs-8", "beglaubigt-docs-24" ] }, { "productId": "beglaubigt", "storyId": "api-interactive-docs", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "beglaubigt-probe-2", "beglaubigt-docs-2", "beglaubigt-docs-4" ] }, { "productId": "beglaubigt", "storyId": "api-machine-spec", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [ "beglaubigt-probe-2", "beglaubigt-probe-1" ] }, { "productId": "beglaubigt", "storyId": "api-sandbox", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [ "beglaubigt-docs-1", "beglaubigt-probe-1", "beglaubigt-probe-2" ] }, { "productId": "beglaubigt", "storyId": "api-versioning-policy", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "beglaubigt-docs-8", "beglaubigt-probe-2" ] }, { "productId": "beglaubigt", "storyId": "audit-trail-certificate", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "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.", "evidenceIds": [ "beglaubigt-docs-9", "beglaubigt-docs-10", "beglaubigt-docs-11", "beglaubigt-docs-4" ] }, { "productId": "beglaubigt", "storyId": "automation-bulk-operations", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "beglaubigt-docs-6", "beglaubigt-docs-4", "beglaubigt-docs-2" ] }, { "productId": "beglaubigt", "storyId": "automation-rules-engine", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "beglaubigt-docs-9", "beglaubigt-docs-10", "beglaubigt-docs-11" ] }, { "productId": "beglaubigt", "storyId": "automation-scheduled-jobs", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Beglaubigt.de is a document notarization/incorporation API/service, not an AI agent or workflow platform; there is no concept of scheduling recurring jobs or workflows in this product category. This axis is a category error for a notarization/legal-services API.", "evidenceIds": [] }, { "productId": "beglaubigt", "storyId": "automation-versioned-workflows", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Beglaubigt.de is a notarization/incorporation API service, not an automation/workflow-building tool; there is no concept of user-created 'automations' to version, review, or roll back in the evidence.", "evidenceIds": [] }, { "productId": "beglaubigt", "storyId": "board-consents", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "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.", "evidenceIds": [ "beglaubigt-docs-1", "beglaubigt-docs-4", "beglaubigt-docs-5", "beglaubigt-docs-9" ] }, { "productId": "beglaubigt", "storyId": "bulk-send-envelopes", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "beglaubigt-docs-1", "beglaubigt-docs-4" ] }, { "productId": "beglaubigt", "storyId": "compliance-calendar", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [ "beglaubigt-docs-9", "beglaubigt-docs-11" ] }, { "productId": "beglaubigt", "storyId": "contract-approval-workflows", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Beglaubigt.de is a notarization/incorporation/translation API service, not a contract-lifecycle or e-signature platform with configurable multi-step approval workflows; the evidence shows document submission and notary/signer management, not approval routing before signature. This is a category mismatch rather than a missing feature.", "evidenceIds": [] }, { "productId": "beglaubigt", "storyId": "contract-draft-negotiate", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Beglaubigt.de is a notarization/incorporation/translation API product focused on legal document certification workflows, not a contract-drafting or redlining tool; the story's subject (contract negotiation/redlining workflow) is outside its product category.", "evidenceIds": [] }, { "productId": "beglaubigt", "storyId": "contract-repository-search", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Beglaubigt.de is a notarization/incorporation/translation API service, not a contract repository or CLM tool; there is no evidence of any document storage, search, or metadata-extraction repository for executed contracts. This axis is a category error for this product type.", "evidenceIds": [] }, { "productId": "beglaubigt", "storyId": "document-generation-api", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "beglaubigt-docs-2", "beglaubigt-docs-3", "beglaubigt-docs-4", "beglaubigt-docs-6", "beglaubigt-docs-7", "beglaubigt-docs-8", "beglaubigt-docs-9", "beglaubigt-docs-11", "beglaubigt-probe-2" ] }, { "productId": "beglaubigt", "storyId": "ein-tax-id", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Beglaubigt.de is a German platform for notarization, translation, apostilles, and GmbH/UG incorporation, with tax registration handled via the German ELSTER system (Finanzamt), not the U.S. IRS. A 'federal EIN' is a U.S.-specific tax ID concept that has no analog in this German jurisdiction, so the axis is a category mismatch for this product.", "evidenceIds": [] }, { "productId": "beglaubigt", "storyId": "embedded-signing", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "beglaubigt-docs-4", "beglaubigt-docs-5", "beglaubigt-docs-9", "beglaubigt-probe-1", "beglaubigt-probe-2" ] }, { "productId": "beglaubigt", "storyId": "equity-hiring-paperwork", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "beglaubigt-docs-1", "beglaubigt-docs-4", "beglaubigt-docs-5" ] }, { "productId": "beglaubigt", "storyId": "guided-questionnaires", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "There is evidence of structured data submission for incorporation (company details, shareholders, directors) and a digital tax registration questionnaire submitted via ELSTER, which resembles guided form-filling, but nothing describes a questionnaire flow that validates legal choices or flags items requiring attorney review — the process instead routes to real notaries for the legal check, not an in-app flagging mechanism. Missing for 10: evidence of a structured Q&A/questionnaire UI, logic that flags legally risky choices, and any attorney-review escalation feature.", "evidenceIds": [ "beglaubigt-docs-2", "beglaubigt-docs-23", "beglaubigt-docs-14" ] }, { "productId": "beglaubigt", "storyId": "incorporate-end-to-end", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Beglaubigt.de is a German notarization/incorporation API focused on German entities (GmbH, UG) and German legal processes (ELSTER tax, Transparenzregister, Gewerbeanmeldung) — it has no connection to Delaware or US corporate law; this is a wrong-jurisdiction category error, not a missing feature.", "evidenceIds": [ "beglaubigt-docs-2", "beglaubigt-docs-14", "beglaubigt-docs-22" ] }, { "productId": "beglaubigt", "storyId": "legal-template-library", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Beglaubigt.de is a notarization/incorporation/translation API platform, not a legal-document template library; the evidence shows no offering of vetted NDA/agreement/policy templates for founders to self-serve, so this axis is a category mismatch rather than a gap.", "evidenceIds": [] }, { "productId": "beglaubigt", "storyId": "openness-api-parity", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "beglaubigt-docs-2", "beglaubigt-docs-4", "beglaubigt-docs-6", "beglaubigt-docs-7", "beglaubigt-docs-8", "beglaubigt-docs-9", "beglaubigt-docs-22", "beglaubigt-docs-17", "beglaubigt-docs-18", "beglaubigt-probe-2" ] }, { "productId": "beglaubigt", "storyId": "openness-full-export", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "beglaubigt-docs-1", "beglaubigt-docs-4", "beglaubigt-docs-6" ] }, { "productId": "beglaubigt", "storyId": "openness-open-license", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Beglaubigt.de is a closed commercial SaaS API for notarization/incorporation services, not an open-source software product; there is no indication source code publication is a relevant axis for this kind of service.", "evidenceIds": [] }, { "productId": "beglaubigt", "storyId": "openness-self-host", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Beglaubigt.de is a notarization/legal-services SaaS API tied to German notaries and regulatory infrastructure (ELSTER, Transparenzregister), not software that can be run on one's own infrastructure; self-hosting is not a meaningful axis for this kind of regulated service product.", "evidenceIds": [] }, { "productId": "beglaubigt", "storyId": "post-incorporation-setup", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Beglaubigt.de is a German notarization/incorporation platform for GmbH/UG entities under German law; the story's specific mechanisms (founder stock purchases, IP assignment agreements, IRS 83(b) elections) are U.S. corporate/tax law constructs that do not exist in the German legal system this product operates in. This is a jurisdictional category mismatch, not a missing feature.", "evidenceIds": [] }, { "productId": "beglaubigt", "storyId": "privacy-data-residency", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [] }, { "productId": "beglaubigt", "storyId": "privacy-no-training", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Beglaubigt.de is a notarization/incorporation/document API service, not an AI model or AI product that trains on user data; the AI-training opt-out axis doesn't apply to this category of product.", "evidenceIds": [] }, { "productId": "beglaubigt", "storyId": "privacy-retention-controls", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [] }, { "productId": "beglaubigt", "storyId": "privacy-telemetry-optout", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Beglaubigt.de is a notarization/incorporation SaaS API product, not an AI agent/assistant tool with telemetry settings relevant to AI-native usage; no evidence pack content relates to telemetry or usage tracking opt-out at all.", "evidenceIds": [] }, { "productId": "beglaubigt", "storyId": "registered-agent-service", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Beglaubigt.de is a German notarization/incorporation/translation API platform, not a US-style registered agent service handling service of process; this is a category/jurisdiction mismatch, not a missing feature.", "evidenceIds": [] }, { "productId": "beglaubigt", "storyId": "renewal-obligation-tracking", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Beglaubigt.de is a notarization/incorporation/document-legalization API service, not a contract-lifecycle management tool; nothing in the evidence relates to tracking contract renewals, expirations, or obligations with alerts.", "evidenceIds": [] }, { "productId": "beglaubigt", "storyId": "safe-financing-docs", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Beglaubigt.de is a German notarization/incorporation/document API platform (notarization, translation, apostille, company registration), not a fundraising-document or SAFE/convertible-note generation tool; generating equity-fundraising instruments is outside its product category.", "evidenceIds": [] }, { "productId": "beglaubigt", "storyId": "send-for-esignature", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "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.", "evidenceIds": [ "beglaubigt-docs-1", "beglaubigt-docs-4", "beglaubigt-docs-5" ] }, { "productId": "beglaubigt", "storyId": "signer-identity-verification", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "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.", "evidenceIds": [ "beglaubigt-docs-16", "beglaubigt-docs-4" ] }, { "productId": "beglaubigt", "storyId": "signing-order-reminders", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "beglaubigt-docs-1", "beglaubigt-docs-9", "beglaubigt-docs-11" ] }, { "productId": "clerky", "storyId": "agent-drafts-routes-nda", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Clerky's Partner API and MCP server are real and documented, but the API explicitly states it 'currently supports Delaware C-Corporation formations' only, and the MCP server tools are scoped to Clerky's startup-formation document sets (cap tables, safes, stock plans) — there is no evidence of NDA drafting or NDA e-signature routing via either channel.", "evidenceIds": [ "clerky-docs-19", "clerky-docs-20", "clerky-docs-22", "clerky-probe-5" ] }, { "productId": "clerky", "storyId": "agent-files-annual-report", "verdict": "partial", "quality": 4, "confidence": "medium", "rationale": "Clerky offers a remote MCP server and Partner API that let an AI assistant interact with document sets, forms, and workflow state (clerky-docs-19/20/22), and IRS forms can be completed and submitted online (clerky-docs-5/15), suggesting some agent-driven compliance work is possible. However, the probe shows the MCP tools are read-only with team-scoped OAuth access (clerky-probe-5), and there is no evidence of an actual 'annual report' or ongoing compliance-filing product, nor of an agent completing filings end-to-end with minimal human input. missing for 10: evidence of annual report/compliance-filing capability specifically, evidence the MCP/API can autonomously submit filings (not just read/collect data), and confirmation that human sign-off isn't required at each step.", "evidenceIds": [ "clerky-docs-19", "clerky-docs-20", "clerky-docs-22", "clerky-probe-5", "clerky-docs-5", "clerky-docs-15" ] }, { "productId": "clerky", "storyId": "agent-monitors-renewals", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Clerky's API and MCP server are scoped to formation document-set workflows (create, fill forms, sign, poll lifecycle state) — there is no evidence of tracking contract renewal dates, deadline alerts, or proactive lapse-prevention actions via the API or MCP tools.", "evidenceIds": [ "clerky-docs-19", "clerky-docs-20", "clerky-docs-22", "clerky-probe-5" ] }, { "productId": "clerky", "storyId": "agentic-agent-docs", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "Clerky's developer docs site serves a valid llms.txt (HTTP 200) with structured links to markdown-formatted docs pages, confirmed by direct probe evidence, satisfying the ability to point an agent at agent-oriented documentation. missing for 10: independent third-party confirmation of an agent successfully consuming the llms.txt in practice.", "evidenceIds": [ "clerky-probe-4", "clerky-docs-19", "clerky-docs-20" ] }, { "productId": "clerky", "storyId": "agentic-ai-insights", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Clerky is a legal document/formation platform with an MCP server and partner API for workflow automation, but there is no evidence of AI-generated insights or suggestions surfaced from the user's own data (e.g., analytics, recommendations, anomaly detection) inside the product. The MCP server exposes tools for AI assistants to act on data, not the product itself generating insights.", "evidenceIds": [ "clerky-docs-22", "clerky-probe-5" ] }, { "productId": "clerky", "storyId": "agentic-autonomous-automation", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Clerky's MCP server and Partner API let AI assistants or partner products interactively invoke Clerky tools (with team-scoped OAuth access), but nothing in the evidence describes autonomous, unattended background automations (e.g., scheduled triggers, event-driven workflows) running without a live user/assistant session initiating each action.", "evidenceIds": [ "clerky-docs-22", "clerky-probe-5", "clerky-docs-19", "clerky-docs-20" ] }, { "productId": "clerky", "storyId": "agentic-builtin-assistant", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows Clerky exposes an MCP server so external AI assistants (Claude, ChatGPT) can call into Clerky's tools, but this is the reverse of a built-in assistant inside Clerky's own product that a user delegates tasks to. No evidence of any in-app AI assistant/chat feature for delegating formation, hiring, or document tasks.", "evidenceIds": [ "clerky-docs-22", "clerky-probe-5" ] }, { "productId": "clerky", "storyId": "agentic-headless", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Clerky exposes a Partner API (create document sets, list forms, submit JSON, poll status) that could in principle be scripted, but authentication is an OAuth authorization-code flow tied to a human sign-in ('coming soon' per docs), and legal documents still require human e-signature, so true unattended/CI automation isn't demonstrated. Missing for 10: machine-to-machine/service-account auth, CLI or CI examples, and confirmation the workflow can complete without a human signing step.", "evidenceIds": [ "clerky-docs-19", "clerky-docs-20", "clerky-docs-21" ] }, { "productId": "clerky", "storyId": "agentic-mcp-client", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Clerky is a legal-paperwork SaaS, not an AI agent/assistant platform; the evidence shows it exposes its own remote MCP server (mcp.clerky.com) for other AI assistants to consume its tools, which is the opposite direction from this story (a user plugging external MCP servers into Clerky so it can use their tools). There is no evidence Clerky itself acts as an MCP client consuming outside tools, and this capability is outside its product category.", "evidenceIds": [ "clerky-docs-22", "clerky-probe-5" ] }, { "productId": "clerky", "storyId": "agentic-mcp-server", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Clerky publishes an official remote MCP server (https://mcp.clerky.com/mcp) with documented setup for Claude, ChatGPT, and other AI assistants, and a live probe confirms the endpoint is real and OAuth-gated as documented. Missing for 10: independent/community confirmation of real-world agent usage and full detail on the OAuth authorization flow completion.", "evidenceIds": [ "clerky-docs-22", "clerky-probe-5", "clerky-docs-21" ] }, { "productId": "clerky", "storyId": "agentic-nl-commands", "verdict": "partial", "quality": 7, "confidence": "medium", "rationale": "Clerky ships a live MCP server (mcp.clerky.com) enabling Claude/ChatGPT and other AI assistants to invoke Clerky tools with team-scoped access, which is the mechanism for natural-language operation; a probe confirms the endpoint is real and OAuth-gated rather than vaporware. Missing for 10: no hands-on transcript or independent report of actually issuing natural-language commands through the MCP tools, and no evidence of a broader in-app conversational/NL command interface beyond the MCP integration.", "evidenceIds": [ "clerky-docs-22", "clerky-probe-5", "clerky-probe-4" ] }, { "productId": "clerky", "storyId": "agentic-official-cli", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Clerky provides a Partner API and a remote MCP server, but no evidence of an official CLI tool for AI-native workflows; probes for docs/llms.txt found no CLI references.", "evidenceIds": [ "clerky-docs-19", "clerky-docs-20", "clerky-docs-22", "clerky-probe-4" ] }, { "productId": "clerky", "storyId": "agentic-public-api", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Clerky publishes real developer documentation for a Partner API (developers.clerky.com, discoverable via llms.txt) covering document-set lifecycle, form schemas, and endpoints like POST /v1/document_sets and GET forms, which is genuine documented programmatic access. However, the docs themselves state OAuth-based authentication is 'coming soon' and not yet live, meaning the API isn't fully operational for external partner integration yet, and scope is limited to Delaware C-Corp formations only. Missing for 10: live/functional authentication flow, evidence of broader API scope, and independent developer reports of successful integration.", "evidenceIds": [ "clerky-docs-19", "clerky-docs-20", "clerky-docs-21", "clerky-probe-4" ] }, { "productId": "clerky", "storyId": "agentic-scoped-keys", "verdict": "partial", "quality": 4, "confidence": "medium", "rationale": "Clerky documents an OAuth 2.0 bearer-token model for its Partner API with an 'access model' limiting what each token can do, and a live remote MCP server gated by OAuth ('team access you authorize') confirmed via a 401 invalid_token probe rather than being open. However, OAuth for the Partner API is explicitly marked 'coming soon' with scopes/lifetime 'to be published,' and the MCP scoping described is team-level, not clearly a fine-grained least-privilege credential model for individual agents. Missing for 10: published granular scopes/permissions list, confirmed live least-privilege token issuance flow, and independent verification of scope enforcement.", "evidenceIds": [ "clerky-docs-21", "clerky-docs-22", "clerky-probe-5" ] }, { "productId": "clerky", "storyId": "agentic-sdks", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Clerky publishes an official Partner API (REST, JSON schema-driven forms, document-set lifecycle) with docs and an llms.txt developer portal, plus a documented remote MCP server for AI assistants — both usable for programmatic/agentic integration. However there is no evidence of a packaged SDK (client libraries in Python/JS/etc.), and the API's OAuth authentication is explicitly still 'coming soon,' meaning full client access isn't yet live. Missing for 10: language-specific SDK packages, completed/live OAuth client registration, independent developer corroboration of successful integration.", "evidenceIds": [ "clerky-docs-19", "clerky-docs-20", "clerky-docs-21", "clerky-docs-22", "clerky-probe-4", "clerky-probe-5" ] }, { "productId": "clerky", "storyId": "agentic-webhooks", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "The Partner API docs explicitly describe a poll-based lifecycle model (create, submit, poll for state) rather than any webhook/event-subscription mechanism, and no evidence anywhere mentions webhooks or push notifications.", "evidenceIds": [ "clerky-docs-20", "clerky-docs-19" ] }, { "productId": "clerky", "storyId": "annual-report-filings", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence anywhere in the pack mentions annual report filing, franchise tax filing, registered agent services, or compliance deadline tracking; Clerky's documented scope is formation, equity, hiring, banking, and IRS forms only.", "evidenceIds": [] }, { "productId": "clerky", "storyId": "api-interactive-docs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Clerky's developer docs describe the Partner API lifecycle, forms, and authentication in prose (clerky-docs-19/20/21) and llms.txt lists doc pages, but there is no evidence of an interactive API reference (e.g., Swagger/OpenAPI explorer) or runnable examples; explicit probes for openapi.json/swagger.json all returned 404 (clerky-probe-3).", "evidenceIds": [ "clerky-docs-19", "clerky-docs-20", "clerky-docs-21", "clerky-probe-3", "clerky-probe-4" ] }, { "productId": "clerky", "storyId": "api-machine-spec", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Clerky has a documented Partner API with REST endpoints and JSON schema forms, but explicit probes for OpenAPI/Swagger spec files (openapi.json, swagger.json, .well-known/openapi.json) all returned 404, and no docs page offers a downloadable machine-readable spec.", "evidenceIds": [ "clerky-probe-3", "clerky-docs-19", "clerky-docs-20" ] }, { "productId": "clerky", "storyId": "api-sandbox", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Clerky's Partner API and MCP server docs describe production workflows (document sets, OAuth, live formation filings) but no evidence anywhere mentions a sandbox, test mode, or staging environment separate from production data.", "evidenceIds": [ "clerky-docs-19", "clerky-docs-20", "clerky-docs-21", "clerky-docs-22", "clerky-probe-5" ] }, { "productId": "clerky", "storyId": "api-versioning-policy", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The Partner API docs show endpoints prefixed with /v1/ but there is no evidence of a documented API versioning scheme, changelog, or deprecation policy anywhere in the docs, llms.txt index, or OpenAPI probes (which 404). Missing for 10: any explicit versioning/deprecation policy documentation, changelog, or migration guidance for breaking changes.", "evidenceIds": [ "clerky-docs-19", "clerky-docs-20", "clerky-docs-21", "clerky-probe-3", "clerky-probe-4" ] }, { "productId": "clerky", "storyId": "audit-trail-certificate", "verdict": "partial", "quality": 2, "confidence": "low", "rationale": "Clerky documents that it logs every change made to a document set or workspace so admins can see who did what, which is a basic audit-log capability, but there is no mention of tamper-evidence (e.g., cryptographic sealing, hash-chained logs) or of a signing completion certificate being issued for executed documents. Missing for 10: tamper-evident/cryptographic audit trail mechanics, completion certificate artifact, and any independent verification of these claims.", "evidenceIds": [ "clerky-docs-4" ] }, { "productId": "clerky", "storyId": "automation-bulk-operations", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows Clerky's Partner API and MCP server operate on a single document set at a time (create, fill forms, submit, poll) with no batch/bulk endpoints or bulk document/task operations documented; task assignment features are per-item, not bulk. Missing for 10: any bulk create/update endpoint, batch API operations, or bulk import/export capability across multiple items.", "evidenceIds": [ "clerky-docs-19", "clerky-docs-20", "clerky-docs-22", "clerky-probe-5" ] }, { "productId": "clerky", "storyId": "automation-rules-engine", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Clerky is a legal document/incorporation product, not a rules/automation-engine platform; defining event-triggered automation rules is a category error for this type of product.", "evidenceIds": [] }, { "productId": "clerky", "storyId": "automation-scheduled-jobs", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Clerky is a legal/formation document platform; scheduling recurring automated jobs or workflows is not a fit for its product category (document sets, formations, partner API, MCP tools for legal paperwork), and no evidence suggests any job-scheduling capability.", "evidenceIds": [] }, { "productId": "clerky", "storyId": "automation-versioned-workflows", "verdict": "na", "quality": 0, "confidence": "medium", "rationale": "Clerky is a legal-document/formation automation service (document sets, e-signatures, filings), not a workflow/automation-builder product with versionable automations to review or roll back; the closest evidence is basic audit logging of document-set changes, not automation versioning.", "evidenceIds": [ "clerky-docs-4" ] }, { "productId": "clerky", "storyId": "board-consents", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Clerky's docs describe document-set collaboration, inviting co-founders/attorneys to review and comment in real-time, and issuing stock/options (which typically requires board approval) — these features generally support drafting and collecting sign-off on corporate paperwork online. However, no evidence explicitly names 'board consents' or 'resolutions' as a document type or confirms an approval-workflow specifically for board actions. Missing for 10: explicit mention of board consent/resolution templates, a dedicated approval/e-signature workflow for board members, and independent confirmation that board-level approvals are collected through the platform.", "evidenceIds": [ "clerky-docs-9", "clerky-docs-13", "clerky-docs-17", "clerky-docs-12", "clerky-docs-7", "clerky-comm-3" ] }, { "productId": "clerky", "storyId": "bulk-send-envelopes", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Clerky's evidence describes single document-set collaboration, invitations, and signature workflows for specific named parties (co-founders, employees, attorneys) but nothing about bulk-sending one document to many recipients at once, a feature typical of e-signature platforms like DocuSign.", "evidenceIds": [] }, { "productId": "clerky", "storyId": "compliance-calendar", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack of any compliance calendar, filing-deadline tracking, or reminder feature; Clerky's evidence covers document formation, collaboration, task assignment, and API/MCP integrations but nothing about deadline tracking or reminders.", "evidenceIds": [] }, { "productId": "clerky", "storyId": "contract-approval-workflows", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Clerky's evidence covers document generation, collaboration, task assignment, and attorney review invites, but nothing describes configurable approval workflows/routing before signature (e.g., multi-step approval chains, conditional routing rules, or sign-off gating). Collaboration/task features are not the same as an approval workflow engine.", "evidenceIds": [ "clerky-docs-7", "clerky-docs-12", "clerky-docs-13", "clerky-docs-17" ] }, { "productId": "clerky", "storyId": "contract-draft-negotiate", "verdict": "partial", "quality": 4, "confidence": "medium", "rationale": "Clerky offers real-time collaboration, attorney review/comment, customization of key terms, and full audit logging of document set changes, which supports a 'controlled workflow instead of email attachments' for its own formation/equity documents. However, there is no evidence of redlining, track-changes, or multi-round negotiation with external counterparties—Clerky's workflow is field-based data entry and e-signature for standardized startup legal docs, not general contract redlining. Missing for 10: explicit redline/track-changes tooling, version comparison, negotiation cycles with external parties, and support for arbitrary (non-template) contracts.", "evidenceIds": [ "clerky-docs-4", "clerky-docs-12", "clerky-docs-13", "clerky-docs-17", "clerky-docs-11" ] }, { "productId": "clerky", "storyId": "contract-repository-search", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Clerky is a formation/document-generation tool; evidence covers document sets, activity logs, and collaboration but nothing about a searchable repository of executed contracts with extracted key terms/metadata—no full-text search, term extraction, or metadata tagging is described anywhere in the pack.", "evidenceIds": [] }, { "productId": "clerky", "storyId": "document-generation-api", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Clerky publishes a documented Partner API with concrete lifecycle steps (create document set, GET forms with json_schema, POST values, poll state) covering document generation and population (clerky-docs-19, clerky-docs-20). However, the API currently only supports Delaware C-Corp formations, OAuth-based authentication is explicitly stated as 'coming soon' rather than live (clerky-docs-21), and 'sending' is really 'user signs on Clerky' rather than a programmatic send step, so the story is only partially realized in production. Missing for 10: live/production authentication for partners, broader document-type coverage beyond formations, and independent/hands-on evidence of a working end-to-end integration.", "evidenceIds": [ "clerky-docs-19", "clerky-docs-20", "clerky-docs-21", "clerky-probe-4" ] }, { "productId": "clerky", "storyId": "ein-tax-id", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "Clerky explicitly advertises completing and submitting IRS forms (including EIN application, a core IRS form for new companies) fully online without fax, done in-house — clerky-docs-5/15. Community evidence corroborates general ease/friction of the incorporation process but doesn't specifically dispute the EIN step. Missing for 10: independent hands-on confirmation specifically of the EIN application step (vs. general process reviews) and detail on turnaround time.", "evidenceIds": [ "clerky-docs-5", "clerky-docs-15", "clerky-comm-8" ] }, { "productId": "clerky", "storyId": "embedded-signing", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Clerky's Partner API lets a developer create a document set, render forms, and collect data inside their own product, but the docs explicitly state 'Users enter formation information in your product and sign documents on Clerky' — meaning the actual signing step happens on Clerky's own platform rather than being embedded, and OAuth authentication for partners is still listed as 'coming soon' rather than live. missing for 10: evidence of an embeddable signing widget/iframe, live partner OAuth flow, and any third-party confirmation of a working embedded integration.", "evidenceIds": [ "clerky-docs-19", "clerky-docs-20", "clerky-docs-21" ] }, { "productId": "clerky", "storyId": "equity-hiring-paperwork", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Clerky's own product docs explicitly cover hiring paperwork (offer/hiring workflows), confidentiality/IP agreements implied via founder/employee onboarding docs, and equity issuance (stock, stock options, safes, convertible notes) via a stock plan, plus attorney oversight/collaboration features for legal-ops review. Community reviews corroborate real-world use of the hiring/fundraising/maintenance packages. Missing for 10: explicit mention of confidentiality/IP agreement templates by name and independent case studies detailing legal-ops workflows specifically.", "evidenceIds": [ "clerky-docs-9", "clerky-docs-16", "clerky-docs-8", "clerky-docs-12", "clerky-comm-3" ] }, { "productId": "clerky", "storyId": "guided-questionnaires", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Clerky's docs show forms with structured fields/json_schema that collect info to fill documents (clerky-docs-19, clerky-docs-20), easy customization of key terms (clerky-docs-11), and the ability to loop in an attorney to review and comment on entered information (clerky-docs-12). However, there is no explicit evidence of a system that automatically flags specific choices as needing attorney review versus a general 'invite attorney' collaboration feature. missing for 10: explicit automated flagging/warning UI for attorney-review-needed choices, independent user account of the questionnaire flow itself, and confirmation the guided form correctly maps answers to legal documents.", "evidenceIds": [ "clerky-docs-19", "clerky-docs-20", "clerky-docs-11", "clerky-docs-12", "clerky-docs-13" ] }, { "productId": "clerky", "storyId": "incorporate-end-to-end", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Clerky is purpose-built for online Delaware incorporation, covering formation filing, customizable bylaws/legal documents, board approvals, and post-incorporation paperwork, corroborated by positive hands-on founder accounts of using it for incorporation. missing for 10: independent verification of the full end-to-end filing-to-board-approval flow (vs marketing pages), and a documented step-by-step walkthrough showing bylaws/board consent generation explicitly.", "evidenceIds": [ "clerky-docs-8", "clerky-docs-11", "clerky-docs-9", "clerky-docs-16", "clerky-comm-2", "clerky-comm-8", "clerky-comm-5" ] }, { "productId": "clerky", "storyId": "legal-template-library", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Clerky documents show a template-driven system for startup-specific legal paperwork (formation, safes/convertible notes, stock plans, hiring/equity agreements, IRS forms) that lets founders self-serve rather than hire counsel for those documents. However, the evidence never mentions NDAs, general contract templates, or company policy documents, which are explicitly named in the story. Missing for 10: evidence of NDA templates, general business agreement templates, and policy document templates beyond incorporation/equity paperwork.", "evidenceIds": [ "clerky-docs-9", "clerky-docs-16", "clerky-docs-5", "clerky-docs-11", "clerky-comm-3" ] }, { "productId": "clerky", "storyId": "openness-api-parity", "verdict": "partial", "quality": 4, "confidence": "medium", "rationale": "Clerky has a Partner API but it explicitly 'currently supports Delaware C-Corporation formations' only, a narrow subset of the 40+ products, safes, stock plans, hiring, banking integrations, and legal dashboard features described in the UI docs. OAuth authentication is also still 'coming soon,' meaning the API isn't even fully live yet, and there's no evidence of API coverage for post-formation workflows (safes, convertible notes, hiring, stock issuance, IRS filing, banking apps) that are core UI capabilities. Missing for 10: API coverage for post-incorporation products (safes, hiring, equity issuance, IRS/bank filings), live OAuth access, and evidence of parity across the 40+ advanced products.", "evidenceIds": [ "clerky-docs-19", "clerky-docs-20", "clerky-docs-21", "clerky-docs-9", "clerky-docs-2", "clerky-docs-6" ] }, { "productId": "clerky", "storyId": "openness-full-export", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No evidence of any bulk data export in open/standard formats (e.g., document download bundles, JSON/CSV exports of legal data) for users to take their data and leave; the Partner API and MCP server are designed for partner integrations/AI assistants working within Clerky, not full data portability/exit. Probes also show no llms.txt/docs export or export-oriented endpoints beyond the legal-workflow API.", "evidenceIds": [ "clerky-docs-19", "clerky-docs-21", "clerky-probe-1", "clerky-probe-2", "clerky-probe-3" ] }, { "productId": "clerky", "storyId": "openness-open-license", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Clerky is a closed-source legal SaaS product; there is no evidence of any open-source license or public source repository, and probes for open documentation/API artifacts returned 404s. Missing for 10: any open-source license, public code repository, or source availability statement.", "evidenceIds": [ "clerky-probe-1", "clerky-probe-2", "clerky-probe-3" ] }, { "productId": "clerky", "storyId": "openness-self-host", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Clerky is a SaaS legal/formation platform tied to legal filings and attorney workflows; self-hosting the core product is not a coherent capability for this category, as it depends on Clerky's own infrastructure, attorneys, and IRS/state filing pipelines.", "evidenceIds": [] }, { "productId": "clerky", "storyId": "post-incorporation-setup", "verdict": "partial", "quality": 7, "confidence": "medium", "rationale": "Clerky's docs confirm founder stock/equity issuance (clerky-docs-9, clerky-docs-16) and completing/submitting IRS forms online (clerky-docs-5, clerky-docs-15), which covers 83(b) elections, and community confirms a post-incorporation 'Maintenance' package (clerky-comm-3). However, IP assignment agreements are not explicitly named in the evidence pack, so full coverage of that specific document isn't directly confirmed. missing for 10: explicit documentation of IP assignment agreement generation, independent verification that 83(b) filings are correctly executed, and hands-on account of the full post-incorporation flow.", "evidenceIds": [ "clerky-docs-5", "clerky-docs-9", "clerky-docs-15", "clerky-docs-16", "clerky-comm-3" ] }, { "productId": "clerky", "storyId": "privacy-data-residency", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Clerky is a legal document/formation service, not infrastructure with configurable data residency; the evidence pack contains no mention of region/residency options, and this is not a fair capability to expect from this type of product (a US-focused legal filing service).", "evidenceIds": [] }, { "productId": "clerky", "storyId": "privacy-no-training", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack addresses AI training data usage, opt-out settings, or any privacy policy statement about model training; Clerky's materials focus on legal document workflows, MCP/API integration, and formation services with nothing on this axis.", "evidenceIds": [] }, { "productId": "clerky", "storyId": "privacy-retention-controls", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack addresses data retention policies, export, or deletion controls for user data within Clerky; the docs focus on formation, collaboration, and MCP/API features, none of which mention retention or deletion. Missing for 10: any documentation of data retention periods, deletion requests, or export/erasure controls.", "evidenceIds": [] }, { "productId": "clerky", "storyId": "privacy-telemetry-optout", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack addresses telemetry, usage tracking, or any opt-out mechanism for Clerky; the documentation focuses entirely on legal/document workflows with no privacy-controls content.", "evidenceIds": [] }, { "productId": "clerky", "storyId": "registered-agent-service", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence anywhere in the pack that Clerky offers registered agent services or digital mail/service-of-process scanning; its documented scope is document generation, e-signature, IRS filings, banking, and API/MCP integrations. Registered agent service is a plausible offering for a startup-formation platform, so absence of evidence yields 'none' rather than 'na'.", "evidenceIds": [] }, { "productId": "clerky", "storyId": "renewal-obligation-tracking", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Clerky is a startup legal-document formation and equity/incorporation platform, not a contract-lifecycle management tool; there is no evidence of contract renewal tracking, expiration alerts, or obligation management, and this is not the kind of capability Clerky's product category would offer.", "evidenceIds": [] }, { "productId": "clerky", "storyId": "safe-financing-docs", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Clerky's core startup product explicitly supports issuing SAFEs and convertible notes on standard forms with customizable key terms, collaborative editing, attorney review, and e-signature—removing the need to draft from scratch. Community feedback corroborates ease of use and frictionless process for founders using Clerky's paperwork workflows. Missing for 10: independent hands-on account of actually generating/signing a SAFE end-to-end and specifics on which standard SAFE variants (YC, pre/post-money) are supported.", "evidenceIds": [ "clerky-docs-9", "clerky-docs-11", "clerky-docs-12", "clerky-docs-13", "clerky-comm-7", "clerky-comm-8" ] }, { "productId": "clerky", "storyId": "send-for-esignature", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Clerky's document sets clearly involve multiple signers (collaborators, attorneys, co-founders) and a signing workflow (clerky-docs-13/17, clerky-docs-19/20), but this is signing within Clerky's own fixed legal document templates rather than a general-purpose 'send any document for signature with custom multi-recipient routing' capability. No evidence describes configurable signing order, roles, or routing logic for recipients. Missing for 10: explicit documentation of routing/sequencing controls, ability to send arbitrary documents (not just Clerky-generated ones) for signature, and independent confirmation of multi-recipient routing behavior.", "evidenceIds": [ "clerky-docs-13", "clerky-docs-17", "clerky-docs-19", "clerky-docs-20" ] }, { "productId": "clerky", "storyId": "signer-identity-verification", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence anywhere in the pack mentions signer identity verification methods like SMS, ID check, or knowledge-based authentication for document signing; Clerky's documentation focuses on formation workflows, collaboration, and audit logs, not signer verification strength.", "evidenceIds": [] }, { "productId": "clerky", "storyId": "signing-order-reminders", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence describes signing order, automatic reminders, or expiration settings for signature requests; Clerky's evidence focuses on document collaboration, workspace access, and formation workflows, not e-signature controls of this kind.", "evidenceIds": [] }, { "productId": "docusign", "storyId": "agent-drafts-routes-nda", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "docusign-docs-21", "docusign-docs-40", "docusign-docs-47", "docusign-docs-16", "docusign-docs-20", "docusign-probe-3", "docusign-intdir-6" ] }, { "productId": "docusign", "storyId": "agent-files-annual-report", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "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.", "evidenceIds": [ "docusign-docs-39", "docusign-docs-47", "docusign-docs-16", "docusign-docs-20", "docusign-docs-25", "docusign-intdir-6", "docusign-probe-3" ] }, { "productId": "docusign", "storyId": "agent-monitors-renewals", "verdict": "partial", "quality": 7, "confidence": "medium", "rationale": "Docusign's REST API and new MCP connector explicitly expose agreement status, key dates, and metadata, and let AI agents (Claude, Gemini CLI, Copilot) trigger workflow actions through IAM tools, which supports agent-driven monitoring and pre-lapse action. However, there's no explicit documentation of renewal-specific alerts/triggers or an end-to-end example of an agent proactively acting before a deadline lapses, and no independent corroboration of this MCP monitoring workflow in production. Missing for 10: explicit renewal/deadline-triggered automation examples, third-party/hands-on validation of the MCP agent acting autonomously before lapse.", "evidenceIds": [ "docusign-docs-11", "docusign-docs-12", "docusign-docs-39", "docusign-docs-47", "docusign-probe-3", "docusign-intdir-4", "docusign-intdir-6" ] }, { "productId": "docusign", "storyId": "agentic-agent-docs", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "docusign-probe-1", "docusign-probe-3", "docusign-docs-39", "docusign-docs-47", "docusign-gh-2" ] }, { "productId": "docusign", "storyId": "agentic-ai-insights", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "docusign-docs-2", "docusign-docs-20", "docusign-docs-25", "docusign-docs-28", "docusign-docs-16", "docusign-docs-33", "docusign-docs-44" ] }, { "productId": "docusign", "storyId": "agentic-autonomous-automation", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "docusign-docs-4", "docusign-docs-12", "docusign-docs-39", "docusign-probe-3", "docusign-docs-41" ] }, { "productId": "docusign", "storyId": "agentic-builtin-assistant", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Docusign ships AI-Assisted Review, AI-Assisted Summary/Q&A, and Iris-powered form conversion embedded within its products, letting users delegate agreement-analysis and drafting tasks to built-in AI features rather than a single unified conversational assistant that can be delegated arbitrary tasks. missing for 10: evidence of a general-purpose, agentic in-product assistant that can autonomously execute multi-step tasks (not just summarize/flag/draft within a specific workflow), and independent/hands-on validation of these AI features actually working as described.", "evidenceIds": [ "docusign-docs-2", "docusign-docs-20", "docusign-docs-25", "docusign-docs-28", "docusign-docs-33", "docusign-docs-16", "docusign-docs-27" ] }, { "productId": "docusign", "storyId": "agentic-headless", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "docusign-docs-21", "docusign-docs-13", "docusign-docs-40", "docusign-gh-1", "docusign-gh-2", "docusign-intdir-4", "docusign-comm-4", "docusign-comm-5" ] }, { "productId": "docusign", "storyId": "agentic-mcp-client", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "All MCP-related evidence describes Docusign functioning as an MCP *server* that other AI clients (Claude, Gemini CLI, Copilot) connect to and use — not Docusign itself consuming or plugging in external MCP servers to use their tools. There is no evidence of Docusign acting as an MCP client that ingests third-party MCP tool servers, which is what this story requires.", "evidenceIds": [ "docusign-docs-39", "docusign-intdir-4", "docusign-intdir-6", "docusign-probe-3" ] }, { "productId": "docusign", "storyId": "agentic-mcp-server", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "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.", "evidenceIds": [ "docusign-docs-39", "docusign-docs-47", "docusign-intdir-4", "docusign-intdir-6", "docusign-probe-3" ] }, { "productId": "docusign", "storyId": "agentic-nl-commands", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "docusign-docs-11", "docusign-docs-12", "docusign-docs-39", "docusign-docs-47", "docusign-intdir-4", "docusign-intdir-6", "docusign-intdir-7", "docusign-probe-3", "docusign-docs-20" ] }, { "productId": "docusign", "storyId": "agentic-official-cli", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack shows SDKs, REST APIs, an MCP server/connector, and third-party CLI pairing (Gemini CLI + Docusign MCP), but no official Docusign-branded CLI tool is documented anywhere in the evidence.", "evidenceIds": [ "docusign-intdir-4", "docusign-docs-21", "docusign-docs-40" ] }, { "productId": "docusign", "storyId": "agentic-public-api", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "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.", "evidenceIds": [ "docusign-docs-21", "docusign-docs-22", "docusign-gh-1", "docusign-gh-2", "docusign-gh-3", "docusign-docs-13", "docusign-docs-40", "docusign-comm-4", "docusign-comm-5", "docusign-probe-2" ] }, { "productId": "docusign", "storyId": "agentic-scoped-keys", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "docusign-docs-39", "docusign-docs-47", "docusign-comm-1" ] }, { "productId": "docusign", "storyId": "agentic-sdks", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "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.", "evidenceIds": [ "docusign-docs-13", "docusign-docs-40", "docusign-docs-21", "docusign-docs-22", "docusign-gh-1", "docusign-gh-3", "docusign-comm-4", "docusign-comm-5", "docusign-probe-1", "docusign-probe-2" ] }, { "productId": "docusign", "storyId": "agentic-webhooks", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "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'.", "evidenceIds": [] }, { "productId": "docusign", "storyId": "annual-report-filings", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Docusign is an e-signature/agreement management platform; filing annual reports and franchise taxes is a registered-agent/compliance-service function entirely outside its product category, so this axis does not apply.", "evidenceIds": [] }, { "productId": "docusign", "storyId": "api-interactive-docs", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "docusign-docs-21", "docusign-docs-22", "docusign-gh-1", "docusign-gh-2", "docusign-probe-1", "docusign-probe-2" ] }, { "productId": "docusign", "storyId": "api-machine-spec", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "docusign-gh-1", "docusign-gh-2", "docusign-gh-3", "docusign-docs-21", "docusign-docs-22", "docusign-probe-2" ] }, { "productId": "docusign", "storyId": "api-sandbox", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "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.", "evidenceIds": [] }, { "productId": "docusign", "storyId": "api-versioning-policy", "verdict": "disputed", "quality": 3, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "docusign-comm-1", "docusign-comm-5", "docusign-gh-1", "docusign-docs-21" ] }, { "productId": "docusign", "storyId": "audit-trail-certificate", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [] }, { "productId": "docusign", "storyId": "automation-bulk-operations", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "docusign-docs-21", "docusign-docs-13", "docusign-docs-11", "docusign-docs-12", "docusign-docs-47" ] }, { "productId": "docusign", "storyId": "automation-rules-engine", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "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.", "evidenceIds": [ "docusign-docs-4", "docusign-docs-17", "docusign-docs-19", "docusign-docs-26", "docusign-docs-12", "docusign-docs-47", "docusign-docs-41" ] }, { "productId": "docusign", "storyId": "automation-scheduled-jobs", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Docusign documents configurable workflows, templates, MCP/API integrations, and third-party connectors (Zapier-style), so a buyer could reasonably ask about recurring/scheduled job automation, but no evidence pack item describes any cron-like scheduler, recurring trigger, or automated recurring workflow execution capability.", "evidenceIds": [] }, { "productId": "docusign", "storyId": "automation-versioned-workflows", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No evidence describes any version history, review/approval workflow, or rollback mechanism for automations (workflows, templates, or MCP-triggered actions); Docusign's docs cover building and configuring workflows/templates but not versioning or reverting them.", "evidenceIds": [] }, { "productId": "docusign", "storyId": "board-consents", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "docusign-docs-4", "docusign-docs-6", "docusign-docs-7", "docusign-docs-9", "docusign-docs-36", "docusign-comm-5" ] }, { "productId": "docusign", "storyId": "bulk-send-envelopes", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [] }, { "productId": "docusign", "storyId": "compliance-calendar", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "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.", "evidenceIds": [] }, { "productId": "docusign", "storyId": "contract-approval-workflows", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Docusign explicitly markets configurable workflows (docusign-docs-4), CLM drag-and-drop process design (docusign-docs-17), and delegated signing (docusign-docs-9), and integrates with systems like Salesforce for auto-populating agreements (docusign-docs-24), which together support pre-signature approval routing. However, the evidence lacks detail on how approval-specific routing (multi-stage sign-off before signature) is configured, no independent/hands-on validation of workflow configuration exists, and community evidence focuses on embedded signing/security issues rather than approval workflows. Missing for 10: concrete documentation or demo of approval-stage routing logic, independent corroboration of workflow configurability, and detail on approval conditions/rules engine.", "evidenceIds": [ "docusign-docs-4", "docusign-docs-17", "docusign-docs-9", "docusign-docs-24", "docusign-docs-41" ] }, { "productId": "docusign", "storyId": "contract-draft-negotiate", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Docusign CLM and AI-Assisted Review offer redlining, playbook-based suggested edits, and MS Word integration for contract negotiation, moving beyond email attachments, and web forms/templates support structured drafting workflows. However, evidence is entirely vendor-sourced marketing copy with no independent hands-on account of a full negotiation/redline cycle, and community threads focus on unrelated integration/security complaints rather than corroborating the CLM/redlining workflow. Missing for 10: independent or hands-on verification of the redline/negotiation workflow in practice, detail on multi-party version control during negotiation, and confirmation that AI-Assisted Review's Word integration handles full negotiation cycles reliably.", "evidenceIds": [ "docusign-docs-16", "docusign-docs-17", "docusign-docs-20", "docusign-docs-25", "docusign-docs-28", "docusign-docs-41", "docusign-docs-44" ] }, { "productId": "docusign", "storyId": "contract-repository-search", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Docusign's IAM/CLM platform explicitly markets a searchable agreement repository ('Securely store and access all your agreements in one place', 'Find, analyze, and act on agreements powered by AI') plus metadata/key-term extraction via AI-assisted review and MCP connector features ('Retrieve agreement context and metadata', AI flags clauses and suggests terms). This directly matches the legal-ops story of a searchable repository with extracted key terms and metadata. missing for 10: independent/hands-on corroboration of the repository search and metadata-extraction UX, and detail on extraction accuracy or breadth of metadata fields captured", "evidenceIds": [ "docusign-docs-36", "docusign-docs-46", "docusign-docs-45", "docusign-docs-11", "docusign-docs-16", "docusign-docs-20", "docusign-docs-44" ] }, { "productId": "docusign", "storyId": "document-generation-api", "verdict": "disputed", "quality": 6, "confidence": "medium", "rationale": "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).", "evidenceIds": [ "docusign-docs-21", "docusign-docs-22", "docusign-gh-1", "docusign-docs-13", "docusign-comm-4", "docusign-comm-5", "docusign-comm-1", "docusign-comm-3", "docusign-comm-6", "docusign-probe-2" ] }, { "productId": "docusign", "storyId": "ein-tax-id", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Docusign is an e-signature/agreement management platform; obtaining a federal EIN is a government registration task entirely outside its product category, not an axis this kind of product could plausibly cover.", "evidenceIds": [] }, { "productId": "docusign", "storyId": "embedded-signing", "verdict": "disputed", "quality": 6, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "docusign-docs-43", "docusign-docs-21", "docusign-comm-1", "docusign-comm-4", "docusign-comm-5", "docusign-comm-3" ] }, { "productId": "docusign", "storyId": "equity-hiring-paperwork", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "docusign-docs-6", "docusign-docs-7", "docusign-docs-4", "docusign-docs-5", "docusign-docs-49" ] }, { "productId": "docusign", "storyId": "guided-questionnaires", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Docusign is an e-signature/agreement management platform; it does not provide guided legal questionnaires that draft documents and flag items for attorney review — that is a legal-document-generation product category (e.g., Rocket Lawyer/LegalZoom-style tools), not what Docusign offers. Its templates and CLM/AI review features operate on already-drafted agreements rather than interviewing a founder to fill in a document from scratch, so this axis is a category mismatch.", "evidenceIds": [] }, { "productId": "docusign", "storyId": "incorporate-end-to-end", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Docusign is an e-signature/agreement management platform, not a legal/incorporation service; it can be used to sign documents but has no filing, registered agent, or legal formation capability for Delaware incorporation, so this axis is a category error for this product type.", "evidenceIds": [] }, { "productId": "docusign", "storyId": "legal-template-library", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Docusign's evidence describes reusable/custom templates that users build and share within their own workflows (e.g., docusign-docs-6, docusign-docs-7, docusign-docs-34), but there is no mention of a pre-built, vetted library of standard legal documents (NDAs, agreements, policies) that a founder could use in place of counsel. Docusign's template features are about reusing your own document setup, not sourcing vetted legal content.", "evidenceIds": [ "docusign-docs-6", "docusign-docs-7", "docusign-docs-34" ] }, { "productId": "docusign", "storyId": "openness-api-parity", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "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.", "evidenceIds": [ "docusign-docs-21", "docusign-gh-1", "docusign-docs-47", "docusign-probe-3", "docusign-comm-1", "docusign-docs-17", "docusign-docs-18" ] }, { "productId": "docusign", "storyId": "openness-full-export", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "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.", "evidenceIds": [] }, { "productId": "docusign", "storyId": "openness-open-license", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Docusign is a closed-source commercial SaaS platform; while it publishes SDKs, OpenAPI specs, and an MCP connector, none of the evidence indicates the core product source is released under an open license, and its client libraries/specs are auxiliary developer tools rather than the product's source.", "evidenceIds": [] }, { "productId": "docusign", "storyId": "openness-self-host", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Docusign is a SaaS e-signature/agreement platform with no self-hosted deployment option; self-hosting is a category error for this kind of cloud service, not a missing feature.", "evidenceIds": [] }, { "productId": "docusign", "storyId": "post-incorporation-setup", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Docusign is an e-signature/agreement platform, not a legal document generation or incorporation-workflow tool; it does not produce or manage the substantive legal content of founder stock purchase agreements, IP assignment agreements, or 83(b) elections — it can only be used to sign documents someone else prepared. Post-incorporation legal paperwork generation is outside its product category (wrong axis), so this is a category error rather than a missing feature.", "evidenceIds": [] }, { "productId": "docusign", "storyId": "privacy-data-residency", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "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.", "evidenceIds": [] }, { "productId": "docusign", "storyId": "privacy-no-training", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack contains no mention of AI training data opt-out, data usage policies, or privacy controls specific to AI model training; only unrelated feature and integration descriptions plus community complaints about API issues and phishing. Missing for 10: any documented opt-out/consent mechanism for AI training, privacy policy language on data usage, or admin controls to restrict data use for model training.", "evidenceIds": [] }, { "productId": "docusign", "storyId": "privacy-retention-controls", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "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.", "evidenceIds": [] }, { "productId": "docusign", "storyId": "privacy-telemetry-optout", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack addresses telemetry/usage-tracking opt-out settings for Docusign or its AI features; the pack covers product features, integrations, and unrelated community complaints. This axis applies to any AI-native product handling user data, but no documentation of an opt-out mechanism exists.", "evidenceIds": [] }, { "productId": "docusign", "storyId": "registered-agent-service", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Docusign is an e-signature/agreement platform, not a registered agent service; acting as a registered agent for legal mail/service of process is an entirely different regulated business function outside its product category.", "evidenceIds": [] }, { "productId": "docusign", "storyId": "renewal-obligation-tracking", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "Docusign's CLM and IAM materials mention querying 'agreement status and key dates' and general agreement analysis, but no evidence describes automated renewal/expiration tracking or alerting for obligations. missing for 10: explicit renewal/expiration tracking feature, automatic alert/notification mechanism, obligation management documentation.", "evidenceIds": [ "docusign-docs-47", "docusign-docs-45", "docusign-docs-17" ] }, { "productId": "docusign", "storyId": "safe-financing-docs", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Docusign is an e-signature/agreement management platform, not a legal-document drafting tool for equity instruments like SAFEs or convertible notes; generating standard-terms legal instruments from scratch is outside its product category (it supports templates and e-signing of already-drafted documents, not legal-content generation for specific fundraising instruments).", "evidenceIds": [] }, { "productId": "docusign", "storyId": "send-for-esignature", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "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).", "evidenceIds": [ "docusign-docs-1", "docusign-docs-4", "docusign-docs-9", "docusign-docs-21", "docusign-comm-4", "docusign-comm-5" ] }, { "productId": "docusign", "storyId": "signer-identity-verification", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "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.", "evidenceIds": [ "docusign-docs-14", "docusign-docs-15", "docusign-docs-26", "docusign-docs-30", "docusign-docs-10" ] }, { "productId": "docusign", "storyId": "signing-order-reminders", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "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.", "evidenceIds": [ "docusign-docs-4", "docusign-docs-9" ] }, { "productId": "firstbase", "storyId": "agent-drafts-routes-nda", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Firstbase is a company-formation/back-office compliance platform, not a document-automation or e-signature product; there is no API/MCP-driven NDA drafting or signature routing capability in scope for this product category.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "agent-files-annual-report", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Firstbase offers a human-facing registered-agent and compliance dashboard, but there is no evidence of any AI-agent API, automation hooks, or delegation workflow that would let an AI agent prepare filings with minimal human input; probes even confirm no llms.txt or OpenAPI endpoint exists for programmatic/agentic access.", "evidenceIds": [ "firstbase-docs-7", "firstbase-docs-14", "firstbase-probe-1", "firstbase-probe-2" ] }, { "productId": "firstbase", "storyId": "agent-monitors-renewals", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any public API for agents to consume deadline/contract data; probes confirm no OpenAPI spec or llms.txt exists, and deadline tracking is described only as a manual dashboard feature, not an API-accessible capability. missing for 10: public API/webhook for deadlines, agent-actionable endpoints, any documentation of programmatic access.", "evidenceIds": [ "firstbase-probe-1", "firstbase-probe-2", "firstbase-docs-7", "firstbase-docs-14" ] }, { "productId": "firstbase", "storyId": "agentic-agent-docs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Firstbase is a business-formation/back-office SaaS, and while agent-oriented docs are a fair axis for any modern SaaS, a direct probe shows llms.txt returns 404 and no other agent-oriented documentation format is evidenced.", "evidenceIds": [ "firstbase-probe-1" ] }, { "productId": "firstbase", "storyId": "agentic-ai-insights", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of AI-generated insights, analytics, or suggestions within Firstbase's product; the pack only describes compliance, banking, mail, and accounting services delivered by humans or manual processes.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "agentic-autonomous-automation", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Firstbase is a company-formation/back-office service; nothing in the evidence describes AI-agent automation building, scheduling, or autonomous background workflows for users. No API, no llms.txt, no automation builder is documented — probes for openapi/llms.txt both 404.", "evidenceIds": [ "firstbase-probe-1", "firstbase-probe-2" ] }, { "productId": "firstbase", "storyId": "agentic-builtin-assistant", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Firstbase is a business-formation/back-office compliance service, not an AI product; there is no evidence of any built-in AI assistant feature, so this axis is a category error for this product type.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "agentic-headless", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Firstbase is a company-formation/back-office service (registered agent, accounting, banking, tax), not a developer tool or agent-driven product with a CLI/API surface meant for headless or CI automation — this axis is a category error for this product type.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "agentic-mcp-client", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Firstbase is a business incorporation/back-office service, not an AI agent or platform with MCP integration; plugging MCP servers into it is a category error for this product type.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "agentic-mcp-server", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Firstbase is a business-incorporation/back-office SaaS, not an AI agent or agentic tool; MCP server connectivity is not a relevant axis for this category, and no evidence suggests otherwise.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "agentic-nl-commands", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any natural-language command interface, chat-based control, or AI-native operation; probes for llms.txt and OpenAPI both failed, and all docs describe a traditional web-form/dashboard business-services product.", "evidenceIds": [ "firstbase-probe-1", "firstbase-probe-2" ] }, { "productId": "firstbase", "storyId": "agentic-official-cli", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any official CLI tool; Firstbase is a business incorporation/back-office platform with no mention of developer tooling or CLI. Missing for 10: any CLI documentation, package, or reference whatsoever.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "agentic-public-api", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of a documented public API; probes for llms.txt and OpenAPI/Swagger specs all returned 404, and no docs mention API access for AI-native or programmatic use.", "evidenceIds": [ "firstbase-probe-1", "firstbase-probe-2" ] }, { "productId": "firstbase", "storyId": "agentic-scoped-keys", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Firstbase is a business incorporation/back-office service (registered agent, banking, payroll, accounting), not an API/agent platform; scoped API credential issuance for agents is a category mismatch for this product.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "agentic-sdks", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Firstbase is a business incorporation/back-office service with no evidence of any SDK offering; probes for llms.txt and OpenAPI specs both returned 404s, and no docs mention SDKs at all.", "evidenceIds": [ "firstbase-probe-1", "firstbase-probe-2" ] }, { "productId": "firstbase", "storyId": "agentic-webhooks", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any webhook subscription capability, API, or event system in Firstbase's documentation; probes for OpenAPI/llms.txt both returned 404, and no docs mention webhooks at all.", "evidenceIds": [ "firstbase-probe-1", "firstbase-probe-2" ] }, { "productId": "firstbase", "storyId": "annual-report-filings", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Firstbase documents a compliance dashboard showing per-state deadlines and required actions, registered agent service, and tax filing (extension filing, R&D eligibility) — covering the general mechanics of annual report/franchise tax compliance. However, evidence doesn't explicitly confirm automated annual report filing itself (vs. just deadline tracking), and a community report confirms users still must independently handle annual state filings/fees themselves. Missing for 10: explicit confirmation that Firstbase files annual reports/franchise tax on the founder's behalf (not just tracks deadlines), and independent verification of on-time filing success.", "evidenceIds": [ "firstbase-docs-7", "firstbase-docs-14", "firstbase-docs-8", "firstbase-docs-10", "firstbase-comm-1" ] }, { "productId": "firstbase", "storyId": "api-interactive-docs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Firstbase is a business-formation/back-office platform; no evidence of any API reference, interactive docs, or runnable examples—probes for llms.txt and OpenAPI specs both returned 404.", "evidenceIds": [ "firstbase-probe-1", "firstbase-probe-2" ] }, { "productId": "firstbase", "storyId": "api-machine-spec", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Probes explicitly show no OpenAPI/swagger spec exists at any expected location, and no docs mention a public API spec.", "evidenceIds": [ "firstbase-probe-2" ] }, { "productId": "firstbase", "storyId": "api-sandbox", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Firstbase is a business incorporation/back-office platform, not a developer/API product with sandbox testing environments; sandbox-vs-production data testing is a category mismatch here.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "api-versioning-policy", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any public API, versioning scheme, or deprecation policy; probes for llms.txt and OpenAPI specs both returned 404, and Firstbase's docs focus entirely on incorporation/compliance services, not developer APIs.", "evidenceIds": [ "firstbase-probe-1", "firstbase-probe-2" ] }, { "productId": "firstbase", "storyId": "audit-trail-certificate", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Firstbase is a company formation/back-office compliance platform, not an e-signature or document-execution tool; the evidence contains nothing about signing documents, audit trails, or completion certificates, so this axis is a category error for this product.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "automation-bulk-operations", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any bulk/batch operations capability across items; Firstbase is a company formation/back-office service with no API or bulk automation features documented, and probes confirm no API/llms.txt exists.", "evidenceIds": [ "firstbase-probe-1", "firstbase-probe-2" ] }, { "productId": "firstbase", "storyId": "automation-rules-engine", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Firstbase is a company-formation/back-office compliance service, not an automation/rules-engine platform; defining event-triggered automation rules is outside its product category.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "automation-scheduled-jobs", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Firstbase is a business incorporation/compliance back-office service, not an automation/workflow platform; scheduling recurring jobs is not a relevant capability for this product category.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "automation-versioned-workflows", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Firstbase is a business incorporation/compliance/back-office service, not an automation or workflow-building tool; there is no concept of automations to version, review, or roll back.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "board-consents", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Firstbase is a company formation/back-office compliance platform (registered agent, banking, accounting, tax); nothing in its evidence pack relates to preparing board consents/resolutions or collecting e-signature approvals, which is a cap-table/equity-management axis outside its category.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "bulk-send-envelopes", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Firstbase is a company incorporation/compliance/back-office platform, not an e-signature or document-distribution product; bulk-sending documents to recipients is outside its category.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "compliance-calendar", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Firstbase's registered-agent/compliance dashboard gives an overview of state-by-state status and upcoming deadlines (firstbase-docs-7, firstbase-docs-14), which is the closest match to a compliance calendar, but there's no evidence of proactive reminder/notification mechanisms (email/SMS alerts) before deadlines. missing for 10: explicit reminder/notification feature description, evidence of calendar/alert scheduling, independent confirmation the dashboard surfaces deadlines accurately.", "evidenceIds": [ "firstbase-docs-7", "firstbase-docs-14", "firstbase-docs-9" ] }, { "productId": "firstbase", "storyId": "contract-approval-workflows", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Firstbase is a company incorporation/back-office platform (registered agent, banking, accounting, payroll, tax); it has no contract-lifecycle or approval-workflow functionality in its product category, so this axis is a category error.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "contract-draft-negotiate", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Firstbase is a company-formation/back-office platform (registered agent, banking, payroll, accounting) with no contract-lifecycle, drafting, or redlining features in evidence — this axis is a category error for this product type.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "contract-repository-search", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Firstbase is a company formation/back-office compliance platform (registered agent, banking, payroll, tax, mailroom); it has no contract-lifecycle or document repository functionality in evidence. This is a category mismatch, not a missing feature.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "document-generation-api", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of a documented API for generating, populating, or sending legal documents; probes for OpenAPI/llms.txt endpoints returned 404s, and all docs describe manual/back-office services, not developer APIs.", "evidenceIds": [ "firstbase-probe-1", "firstbase-probe-2" ] }, { "productId": "firstbase", "storyId": "ein-tax-id", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "The evidence pack covers registered agent, banking, payroll, accounting, and mailroom services, but no citation explicitly states Firstbase files or obtains a federal EIN for the founder; the only EIN reference (docs-16) is about opening a bank account 'without an EIN', not about Firstbase obtaining one. Missing for 10: explicit documentation of an EIN application/filing service and any confirmation of turnaround time or IRS interaction.", "evidenceIds": [ "firstbase-docs-16" ] }, { "productId": "firstbase", "storyId": "embedded-signing", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Firstbase is a company incorporation/back-office compliance platform, not an e-signature/embedding SDK product; the evidence pack shows no signing or embeddable UI capability at all, making this axis a category error for this product type.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "equity-hiring-paperwork", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Evidence covers incorporation, registered agent, banking, payroll registration, accounting, and tax filing, but nothing about offer letters, confidentiality/IP agreements, or option/equity grant paperwork for hiring.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "guided-questionnaires", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Evidence shows Firstbase handles incorporation, registered agent, banking, accounting, and payroll services, but there is no mention of guided questionnaires that fill in legal documents or flag choices needing attorney review — missing for 10: any documented questionnaire/document-assembly workflow, any attorney-review flagging feature, any templates library.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "incorporate-end-to-end", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Firstbase clearly offers a company-formation product (evidenced by the /incorporate-your-company URL and related account/banking setup features), and a community anecdote confirms users have used it to set up a US entity. However, no evidence explicitly describes Delaware-specific filing, bylaws generation, or initial board approval workflows. Missing for 10: explicit documentation of Delaware filing steps, bylaws templates/generation, and board consent/approval process.", "evidenceIds": [ "firstbase-docs-16", "firstbase-comm-1" ] }, { "productId": "firstbase", "storyId": "legal-template-library", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No evidence of a legal templates library (NDAs, agreements, policies) anywhere in Firstbase's docs; evidence covers incorporation, registered agent, accounting, banking, payroll, and tax services only, not standardized legal document templates.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "openness-api-parity", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any public API at all — probes for llms.txt and OpenAPI/Swagger endpoints returned 404, and no docs mention an API for parity with UI features.", "evidenceIds": [ "firstbase-probe-1", "firstbase-probe-2" ] }, { "productId": "firstbase", "storyId": "openness-full-export", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any data export functionality in open formats; Firstbase is a business incorporation/back-office service with no documented export/portability feature, and probes for llms.txt and OpenAPI both 404.", "evidenceIds": [ "firstbase-probe-1", "firstbase-probe-2" ] }, { "productId": "firstbase", "storyId": "openness-open-license", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Firstbase is a company-incorporation/back-office SaaS, not open-source software; there is no source code to read under any license, so this axis is a category error for this product.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "openness-self-host", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Firstbase is a SaaS business-formation/back-office service, not open-source or deployable software; self-hosting is not a coherent concept for this product category.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "post-incorporation-setup", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack mentions founder stock purchase agreements, IP assignment agreements, or 83(b) election paperwork — Firstbase's documented offerings focus on registered agent, compliance dashboard, banking, accounting, and payroll services instead.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "privacy-data-residency", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Firstbase is a business incorporation/compliance platform, not a data storage or AI product; data residency/region selection is a category error for this product type.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "privacy-no-training", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Firstbase is a company incorporation/back-office service, not an AI model or AI-data product; AI training-data opt-out is not a relevant axis for this product category.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "privacy-retention-controls", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Firstbase is a company-formation/back-office platform; none of the evidence addresses AI data retention, data deletion controls, or privacy settings for AI-native use of user data. Absence of any mention of data retention/deletion policy means this applicable axis is unmet.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "privacy-telemetry-optout", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Firstbase is a business incorporation/back-office service, not an AI tool or SDK with telemetry collection relevant to AI-native users; this privacy axis about opting out of telemetry doesn't apply to this product category.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "registered-agent-service", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Firstbase explicitly offers a Registered Agent service with compliance dashboard tracking deadlines/state requirements, and a virtual mailroom that scans mail into PDFs, which together cover the registered-agent-plus-digital-mail story. Missing for 10: explicit mention of 'service of process' handling, independent/hands-on confirmation of the registered agent mail-scanning workflow, and any user testimonial specifically validating this feature.", "evidenceIds": [ "firstbase-docs-1", "firstbase-docs-7", "firstbase-docs-14", "firstbase-docs-18" ] }, { "productId": "firstbase", "storyId": "renewal-obligation-tracking", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Firstbase is a company formation/back-office compliance platform (registered agent, accounting, banking, tax), not a contract-lifecycle management tool; there is no evidence of contract tracking, renewal alerts, or obligation management, and this axis is a category mismatch for the product's purpose.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "safe-financing-docs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Evidence covers incorporation, registered agent, banking, payroll, accounting, and tax services but contains no mention of SAFEs, convertible notes, or equity fundraising document generation.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "send-for-esignature", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack mentions e-signature functionality, document routing, or multi-recipient signing workflows; Firstbase's evidence covers incorporation, compliance, banking, accounting, and mail services only.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "signer-identity-verification", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Firstbase is a business incorporation/compliance/back-office platform, not a document e-signature or identity-verification product; signer verification (SMS, ID check, KBA) is not a relevant axis for this product category.", "evidenceIds": [] }, { "productId": "firstbase", "storyId": "signing-order-reminders", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Firstbase is a company incorporation/compliance/back-office platform, not an e-signature product; signing order, reminders, and expirations on signature requests are outside its category entirely.", "evidenceIds": [] }, { "productId": "ironclad", "storyId": "agent-drafts-routes-nda", "verdict": "partial", "quality": 4, "confidence": "medium", "rationale": "Ironclad's Public API supports creating records from templates, launching workflows, and retrieving/interacting with workflows and contract data (ironclad-docs-2,5,13,23), which could technically support an agent drafting and routing an NDA end-to-end. However there is no evidence of an official MCP server, no explicit NDA-drafting example, and the docs note that approval/signature policies are handled by the platform rather than fully exposed for programmatic completion (ironclad-docs-15). Missing for 10: official MCP server, concrete NDA-draft-to-signature API walkthrough, independent confirmation of full automation without manual signature steps.", "evidenceIds": [ "ironclad-docs-2", "ironclad-docs-5", "ironclad-docs-13", "ironclad-docs-15", "ironclad-docs-23", "ironclad-probe-3" ] }, { "productId": "ironclad", "storyId": "agent-files-annual-report", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Ironclad's evidence covers APIs, workflows, and webhooks for contract lifecycle automation, but nothing describes an agent autonomously preparing an annual report or compliance filing end-to-end with minimal human input; 'Ironclad AI' references are generic marketing without this specific capability.", "evidenceIds": [ "ironclad-docs-12", "ironclad-docs-24", "ironclad-docs-1", "ironclad-docs-5" ] }, { "productId": "ironclad", "storyId": "agent-monitors-renewals", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Ironclad exposes a Records API, Workflows API, and webhooks that could let an external agent poll contract data or receive event notifications and then trigger workflow actions via the API, which is the raw plumbing needed for automated renewal/deadline monitoring. However, there is no explicit documentation of a renewal-date or deadline field/endpoint, no webhook event specifically for upcoming expirations, and no mention of an agent-oriented monitoring pattern. Missing for 10: explicit renewal/deadline tracking endpoints or webhook events, documented example of automated pre-lapse action, independent/hands-on confirmation that this workflow works in practice.", "evidenceIds": [ "ironclad-docs-2", "ironclad-docs-4", "ironclad-docs-13", "ironclad-docs-20", "ironclad-docs-15" ] }, { "productId": "ironclad", "storyId": "agentic-agent-docs", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "Direct probe evidence confirms Ironclad hosts a live llms.txt at the developer docs root and serves markdown-formatted docs pages (e.g. getting-started.md), which are exactly the agent-oriented doc formats an AI agent could point to. Missing for 10: no independent third-party confirmation of agents actually consuming these docs successfully in practice.", "evidenceIds": [ "ironclad-probe-1", "ironclad-probe-2", "ironclad-docs-1" ] }, { "productId": "ironclad", "storyId": "agentic-ai-insights", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Ironclad has a dedicated 'Ironclad AI' product page marketed as 'A New Era of Contract Intelligence,' implying AI-driven insights over contract data, but the evidence pack contains only page titles/taglines with no detail on what specific insights, suggestions, or analytics are actually generated or how a user interacts with them. Missing for 10: concrete feature descriptions (e.g., risk analysis, clause suggestions, obligation extraction), first-party documentation of AI capabilities, and independent/hands-on corroboration of the AI features working as described.", "evidenceIds": [ "ironclad-docs-12", "ironclad-docs-24" ] }, { "productId": "ironclad", "storyId": "agentic-autonomous-automation", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Ironclad's API and webhooks allow workflows to be triggered and events to fire automatically in the background (e.g., launching workflows via API, webhooks posting on contract events, integrations that can 'automatically block or push forward approvals'), which supports building autonomous automations. However, this requires custom integration/dev work rather than a native no-code 'set up an automation' feature aimed at AI-native users, and there's no evidence of an agent-oriented automation builder or scheduler. Missing for 10: a first-party no-code automation/agent builder, evidence of AI-driven autonomous triggers, and independent confirmation these automations run reliably unattended.", "evidenceIds": [ "ironclad-docs-4", "ironclad-docs-5", "ironclad-docs-20", "ironclad-docs-15", "ironclad-docs-8" ] }, { "productId": "ironclad", "storyId": "agentic-builtin-assistant", "verdict": "partial", "quality": 2, "confidence": "low", "rationale": "Ironclad has a dedicated 'Ironclad AI' product page referencing 'contract intelligence,' suggesting some built-in AI capability, but the evidence pack contains only marketing taglines with no detail on what tasks can be delegated to an assistant, how it's invoked, or its scope. Missing for 10: description of assistant task delegation, concrete feature list, hands-on or independent corroboration of AI assistant functionality.", "evidenceIds": [ "ironclad-docs-12", "ironclad-docs-24" ] }, { "productId": "ironclad", "storyId": "agentic-headless", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Ironclad exposes a REST API with OAuth bearer tokens, webhooks, and endpoints to launch workflows, trigger exports, and manage records — all of which can be scripted/automated without the UI, supporting headless-style automation. However there is no CLI, no explicit CI/CD integration examples, and workflow launch still requires a pre-published design from the in-app Workflow Designer, limiting full headless autonomy. Missing for 10: dedicated CLI or SDK for CI pipelines, explicit CI/CD examples, and evidence that workflow publishing itself can be done headlessly.", "evidenceIds": [ "ironclad-docs-1", "ironclad-docs-3", "ironclad-docs-4", "ironclad-docs-5", "ironclad-docs-7", "ironclad-docs-8", "ironclad-docs-13" ] }, { "productId": "ironclad", "storyId": "agentic-mcp-client", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Ironclad is a contract lifecycle management SaaS product, not an AI agent client; there is no mention of MCP server integration in any evidence, and the product's own AI features are not framed as an agent capable of consuming external MCP tools. This axis applies to agent-type products or platforms with an MCP ecosystem story, but no such angle exists here — the evidence only covers REST/webhook APIs and OAuth for traditional integrations.", "evidenceIds": [ "ironclad-docs-1", "ironclad-docs-15", "ironclad-docs-20" ] }, { "productId": "ironclad", "storyId": "agentic-mcp-server", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Ironclad is not an AI agent itself, so publishing an official MCP server is a plausible, applicable axis, but no evidence pack item mentions MCP at all—only REST API, webhooks, and OAuth are documented.", "evidenceIds": [ "ironclad-docs-1", "ironclad-docs-2", "ironclad-docs-3", "ironclad-probe-3" ] }, { "productId": "ironclad", "storyId": "agentic-nl-commands", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows Ironclad offers APIs, webhooks, and a no-code workflow builder, but nothing indicates a natural-language command interface for operating the product; the 'Ironclad AI' page is only a marketing teaser with no described NL capability.", "evidenceIds": [ "ironclad-docs-12", "ironclad-docs-24", "ironclad-docs-1" ] }, { "productId": "ironclad", "storyId": "agentic-official-cli", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Ironclad is a contract lifecycle management SaaS product, not a coding/agent tool; an official CLI for AI-native workflows is not a fair expectation for this product category, and evidence focuses only on REST APIs, webhooks, and web app features.", "evidenceIds": [] }, { "productId": "ironclad", "storyId": "agentic-public-api", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Ironclad ships a documented public REST API (Records, Workflows, Records) with OAuth2 authentication, webhooks, and detailed guides for launching workflows, exports, and embedding clickwraps, clearly enabling programmatic/agentic control of contracting processes. missing for 10: no discoverable OpenAPI/Swagger spec (all candidate paths 404), and no independent/hands-on developer corroboration beyond first-party docs.", "evidenceIds": [ "ironclad-docs-1", "ironclad-docs-2", "ironclad-docs-3", "ironclad-docs-4", "ironclad-docs-13", "ironclad-docs-20", "ironclad-docs-21", "ironclad-probe-3" ] }, { "productId": "ironclad", "storyId": "agentic-scoped-keys", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Ironclad's docs confirm OAuth 2.0 bearer token authentication for its API, but there is no evidence of scoped or least-privilege credential issuance (e.g., configurable permission scopes, role-based API keys, or agent-specific credential grants). The axis applies since an API platform could plausibly offer this, but no supporting evidence exists.", "evidenceIds": [ "ironclad-docs-3" ] }, { "productId": "ironclad", "storyId": "agentic-sdks", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Ironclad documents a REST API (Records, Workflows, webhooks, OAuth2) but the evidence pack contains no mention of official SDKs or client libraries in any language, and an OpenAPI spec probe returned 404s across all standard paths.", "evidenceIds": [ "ironclad-docs-1", "ironclad-docs-2", "ironclad-docs-3", "ironclad-docs-13", "ironclad-probe-3" ] }, { "productId": "ironclad", "storyId": "agentic-webhooks", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Ironclad's developer docs explicitly document webhooks that POST to a user-specified URL when events occur, directly supporting event subscription. Missing for 10: details on event types/filtering, payload schema, retry/security (signature verification) documentation, and independent/hands-on confirmation of reliability.", "evidenceIds": [ "ironclad-docs-4" ] }, { "productId": "ironclad", "storyId": "annual-report-filings", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Ironclad is a contract lifecycle management platform (creation, signing, storage, workflows) — it has no relationship to filing state annual reports or franchise taxes, which is a registered-agent/compliance-filing function outside its product category.", "evidenceIds": [] }, { "productId": "ironclad", "storyId": "api-interactive-docs", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Ironclad publishes a standard API reference (getting-started, authentication, webhooks, workflows) but nothing in the evidence indicates an interactive console or runnable code examples; a probe for an OpenAPI/Swagger spec (which typically powers interactive 'try it' consoles) returned 404 on all candidate paths, suggesting no such tooling exists.", "evidenceIds": [ "ironclad-docs-2", "ironclad-docs-3", "ironclad-docs-4", "ironclad-probe-3" ] }, { "productId": "ironclad", "storyId": "api-machine-spec", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Ironclad has extensive API documentation (Records, Workflows, Webhooks) but a direct probe of common OpenAPI spec locations returned 404 for all candidates, and no evidence pack item shows a downloadable machine-readable spec file. missing for 10: an actual OpenAPI/Swagger JSON or YAML file accessible for download, any documented endpoint serving the spec.", "evidenceIds": [ "ironclad-probe-3" ] }, { "productId": "ironclad", "storyId": "api-sandbox", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of a sandbox/test environment, staging API, or separate test credentials distinct from production data; the docs cover OAuth, webhooks, and API objects but never mention a sandbox mode.", "evidenceIds": [] }, { "productId": "ironclad", "storyId": "api-versioning-policy", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence shows a documented REST API (Records, Workflows, Webhooks) but no mention of API versioning scheme or a documented deprecation policy anywhere in the docs pack, and OpenAPI spec probes all 404. missing for 10: explicit API version numbering, changelog/release notes, deprecation policy or sunset timeline documentation.", "evidenceIds": [ "ironclad-docs-2", "ironclad-docs-13", "ironclad-probe-3" ] }, { "productId": "ironclad", "storyId": "audit-trail-certificate", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Ironclad is a CLM/e-signature platform where a tamper-evident audit trail and completion certificate would be a natural expected capability, but the evidence pack contains no mention of audit trails, certificates of completion, or tamper-evidence for signed documents—only generic pages about signing, storing, and API access.", "evidenceIds": [ "ironclad-docs-10", "ironclad-docs-19", "ironclad-docs-11" ] }, { "productId": "ironclad", "storyId": "automation-bulk-operations", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Ironclad's Records/Workflows APIs allow retrieving, creating, and updating records/workflows programmatically, which enables scripted bulk operations across many contracts/records, and data-export jobs support bulk data retrieval. However, there is no explicit documentation of a native bulk/batch endpoint, rate-limit guidance for bulk calls, or first-party bulk-operation UI/API designed for AI-native agents. Missing for 10: dedicated bulk/batch API endpoints, documented pagination/batching best practices for large-scale operations, and independent evidence of successful bulk automation at scale.", "evidenceIds": [ "ironclad-docs-2", "ironclad-docs-13", "ironclad-docs-7", "ironclad-docs-23" ] }, { "productId": "ironclad", "storyId": "automation-rules-engine", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Ironclad supports webhooks to trigger outbound notifications on events and an API/Workflows API to programmatically launch or update workflows, plus integrations that can block/push forward approvals automatically — this gives event-driven automation. However there's no evidence of a native rules engine where AI-native users can define arbitrary conditional 'if event then action' automations without building custom integration code. Missing for 10: a first-class rules/automation builder, documented trigger-condition-action configuration UI, and independent confirmation of automated rule execution in practice.", "evidenceIds": [ "ironclad-docs-4", "ironclad-docs-13", "ironclad-docs-20", "ironclad-docs-5" ] }, { "productId": "ironclad", "storyId": "automation-scheduled-jobs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Ironclad's API/webhooks allow event-driven and on-demand workflow triggering, but there is no evidence of a scheduler or recurring-job/cron capability for workflows or exports.", "evidenceIds": [] }, { "productId": "ironclad", "storyId": "automation-versioned-workflows", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Ironclad's docs mention publishing workflows via Workflow Designer and admin access, but there is no evidence of version history, review/approval flow for automation changes, or rollback capability for workflows/integrations themselves.", "evidenceIds": [ "ironclad-docs-8", "ironclad-docs-16" ] }, { "productId": "ironclad", "storyId": "board-consents", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "Ironclad is a general contract lifecycle management platform with workflow builders, e-signature, and approval routing that could be used to create and route a board consent/resolution document for approval, but there is no specific evidence of board-consent/resolution templates, cap-table/equity-fundraising features, or governance-specific workflows tailored to legal-ops board approvals. missing for 10: evidence of board consent/resolution-specific templates or workflows, evidence of equity-fundraising or governance use cases, and independent validation that Ironclad is used for board approvals specifically rather than generic contracts.", "evidenceIds": [ "ironclad-docs-9", "ironclad-docs-10", "ironclad-docs-5", "ironclad-docs-8" ] }, { "productId": "ironclad", "storyId": "bulk-send-envelopes", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "Evidence shows Ironclad's Workflow API can launch individual contract workflows and clickwraps can be embedded, but there is no documentation or feature reference to a bulk-send capability (sending one document to many recipients simultaneously). Missing for 10: any mention of bulk-send, mail-merge-style multi-recipient dispatch, or batch signature request tooling.", "evidenceIds": [ "ironclad-docs-5", "ironclad-docs-13", "ironclad-docs-16" ] }, { "productId": "ironclad", "storyId": "compliance-calendar", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Ironclad's evidence covers contract creation, signing, storage, workflows, and API/webhooks, but there is no mention of a compliance/filing deadline calendar or reminder system for legal-ops filing obligations.", "evidenceIds": [] }, { "productId": "ironclad", "storyId": "contract-approval-workflows", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Ironclad's docs describe Workflow Designer for building and publishing approval workflows, launching workflows via API/UI, and explicitly reference 'approval and signature policies' being enforced by the platform (docs-8, docs-15, docs-16, docs-20), directly matching the story of routing contracts through configurable approval steps before signature. Missing for 10: independent/hands-on verification of the approval-workflow configuration UI and no detailed walkthrough of multi-stage approval logic beyond brief doc mentions.", "evidenceIds": [ "ironclad-docs-8", "ironclad-docs-15", "ironclad-docs-16", "ironclad-docs-20", "ironclad-docs-5" ] }, { "productId": "ironclad", "storyId": "contract-draft-negotiate", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Ironclad's docs show core CLM capabilities relevant to the story—no-code contract creation, workflow designer for approvals, APIs to update contract language and control the process, and structured storage/signing—supporting a controlled workflow model instead of email attachments. However, the pack lacks explicit evidence of a redlining/track-changes or counterparty negotiation feature, and community citations are thin/tangential rather than corroborating negotiation workflows in practice. Missing for 10: explicit redline/version-comparison feature documentation, first-hand or independent evidence of negotiation collaboration replacing email attachments.", "evidenceIds": [ "ironclad-docs-9", "ironclad-docs-12", "ironclad-docs-15", "ironclad-docs-20", "ironclad-docs-21", "ironclad-docs-8", "ironclad-docs-16" ] }, { "productId": "ironclad", "storyId": "contract-repository-search", "verdict": "full", "quality": 6, "confidence": "medium", "rationale": "Ironclad's marketing and developer docs explicitly describe a 'Store Contracts Securely, Find Them Easily' repository and a Records API for retrieving/updating structured contract metadata, plus an 'Ironclad AI'/Contract Intelligence product implying key-term extraction. Missing for 10: detailed documentation of specific extracted fields/metadata schema, search functionality specifics, and independent/hands-on corroboration of extraction accuracy.", "evidenceIds": [ "ironclad-docs-11", "ironclad-docs-18", "ironclad-docs-12", "ironclad-docs-24", "ironclad-docs-2", "ironclad-docs-15" ] }, { "productId": "ironclad", "storyId": "document-generation-api", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Ironclad's developer docs describe a documented API (Workflows API to launch workflows, Records API to create/retrieve contract data, template IDs obtainable via API, webhooks for events) that supports generating, populating, and sending contracts programmatically. However, launching workflows still requires a pre-published Workflow Designer template (admin-gated, no-code step) rather than fully programmatic document creation, and there's no independent/hands-on developer corroboration of the API in practice, nor a discoverable OpenAPI spec (probe found only 404s). Missing for 10: independent developer testimonials of using the API end-to-end, a public OpenAPI/swagger spec, and evidence of fully code-driven document creation without the Workflow Designer dependency.", "evidenceIds": [ "ironclad-docs-2", "ironclad-docs-5", "ironclad-docs-8", "ironclad-docs-13", "ironclad-docs-16", "ironclad-docs-23", "ironclad-docs-4", "ironclad-probe-3" ] }, { "productId": "ironclad", "storyId": "ein-tax-id", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Ironclad is a contract lifecycle management platform focused on creating, signing, and storing contracts—it has no incorporation or EIN registration functionality, which is a wrong-axis capability for this product category.", "evidenceIds": [] }, { "productId": "ironclad", "storyId": "embedded-signing", "verdict": "full", "quality": 7, "confidence": "medium", "rationale": "Ironclad provides documented Clickwrap Workflow embedding via iframe for signing/agreement flows directly on a developer's own page. Missing for 10: independent hands-on confirmation of the embedding working in production, and broader coverage beyond clickwrap (e.g., full contract e-signature embedding) is not detailed.", "evidenceIds": [ "ironclad-docs-6", "ironclad-docs-14", "ironclad-docs-22" ] }, { "productId": "ironclad", "storyId": "equity-hiring-paperwork", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Ironclad is a general-purpose CLM platform with no-code contract creation, workflows, and e-signature that could technically be configured to handle offer letters or NDAs (ironclad-docs-9, ironclad-docs-10, ironclad-comm-6 mentions using it for contractor onboarding), but there is no evidence of purpose-built templates, workflows, or integrations for hiring/equity paperwork specifically, especially option grants which typically require cap-table integration. Missing for 10: dedicated HR/equity templates, option grant or cap-table integration evidence, and any case study showing legal-ops running full hiring paperwork through Ironclad.", "evidenceIds": [ "ironclad-docs-9", "ironclad-docs-10", "ironclad-docs-13", "ironclad-comm-6" ] }, { "productId": "ironclad", "storyId": "guided-questionnaires", "verdict": "partial", "quality": 3, "confidence": "low", "rationale": "Ironclad's no-code builder and workflow designer support guided contract creation via questionnaires that populate templates, but there's no evidence of specific attorney-review flagging logic, and community comments explicitly raise concerns about unauthorized legal practice and lack of legal vetting for templates. missing for 10: explicit guided questionnaire walkthrough, evidence of attorney-review flagging/escalation logic, independent validation that generated documents are legally correct, resolution of unauthorized-practice-of-law concerns raised by community.", "evidenceIds": [ "ironclad-docs-9", "ironclad-docs-17", "ironclad-docs-8", "ironclad-docs-16", "ironclad-comm-1", "ironclad-comm-2", "ironclad-comm-8" ] }, { "productId": "ironclad", "storyId": "incorporate-end-to-end", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Ironclad is a contract lifecycle management (CLM) platform for drafting, signing, and managing contracts/workflows, not a Delaware incorporation or company-formation service — filing articles of incorporation, generating bylaws, and initial board consent packages is outside its product category.", "evidenceIds": [] }, { "productId": "ironclad", "storyId": "legal-template-library", "verdict": "disputed", "quality": 3, "confidence": "medium", "rationale": "Ironclad markets contract creation tools (No-Code Builder, workflow templates) that could serve as a template library, but hands-on community feedback from early users directly disputes the 'vetted standard legal templates' framing: users questioned whether the templates constituted unauthorized practice of law and whether Ironclad carried malpractice insurance, and the company pulled the product to rethink it rather than defend the templates as reliable substitutes for counsel. Missing for 10: any current documentation of a curated NDA/agreement/policy template library, evidence of legal vetting or counsel review, and independent validation that founders can safely skip a lawyer.", "evidenceIds": [ "ironclad-docs-9", "ironclad-docs-17", "ironclad-comm-1", "ironclad-comm-2", "ironclad-comm-4", "ironclad-comm-8" ] }, { "productId": "ironclad", "storyId": "openness-api-parity", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Ironclad exposes a broad API (Records, Workflows, Webhooks, Data Exports, launching published workflows) letting AI-native users read/write core contract data and trigger processes, but design-time actions like building/publishing workflows and templates are explicitly UI/no-code-builder only ('See your internal company admin for access to Workflow Designer'), and no public OpenAPI spec was found (probe returned 404s for all standard spec paths), indicating incomplete machine-discoverable parity with the UI. missing for 10: API-driven workflow/template design and publishing, a public OpenAPI/schema for full endpoint discovery, and independent confirmation that all UI actions (e.g., clickwrap embedding config, template creation) are API-accessible.", "evidenceIds": [ "ironclad-docs-2", "ironclad-docs-13", "ironclad-docs-8", "ironclad-docs-16", "ironclad-docs-9", "ironclad-docs-7", "ironclad-probe-3" ] }, { "productId": "ironclad", "storyId": "openness-full-export", "verdict": "partial", "quality": 5, "confidence": "low", "rationale": "Ironclad documents a Data Exports API and Records/Workflows APIs that let customers retrieve their contract records and trigger export jobs, which supports data portability, but nothing explicitly states the export format is open/standard (e.g., JSON/CSV) or that a full, wholesale data exit is guaranteed. missing for 10: explicit statement of open export formats, documentation of a full account data export/deletion process, and independent confirmation that customers can fully migrate off Ironclad.", "evidenceIds": [ "ironclad-docs-7", "ironclad-docs-2", "ironclad-docs-13", "ironclad-docs-15" ] }, { "productId": "ironclad", "storyId": "openness-open-license", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Ironclad is a closed-source commercial SaaS contract management platform; there is no evidence of, nor plausible category expectation for, an open-licensed source code release.", "evidenceIds": [] }, { "productId": "ironclad", "storyId": "openness-self-host", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Ironclad is a SaaS contract lifecycle management platform with no on-premise/self-hosted deployment option evidenced; it is delivered exclusively as a cloud service accessed via API/webhooks. Self-hosting the 'core product' is not a plausible axis for this SaaS category.", "evidenceIds": [] }, { "productId": "ironclad", "storyId": "post-incorporation-setup", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Ironclad is a contract lifecycle management platform for enterprises, not an incorporation/formation service; it has no offering for founder stock purchase agreements, IP assignment, or 83(b) elections as part of company setup — this axis belongs to incorporation-specific products (e.g., Stripe Atlas, Clerky, Firstbase), not general contract management software.", "evidenceIds": [] }, { "productId": "ironclad", "storyId": "privacy-data-residency", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack mentions data residency, regional storage options, or geographic hosting controls for Ironclad; the docs focus on API, workflows, and contract management only. Missing for 10: any mention of region selection, data residency guarantees, or geo-specific hosting infrastructure.", "evidenceIds": [] }, { "productId": "ironclad", "storyId": "privacy-no-training", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence in the pack addresses AI training data usage, opt-out controls, or data privacy policies regarding model training; the pack only covers API/product features and unrelated community feedback.", "evidenceIds": [] }, { "productId": "ironclad", "storyId": "privacy-retention-controls", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack covers API/webhook/workflow documentation and data export jobs, but contains no mention of data retention policies, deletion controls, or AI-training data opt-outs. This is a fair axis for any SaaS handling contract data, so absence of evidence means 'none' rather than 'na'.", "evidenceIds": [] }, { "productId": "ironclad", "storyId": "privacy-telemetry-optout", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack addresses telemetry, usage tracking, or an opt-out mechanism for AI-native or any users; documentation focuses on API, workflows, and contract features.", "evidenceIds": [] }, { "productId": "ironclad", "storyId": "registered-agent-service", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Ironclad is a contract lifecycle management platform; registered agent services and receiving service of process are a completely different regulated business function unrelated to CLM's scope.", "evidenceIds": [] }, { "productId": "ironclad", "storyId": "renewal-obligation-tracking", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "The evidence pack covers Ironclad's contract creation, storage, signing, workflows, and API/webhooks, but nowhere mentions renewal tracking, expiration dates, obligation management, or automatic alerts—core to this story. Missing for 10: any documentation of renewal/expiration tracking, obligation management, or alerting/notification features.", "evidenceIds": [ "ironclad-docs-11", "ironclad-docs-18", "ironclad-docs-4" ] }, { "productId": "ironclad", "storyId": "safe-financing-docs", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Ironclad is a general contract lifecycle management platform with no-code contract creation, e-signature, and workflow tools, but the evidence never mentions SAFEs, convertible notes, or startup fundraising document templates specifically — the community comments reference generic 'industry standard templates' causing legal concerns, not equity instruments.", "evidenceIds": [ "ironclad-docs-9", "ironclad-docs-10", "ironclad-comm-2" ] }, { "productId": "ironclad", "storyId": "send-for-esignature", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Ironclad markets a dedicated 'Sign Contracts' capability and documents a Workflow Designer/Workflows API that lets processes 'follow approval and signature policies,' implying routing across multiple parties, and workflows can be launched via API for automation. However, the pack lacks concrete detail on multi-recipient routing order, legally-binding signature specifics, or independent verification of the e-signature flow working end-to-end. Missing for 10: explicit documentation of multi-recipient signing order/routing configuration, legal-binding compliance details (e.g., ESIGN/UETA), and independent/hands-on confirmation of the signature flow.", "evidenceIds": [ "ironclad-docs-10", "ironclad-docs-19", "ironclad-docs-15", "ironclad-docs-13", "ironclad-docs-5", "ironclad-docs-16" ] }, { "productId": "ironclad", "storyId": "signer-identity-verification", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack mentions signer identity verification methods such as SMS, ID check, or knowledge-based authentication for e-signature; the docs cover contract signing generally but not these verification tiers.", "evidenceIds": [ "ironclad-docs-10", "ironclad-docs-19" ] }, { "productId": "ironclad", "storyId": "signing-order-reminders", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "Evidence only shows generic e-signature and workflow/API pages but no mention of configuring signing order, automatic reminders, or expiration settings on signature requests. Missing for 10: any documentation of signing order configuration, reminder scheduling, or expiration/timeout settings for signature requests.", "evidenceIds": [ "ironclad-docs-10", "ironclad-docs-19" ] }, { "productId": "legalzoom", "storyId": "agent-drafts-routes-nda", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of an API or MCP server for drafting/routing NDAs; the evidence pack only covers business-formation product pages, community pricing complaints, and an llms.txt crawler-guidance file—none showing programmatic document drafting or e-signature routing capability. Missing for 10: any API/MCP endpoint, NDA drafting automation, e-signature routing integration.", "evidenceIds": [ "legalzoom-probe-1" ] }, { "productId": "legalzoom", "storyId": "agent-files-annual-report", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "LegalZoom offers annual-report reminders, compliance notifications, and registered-agent services, but all evidence points to a human-driven web platform (dashboard, live specialists, attorney consults) with no API, agent integration, or documented way for an autonomous agent to actually execute a filing with minimal human input; the llms.txt probe only shows AI-crawler guidance, not an agentic execution channel.", "evidenceIds": [ "legalzoom-docs-14", "legalzoom-docs-16", "legalzoom-docs-19", "legalzoom-docs-20", "legalzoom-probe-1" ] }, { "productId": "legalzoom", "storyId": "agent-monitors-renewals", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of an API for agents to monitor contracts or deadlines; only human-facing dashboard alerts and email/reminder notifications (registered agent alerts, compliance status alerts) are mentioned, with no programmatic access. Missing for 10: any public API/webhook documentation, agent integration examples, or developer-facing endpoints for contract lifecycle monitoring.", "evidenceIds": [ "legalzoom-docs-14", "legalzoom-docs-16", "legalzoom-docs-19" ] }, { "productId": "legalzoom", "storyId": "agentic-agent-docs", "verdict": "full", "quality": 8, "confidence": "medium", "rationale": "A direct probe confirms LegalZoom serves a live llms.txt file at /llms.txt with AI-crawler guidance content, showing the site is agent-discoverable. Missing for 10: no visibility into the full content/structure of the llms.txt beyond the header, and no independent community confirmation of its usefulness for agents.", "evidenceIds": [ "legalzoom-probe-1" ] }, { "productId": "legalzoom", "storyId": "agentic-ai-insights", "verdict": "partial", "quality": 2, "confidence": "low", "rationale": "The only AI-related capability found is 'AI-powered creation of meeting minutes for official record keeping,' which generates content rather than surfacing insights or suggestions derived from the user's own data. There's no evidence of AI-driven analytics, recommendations, or personalized suggestions based on a user's business data. Missing for 10: dashboard-level AI insights, data-driven suggestions/recommendations, any first-party or independent account of AI analyzing user data to produce actionable insights.", "evidenceIds": [ "legalzoom-docs-17" ] }, { "productId": "legalzoom", "storyId": "agentic-autonomous-automation", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "LegalZoom is a legal/business-formation service, not an automation/agentic platform; there is no concept of user-configured autonomous background automations here. This axis is a category error for this product type.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "agentic-builtin-assistant", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Evidence shows only a narrow 'AI-powered meeting minutes' feature and an llms.txt file for crawler guidance, not a built-in assistant that users can delegate broader tasks to. No documentation of a conversational AI agent, task delegation interface, or agentic assistant within the product.", "evidenceIds": [ "legalzoom-docs-17", "legalzoom-probe-1" ] }, { "productId": "legalzoom", "storyId": "agentic-headless", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "LegalZoom is a consumer legal-services website with no API, CLI, or SDK evidence; running it headlessly in CI is a category error for this type of product, not a missing capability.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "agentic-mcp-client", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "LegalZoom is a legal services SaaS platform, not an agent or AI tool that consumes MCP servers; nothing in the evidence suggests it has any MCP client/plugin capability, and this axis is a category error for this product type.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "agentic-mcp-server", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "LegalZoom is a consumer legal services company, not a developer platform or agent product; there is no indication it exposes any API/tool ecosystem where an MCP server would be a relevant offering. This is a category error for the product type, so the axis does not apply.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "agentic-nl-commands", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "There is no evidence of any natural-language command interface, chat-based operation, or AI agent control surface for LegalZoom's product; the llms.txt probe only indicates AI-crawler guidance for content indexing, not user-facing natural-language operation. missing for 10: any natural-language command interface, chatbot/agent control of the product, API or automation surface, evidence of AI-native operability beyond crawler guidance.", "evidenceIds": [ "legalzoom-probe-1" ] }, { "productId": "legalzoom", "storyId": "agentic-official-cli", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "LegalZoom is a legal-services/business-formation platform, not a developer tool or agentic platform; an official CLI is a category mismatch for its product type, and no evidence suggests otherwise.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "agentic-public-api", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any documented public API for LegalZoom; evidence only covers service offerings, pricing, and an llms.txt crawler guidance file, none of which constitute an API for programmatic control. Missing for 10: any API documentation, authentication scheme, endpoints, or SDK enabling programmatic/agentic use.", "evidenceIds": [ "legalzoom-probe-1" ] }, { "productId": "legalzoom", "storyId": "agentic-scoped-keys", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "LegalZoom is a consumer legal/business services platform, not a developer platform or API product; issuing scoped API credentials for agents is not a relevant capability for this kind of product.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "agentic-sdks", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "LegalZoom is a consumer legal services platform, not a developer platform; there is no indication SDKs or programmatic building are part of its product category. This axis is a category error for this type of product.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "agentic-webhooks", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "LegalZoom is a consumer legal services platform, not a developer platform or API product; webhooks/event subscriptions are not a relevant axis for this kind of product, and no evidence suggests any API or developer integration surface exists.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "annual-report-filings", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "LegalZoom docs show registered-agent and annual-report services with deadline reminders and real-time compliance status alerts (docs-14, docs-16), which support timely annual report filing, but there's no explicit evidence of franchise tax filing/payment services on the platform. Missing for 10: franchise tax filing/payment capability, evidence of actual on-time filing outcomes, and independent/hands-on corroboration of the annual report filing process working as described.", "evidenceIds": [ "legalzoom-docs-14", "legalzoom-docs-16", "legalzoom-docs-13" ] }, { "productId": "legalzoom", "storyId": "api-interactive-docs", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "LegalZoom is a consumer legal-services platform, not a developer API product; an interactive API reference with runnable examples is not a fair axis for this product type, and no evidence suggests it exposes a public API at all.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "api-machine-spec", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of an OpenAPI spec, developer API, or machine-readable API documentation anywhere in the evidence pack; only marketing docs, community commentary, and an llms.txt crawler guidance file are present, none of which constitute an API spec.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "api-sandbox", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "LegalZoom is a legal-services product for consumers/businesses, not a developer platform or API with sandbox/test environments; sandbox testing against production data is a category error for this product type.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "api-versioning-policy", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "LegalZoom is a consumer legal-services company, not a developer platform with APIs; the evidence pack contains no mention of any API at all. Versioned APIs and deprecation policies are a wrong-axis question for this type of product.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "audit-trail-certificate", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "LegalZoom is a legal services/business formation platform, not an e-signature or document execution tool; tamper-evident audit trails and completion certificates are specific to e-signature products (e.g., DocuSign) and this axis doesn't apply to LegalZoom's business model shown in evidence.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "automation-bulk-operations", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "LegalZoom is a consumer legal-services platform for individual business formation/compliance tasks, not a data or workflow tool with bulk/batch operations across many items. No evidence pack content addresses bulk processing, and the product's nature (one entity/filing at a time) makes this axis a category mismatch.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "automation-rules-engine", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "LegalZoom is a legal/business-formation services product, not an automation/workflow platform; there is no rule-engine or event-trigger capability applicable to this category, and none of the evidence describes such functionality.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "automation-scheduled-jobs", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "LegalZoom is a legal/business services provider, not a workflow or automation platform; scheduling recurring jobs/workflows is a category error for this product type.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "automation-versioned-workflows", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "LegalZoom is a legal-services/business-formation platform, not an automation/workflow tool with versioned pipelines a user builds and rolls back; this axis is a category error for the product type.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "board-consents", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "Evidence pack covers business formation, registered agent, annual reports, and general services, but nothing mentions board consents, resolutions, or online e-signature/approval collection workflows for governance actions.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "bulk-send-envelopes", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "LegalZoom is a legal-document/business-formation service, not an e-signature platform; there is no evidence of bulk-sending documents for signature to many recipients, and this capability is outside its product category.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "compliance-calendar", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "LegalZoom's registered agent and annual report services document reminders for annual report deadlines and real-time compliance status notifications, which meets the 'reminders before deadlines' part of the story. However, there's no evidence of a unified compliance calendar view aggregating multiple filing deadlines for legal-ops oversight. Missing for 10: dedicated calendar UI/dashboard listing all upcoming filings, evidence of reminders for filings beyond annual reports (e.g., licenses, permits), and independent confirmation the reminder system works reliably.", "evidenceIds": [ "legalzoom-docs-14", "legalzoom-docs-16", "legalzoom-docs-19" ] }, { "productId": "legalzoom", "storyId": "contract-approval-workflows", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "LegalZoom is a consumer/SMB legal document and business-formation service; there is no evidence of contract lifecycle management or configurable approval workflow features. This is a category mismatch rather than a missing feature of a CLM product—LegalZoom's product type does not include enterprise approval-routing workflows.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "contract-draft-negotiate", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Evidence shows LegalZoom offers business formation, registered agent, compliance, and template document services, but nothing about a contract drafting/negotiation/redlining workflow, version control, or collaborative markup replacing email. Missing for 10: contract drafting workflow, redlining/version comparison tools, negotiation collaboration features, audit trail of changes.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "contract-repository-search", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Evidence shows LegalZoom offers unlimited cloud storage for business documents (legalzoom-docs-15) but nothing about a searchable repository with automated extraction of key contract terms/metadata—no clause extraction, no contract search/filtering, no metadata tagging capability is described anywhere in the evidence pack.", "evidenceIds": [ "legalzoom-docs-15" ] }, { "productId": "legalzoom", "storyId": "document-generation-api", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of any developer API, SDK, or programmatic document generation/send capability—only consumer-facing web forms and service descriptions are documented. missing for 10: public API reference, authentication/SDK docs, programmatic document population/send endpoints, developer sandbox or examples.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "ein-tax-id", "verdict": "full", "quality": 6, "confidence": "medium", "rationale": "LegalZoom's LLC formation package explicitly lists obtaining an EIN as part of the service, used for taxes, banking, and hiring staff. Missing for 10: dedicated EIN service documentation detailing the application process/turnaround, and independent/hands-on confirmation of EIN delivery.", "evidenceIds": [ "legalzoom-docs-5" ] }, { "productId": "legalzoom", "storyId": "embedded-signing", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "LegalZoom is a consumer legal services platform (business formation, compliance, documents); there is no evidence of a developer API or embeddable e-signature widget/SDK for third-party apps. This is a category error for this product type, not a missing feature.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "equity-hiring-paperwork", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "The evidence pack covers business formation, registered agent, annual reports, and general legal document access, but contains no mention of offer letters, employee confidentiality/IP assignment agreements, or stock option grant paperwork—the core equity-fundraising/HR-ops artifacts in this story.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "guided-questionnaires", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "LegalZoom's docs show guided document creation (150+ customizable legal documents, LLC/incorporation forms, operating agreements) and bundled attorney consultations for follow-up questions, implying some review path, but there is no explicit evidence of an in-flow questionnaire mechanism that flags specific answer choices needing attorney review. Community comments (e.g., a lawyer noting operating agreements are not commodities) suggest the templated approach may miss nuanced legal decisions that would warrant human review, without directly disputing the questionnaire's correctness. missing for 10: explicit description of the guided questionnaire UI/logic that flags risky choices, independent verification that flagged items are accurate or attorney-reviewed in real time.", "evidenceIds": [ "legalzoom-docs-6", "legalzoom-docs-23", "legalzoom-docs-7", "legalzoom-docs-26", "legalzoom-comm-3" ] }, { "productId": "legalzoom", "storyId": "incorporate-end-to-end", "verdict": "partial", "quality": 4, "confidence": "low", "rationale": "LegalZoom's docs confirm it can file corporation formation (S corp/C corp) online with flat fees and error correction guarantees, which covers the core 'filing' part of a Delaware startup incorporation, but there is no evidence of Delaware-specific service, bylaws drafting, or initial board resolutions/approvals being part of the package (those items are only mentioned for LLC operating agreements, not corporations). Community feedback focuses on LLC formation cost complaints, not corporate incorporation completeness. Missing for 10: Delaware-specific incorporation flow, bylaws generation, initial board consent/resolution documents, and independent verification that these are actually delivered.", "evidenceIds": [ "legalzoom-docs-2", "legalzoom-docs-11", "legalzoom-docs-12", "legalzoom-comm-3" ] }, { "productId": "legalzoom", "storyId": "legal-template-library", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "LegalZoom explicitly offers access to '150+ customizable legal documents' for a year as part of its formation packages, which covers routine business documents like agreements and policies. However, community commentary (a lawyer user) cautions that while basic filings are a commodity, actual document content like operating agreements 'couldn't be more wrong' to assume as commodity, suggesting template quality/customization limits for more complex needs; other users note forms are 'easy enough to fill out yourself' without paid help, undercutting the value-add. Missing for 10: explicit breakdown of NDA/policy-specific templates, evidence of attorney-vetting process behind each template, and independent quality assessment of document library beyond LLC-related bundle mentions.", "evidenceIds": [ "legalzoom-docs-23", "legalzoom-docs-6", "legalzoom-comm-3", "legalzoom-comm-2" ] }, { "productId": "legalzoom", "storyId": "openness-api-parity", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence of a public API for LegalZoom services at all — only an llms.txt for AI crawling guidance and marketing/docs pages describing UI-based products. Missing for 10: any documented API, API authentication, endpoint coverage of formation/filing/document features, or third-party integration evidence.", "evidenceIds": [ "legalzoom-probe-1" ] }, { "productId": "legalzoom", "storyId": "openness-full-export", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence anywhere in the pack of a data export feature, open format export (e.g., CSV/JSON/PDF bulk download), or account/data portability tooling for leaving the platform; evidence only covers business formation services, pricing, and add-ons. Missing for 10: any documented export tool, data portability API, or account closure/data-download workflow.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "openness-open-license", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "LegalZoom is a legal services SaaS platform, not open-source software; open-source licensing of source code is not a fair axis for this product category.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "openness-self-host", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "LegalZoom is a SaaS legal-services platform, not self-hostable software; self-hosting is a category error for this product type.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "post-incorporation-setup", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "The evidence pack covers LLC/incorporation filing, registered agent, annual reports, and general legal document services, but contains no mention of founder stock purchase agreements, IP assignment agreements, or 83(b) election filing support — the specific post-incorporation paperwork the story asks about. Nothing in the docs, community, or probe items addresses this startup-specific stock/equity setup workflow.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "privacy-data-residency", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "LegalZoom is a consumer legal services platform, not a data/infrastructure product where a user would configure data region/residency; no evidence pack content relates to data storage location choices.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "privacy-no-training", "verdict": "none", "quality": 0, "confidence": "low", "rationale": "No evidence of an AI-training opt-out or data-use control mechanism anywhere in LegalZoom's docs, marketing, or community discussion; the evidence pack covers business formation services, not privacy/data controls. missing for 10: any privacy policy or settings documentation on AI training opt-out, data usage controls, or user consent mechanisms for AI model training.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "privacy-retention-controls", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "LegalZoom is a legal-services/business-formation platform, not an AI tool or data-processing product with user-controllable data retention/deletion settings relevant to AI-native workflows; this axis is a category error for this product type and no evidence contradicts that.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "privacy-telemetry-optout", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "LegalZoom is a legal services platform, not an AI tool/agent with telemetry settings relevant to AI-native usage; opting out of usage tracking is not a fair axis for this product category, and no evidence discusses telemetry controls.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "registered-agent-service", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "LegalZoom's registered agent service page confirms core RA functionality: alerts when official mail arrives, unlimited cloud storage for documents, and assistance switching agents, which supports the founder-story premise of receiving legal mail digitally. However, there's no explicit documentation confirming scanned copies of service of process specifically or digital delivery mechanics (scan speed, dashboard viewing), and no independent/hands-on corroboration of the mail-forwarding experience. missing for 10: explicit mention of 'service of process' handling, description of scanning/digitization process, independent user reports confirming reliability of mail alerts.", "evidenceIds": [ "legalzoom-docs-13", "legalzoom-docs-14", "legalzoom-docs-15" ] }, { "productId": "legalzoom", "storyId": "renewal-obligation-tracking", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "LegalZoom's evidence shows alerts for compliance filings, annual reports, and registered-agent mail, but nothing about tracking contract renewals, expirations, or contractual obligations specifically — a distinct contract-lifecycle-management capability that is plausible for a legal services provider but unevidenced here.", "evidenceIds": [ "legalzoom-docs-14", "legalzoom-docs-16" ] }, { "productId": "legalzoom", "storyId": "safe-financing-docs", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Evidence pack covers business formation, registered agent, compliance, and bookkeeping services but contains no mention of SAFEs, convertible notes, equity fundraising documents, or investor-facing templates. This is a plausible axis for a legal-document generation service, but no evidence shows LegalZoom supports generating/signing SAFEs or convertible notes.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "send-for-esignature", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence pack items mention e-signature functionality, multi-recipient routing, or document signing workflows; all evidence is about business formation, registered agent, and compliance services. Missing for 10: any mention of e-signature feature, multi-recipient routing/workflow, or signing order/audit trail.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "signer-identity-verification", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "LegalZoom is a consumer/business legal-services and document platform (business formation, registered agent, compliance filings), not an e-signature/document-signing product with configurable signer identity verification options. The story's axis (SMS/ID/KBA verification for e-signature workflows) does not apply to this product category.", "evidenceIds": [] }, { "productId": "legalzoom", "storyId": "signing-order-reminders", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "LegalZoom is a business formation and legal services platform, not an e-signature/document-signing product; setting signing order, reminders, and expirations on signature requests is a category error for this product's core offering, with no evidence of such e-signature workflow features.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "agent-drafts-routes-nda", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is an incorporation/company-formation product (EIN, 83(b) elections, SAFEs, bank account setup); NDA drafting and e-signature routing is entirely outside its product scope. This is a wrong-axis question, not a missing feature.", "evidenceIds": [ "stripe-atlas-docs-1", "stripe-atlas-docs-3", "stripe-atlas-docs-6" ] }, { "productId": "stripe-atlas", "storyId": "agent-files-annual-report", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Evidence shows Stripe Atlas handles incorporation, EIN, 83(b) elections, and tax filing as a human-facing dashboard/paperwork service with lawyer/accountant support, but there is no evidence of any agent-accessible API, delegation mechanism, or AI-agent workflow for compliance filings; community notes even highlight ongoing manual legwork and need for accountants/lawyers. Missing for 10: any API/agent interface for filings, evidence of autonomous or minimal-human-input agent delegation, documentation of an agent-facing workflow for annual reports or compliance filings.", "evidenceIds": [ "stripe-atlas-docs-3", "stripe-atlas-docs-4", "stripe-atlas-comm-16", "stripe-atlas-comm-12" ] }, { "productId": "stripe-atlas", "storyId": "agent-monitors-renewals", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is a company-incorporation and startup formation service (EIN, bank account, SAFEs, incorporation docs) with no concept of 'contracts' with renewal/deadline lifecycles for an agent to monitor via API; this axis is a category error for the product type.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "agentic-agent-docs", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Probes confirm docs.stripe.com serves a working llms.txt (HTTP 200) and .md versions of Atlas docs pages (e.g., atlas.md, signup.md, 83b-election.md), enabling agents to fetch agent-oriented documentation directly. Missing for 10: no independent third-party confirmation of agent usage/testing against these files, and no explicit Atlas-specific llms.txt (it's site-wide for Stripe docs).", "evidenceIds": [ "stripe-atlas-probe-1", "stripe-atlas-probe-2", "stripe-atlas-docs-7" ] }, { "productId": "stripe-atlas", "storyId": "agentic-ai-insights", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence that Stripe Atlas provides AI-generated insights or suggestions from user data; the evidence pack covers incorporation, banking, equity, and legal services with no mention of AI analytics or recommendations features.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "agentic-autonomous-automation", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is a company-formation/incorporation service, not an automation or agent platform; the story about autonomous background automations is a category mismatch and no evidence suggests otherwise.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "agentic-builtin-assistant", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is a company-incorporation and startup-formation service, not an AI assistant/agent product; there is no axis for delegating tasks to a built-in AI assistant within this product category, and no evidence suggests one exists.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "agentic-headless", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is a one-time company incorporation/formation service, not a tool meant for repeated headless/CI automation workflows; the evidence pack covers incorporation, banking, equity, and legal document processes with no API/CLI automation surface for this axis.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "agentic-mcp-client", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is a company-incorporation/back-office service, not an AI agent or assistant platform; plugging MCP servers into it so it can 'use their tools' is a category error for this kind of product, with no evidence it functions as an AI-agent host.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "agentic-mcp-server", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is a company-incorporation/business-formation service, not an agent or AI-native product with tool-serving capability; connecting an agent via an MCP server is a wrong-axis question for this product category. No evidence suggests Atlas exposes any MCP server or agent connectivity.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "agentic-nl-commands", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is a company-incorporation and formation service (dashboard-driven forms, legal filings, bank account setup), not a conversational or agentic interface product; natural-language command operation is not a fair axis for this kind of product.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "agentic-official-cli", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is a business-incorporation service (forming companies, banking, 83(b) filings), not a developer tool or platform where a CLI would be a natural product surface; the 'official CLI' axis is a category error here.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "agentic-public-api", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No evidence of a documented public API for Atlas itself (company incorporation, SAFE creation, EIN, 83(b) filing, etc.); the OpenAPI probe returned 404s across all candidate paths, and docs only describe Dashboard-based workflows. Stripe's general payments API exists but is a separate product, not evidence Atlas's incorporation/fundraising features are API-driven.", "evidenceIds": [ "stripe-atlas-probe-3", "stripe-atlas-docs-1", "stripe-atlas-docs-6" ] }, { "productId": "stripe-atlas", "storyId": "agentic-scoped-keys", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is a company-incorporation and startup-formation service (EIN, bank account, SAFEs, legal docs), not an API/credentialing platform for agents; scoped API credential issuance is outside its product category.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "agentic-sdks", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is a company-incorporation and startup-formation service (legal filings, bank accounts, SAFEs), not a developer API/SDK product; building against 'official SDKs' is not a fair question for this kind of offering, even though the parent Stripe platform has SDKs.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "agentic-webhooks", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is a company-incorporation/formation service (legal filings, bank account setup, EIN, equity), not an API/event-driven platform; webhook subscriptions are a wrong axis for this product category, unlike Stripe's core payments API.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "annual-report-filings", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No Stripe Atlas documentation claims automated filing of annual reports or Delaware franchise tax on the founder's behalf; the only related community evidence explicitly states the opposite — founders must proactively manage franchise tax bills themselves with 'no warnings' from Atlas, and state/city-level legwork is left to the user.", "evidenceIds": [ "stripe-atlas-comm-19", "stripe-atlas-comm-16" ] }, { "productId": "stripe-atlas", "storyId": "api-interactive-docs", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is a company-incorporation/formation service (bank account, EIN, SAFEs, legal docs), not an API-driven product for which an interactive runnable API reference would be a relevant offering; this axis is a category error for Atlas itself (Stripe's core payments API has such docs, but Atlas is not that).", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "api-machine-spec", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Stripe Atlas docs provide markdown/llms.txt but the explicit probe for OpenAPI spec files at docs.stripe.com returned 404 for all candidate paths, and no other evidence pack item shows a machine-readable API spec being offered for Atlas.", "evidenceIds": [ "stripe-atlas-probe-3", "stripe-atlas-probe-1", "stripe-atlas-probe-2" ] }, { "productId": "stripe-atlas", "storyId": "api-sandbox", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is a company-incorporation and startup formation service (EIN, bank account, SAFEs, legal docs), not a development/testing product with data/API sandboxing—this axis is a category error for this product type.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "api-versioning-policy", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is a company-formation/incorporation service (legal filings, bank accounts, equity docs), not an API product with versioned endpoints for developers to integrate against — the axis of API versioning/deprecation policy is a category error here, distinct from Stripe's core payments API.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "audit-trail-certificate", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "Evidence covers incorporation, document storage, SAFEs, and legal templates, but nothing addresses tamper-evident audit trails or completion certificates for signed documents (e.g., e-signature integrity verification), which is what a legal-ops lead would need.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "automation-bulk-operations", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is a one-time company-incorporation service (bank account, EIN, SAFEs, legal docs), not a data/records platform where bulk operations across many items would apply; this axis is a category error for this product type.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "automation-rules-engine", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is a company-incorporation/formation service, not a platform for defining event-triggered automation rules; this axis is a category error for this product type.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "automation-scheduled-jobs", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is a company-incorporation and startup-formation service, not a workflow/automation platform; scheduling recurring jobs is not a relevant axis for this product category.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "automation-versioned-workflows", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is a company-incorporation and startup-formation service, not an automation/workflow platform; versioning, reviewing, or rolling back 'automations' is not a relevant concept for this product's category.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "board-consents", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Evidence covers incorporation, equity issuance, SAFEs, 83(b) elections, and Cooley-developed legal document templates, but nothing describes preparing board consents/resolutions or collecting board approvals online. Missing for 10: any mention of board consent templates, resolution drafting, or an e-signature/approval-collection workflow for board actions.", "evidenceIds": [ "stripe-atlas-docs-6", "stripe-atlas-docs-7", "stripe-atlas-docs-8" ] }, { "productId": "stripe-atlas", "storyId": "bulk-send-envelopes", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is a company-incorporation and startup-formation product (EIN, bank account, equity, SAFEs); bulk e-signature/document distribution to many recipients is not a feature category it addresses, making this a wrong axis rather than a missing capability.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "compliance-calendar", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No evidence Atlas provides a compliance calendar or deadline reminder system; docs cover incorporation, EIN, 83(b) filing, and equity but nothing about ongoing filing deadline tracking. Community evidence actually notes the opposite—one founder reports being blindsided by Delaware franchise tax bills with 'no warnings' from Atlas, and another notes Atlas doesn't handle state/city-level ongoing compliance legwork.", "evidenceIds": [ "stripe-atlas-comm-19", "stripe-atlas-comm-16" ] }, { "productId": "stripe-atlas", "storyId": "contract-approval-workflows", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is a company incorporation/formation product (EIN, bank account, equity, 83(b) elections, SAFEs), not a contract-lifecycle or e-signature/approval-workflow tool; routing contracts through configurable approval workflows before signature is outside its category.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "contract-draft-negotiate", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is a company-incorporation and startup-setup service (formation, EIN, bank account, SAFEs, template legal docs), not a contract-lifecycle/redlining tool; the story of drafting/negotiating/redlining contracts in a controlled workflow is outside its product category.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "contract-repository-search", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is an incorporation/startup-formation product (EIN, banking, equity, SAFEs); it provides a basic Documents tab for incorporation paperwork but is not a contract-lifecycle/repository product with searchable metadata extraction across executed contracts. This is a category mismatch, not a missing feature.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "document-generation-api", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Atlas documents show SAFEs, 83(b) elections, and incorporation paperwork are created/sent/tracked via the Dashboard, not through a documented developer API, and an OpenAPI/spec probe returned 404s. Missing for 10: any documented REST/API endpoints for generating or sending legal documents programmatically, SDK examples, or API reference for Atlas document workflows.", "evidenceIds": [ "stripe-atlas-docs-6", "stripe-atlas-docs-8", "stripe-atlas-probe-3" ] }, { "productId": "stripe-atlas", "storyId": "ein-tax-id", "verdict": "full", "quality": 9, "confidence": "high", "rationale": "Stripe's docs explicitly state Atlas obtains the company's federal tax ID (EIN) from the IRS as part of incorporation, alongside issuing equity and filing 83(b) elections, and this is corroborated by community accounts of smooth incorporation/tax processes via Atlas. Missing for 10: independent hands-on confirmation specifically of EIN turnaround time or edge-case delays.", "evidenceIds": [ "stripe-atlas-docs-4", "stripe-atlas-docs-5", "stripe-atlas-comm-12", "stripe-atlas-comm-13" ] }, { "productId": "stripe-atlas", "storyId": "embedded-signing", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is a company-formation/incorporation service, not an e-signature or document-signing platform; embedding a signing experience is outside its product scope (it references its own dashboard-based document generation, not an embeddable signing widget for third-party apps).", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "equity-hiring-paperwork", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Atlas documents cover founder equity issuance, vesting customization, and 83(b) election filing, plus general access to Cooley-developed legal documents, which touches option-grant paperwork. However, there is no explicit evidence of offer-letter templates or confidentiality/IP assignment agreement workflows being run through the platform. missing for 10: dedicated offer-letter generation, confidentiality/IP agreement templates, independent confirmation of hiring paperwork beyond equity/incorporation docs.", "evidenceIds": [ "stripe-atlas-docs-2", "stripe-atlas-docs-3", "stripe-atlas-docs-4", "stripe-atlas-docs-7", "stripe-atlas-docs-8" ] }, { "productId": "stripe-atlas", "storyId": "guided-questionnaires", "verdict": "partial", "quality": 5, "confidence": "medium", "rationale": "Atlas does offer guided steps that auto-generate certain legal docs (vesting terms, 83(b) elections, SAFEs, Cooley-drafted templates) and a checklist walkthrough praised by users, but there is no evidence of a questionnaire that explicitly flags decisions needing attorney review — community reports even note Atlas gave 'no warnings' about high-share-count franchise tax consequences and that 'Atlas does not remove the need for an accountant, or a lawyer,' meaning founders must proactively seek legal review themselves. Missing for 10: an explicit attorney-review-flagging mechanism in the questionnaire, and documentation showing how edge-case legal choices are surfaced to counsel.", "evidenceIds": [ "stripe-atlas-docs-2", "stripe-atlas-docs-3", "stripe-atlas-docs-6", "stripe-atlas-docs-7", "stripe-atlas-comm-13", "stripe-atlas-comm-16", "stripe-atlas-comm-19" ] }, { "productId": "stripe-atlas", "storyId": "incorporate-end-to-end", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Docs and community reports confirm Atlas handles Delaware C-corp/LLC incorporation, EIN, founder equity issuance, 83(b) filings, and provides Cooley-drafted legal docs (bylaws, vesting agreements) within days, with independent users confirming a smooth end-to-end filing/checklist experience. Missing for 10: explicit mention of formal 'initial board consent/board approval' documents and independent verification that board resolutions are auto-generated, plus some community reports note extra legwork (state/local filings, franchise tax) still required.", "evidenceIds": [ "stripe-atlas-docs-1", "stripe-atlas-docs-3", "stripe-atlas-docs-4", "stripe-atlas-docs-7", "stripe-atlas-docs-8", "stripe-atlas-docs-11", "stripe-atlas-comm-13", "stripe-atlas-comm-16" ] }, { "productId": "stripe-atlas", "storyId": "legal-template-library", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Atlas provides legal documents developed with Cooley (a startup law firm), including incorporation docs, vesting agreements, and SAFEs, which covers a subset of standard founder legal templates. However, community evidence shows Atlas 'does not remove the need for an accountant, or a lawyer' and users still turned to alternatives like Clerky for gaps in coverage (e.g., broader NDAs/policies), indicating the library is narrower than a full standard-template suite. Missing for 10: explicit evidence of NDA templates, HR/policy documents, or a broader vetted template library beyond incorporation/vesting/SAFE docs, and independent confirmation of template breadth.", "evidenceIds": [ "stripe-atlas-docs-7", "stripe-atlas-docs-6", "stripe-atlas-docs-2", "stripe-atlas-comm-16", "stripe-atlas-comm-17" ] }, { "productId": "stripe-atlas", "storyId": "openness-api-parity", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "No evidence Atlas exposes an API for incorporation, SAFE creation, 83(b) filing, or bank account setup; all documented workflows describe Dashboard-only actions, and a probe for an OpenAPI/swagger spec on the docs site returned 404s. missing for 10: any documented Atlas API endpoints, API reference docs, or programmatic equivalents of the incorporation/SAFE/dashboard workflows.", "evidenceIds": [ "stripe-atlas-docs-6", "stripe-atlas-docs-8", "stripe-atlas-probe-3" ] }, { "productId": "stripe-atlas", "storyId": "openness-full-export", "verdict": "none", "quality": 0, "confidence": "medium", "rationale": "Stripe Atlas is a company-incorporation/legal-paperwork service (EIN, incorporation docs, SAFEs, 83(b) filings); there is no evidence of a data export feature or open-format data portability for users to leave with their data. The only related item is viewing incorporation documents in a dashboard tab, which is not a bulk export in open formats, and no evidence discusses exporting or migrating data out of Atlas.", "evidenceIds": [ "stripe-atlas-docs-8" ] }, { "productId": "stripe-atlas", "storyId": "openness-open-license", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is a company-incorporation/business-formation service, not a software product with source code; open-source licensing is not an applicable axis for this kind of product.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "openness-self-host", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is a managed incorporation/legal/banking service, not infrastructure software; self-hosting is a category error for this kind of product.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "post-incorporation-setup", "verdict": "full", "quality": 8, "confidence": "high", "rationale": "Stripe Atlas docs explicitly confirm it issues founder equity with customizable vesting, files 83(b) elections for all C-corp founders, and provides legal documents developed with Cooley, plus a dashboard to view incorporation documents — directly matching the story's core elements. Community evidence corroborates a smooth incorporation experience, though notes some legwork/gaps remain outside Atlas's scope (e.g., no IP assignment specifics mentioned, and one user needed Clerky for extra needs). Missing for 10: explicit documentation of IP assignment agreements as a named deliverable, and independent verification of 83(b) filing accuracy/timeliness.", "evidenceIds": [ "stripe-atlas-docs-2", "stripe-atlas-docs-3", "stripe-atlas-docs-4", "stripe-atlas-docs-7", "stripe-atlas-docs-8", "stripe-atlas-comm-16", "stripe-atlas-comm-17" ] }, { "productId": "stripe-atlas", "storyId": "privacy-data-residency", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is a company-incorporation/formation service, not a data-hosting or AI platform; data residency/region selection is not a relevant axis for this product category.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "privacy-no-training", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is a company-incorporation/business-formation service, not an AI product handling training data; opting out of AI model training is a wrong-axis question for this product category.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "privacy-retention-controls", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is a company-incorporation and startup-formation service, not an AI/data-processing product; controlling AI data retention/deletion is not a relevant axis for this kind of product.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "privacy-telemetry-optout", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is a company-incorporation/business-formation service, not an AI agent, SDK, or developer tool with telemetry/usage-tracking concerns relevant to AI-native workflows; the axis of opting out of telemetry does not apply to this kind of product.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "registered-agent-service", "verdict": "none", "quality": 0, "confidence": "high", "rationale": "No evidence in the pack mentions registered agent services, scanned legal mail, or service-of-process handling; Atlas documentation covers incorporation, EIN, 83(b), bank accounts, and SAFEs but nothing about acting as a registered agent or forwarding legal mail digitally.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "renewal-obligation-tracking", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is a company incorporation and startup formation service (EIN, incorporation docs, SAFEs, banking setup), not a contract-lifecycle-management tool; contract renewal/expiration tracking with alerts is entirely outside its product category.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "safe-financing-docs", "verdict": "partial", "quality": 6, "confidence": "medium", "rationale": "Docs confirm Atlas lets founders create, send, and track SAFEs from the Dashboard, and provides Cooley-developed legal document templates plus equity issuance/83(b) filing, indicating standard-terms documents are generated rather than drafted from scratch. However, evidence doesn't detail convertible notes specifically, nor confirm e-signature workflows or full customization scope, and community feedback notes gaps requiring outside lawyers for other paperwork. Missing for 10: explicit convertible note support, signing/e-signature flow details, independent hands-on confirmation of SAFE generation quality.", "evidenceIds": [ "stripe-atlas-docs-6", "stripe-atlas-docs-7", "stripe-atlas-docs-2", "stripe-atlas-comm-17" ] }, { "productId": "stripe-atlas", "storyId": "send-for-esignature", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is a company-incorporation and startup-formation service (EIN, bank account, SAFEs, 83(b) elections), not an e-signature/document routing product; multi-recipient e-signature workflows are outside its category.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "signer-identity-verification", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is an incorporation/company-formation service (EIN, SAFEs, equity, banking) — it has no e-signature/document-signing workflow feature to attach signer identity verification (SMS/ID/KBA) to; this is a category error, not a missing feature.", "evidenceIds": [] }, { "productId": "stripe-atlas", "storyId": "signing-order-reminders", "verdict": "na", "quality": 0, "confidence": "high", "rationale": "Stripe Atlas is a company-incorporation and startup-formation service (EIN, incorporation docs, SAFEs, banking); it has no e-signature workflow product with signing order, reminders, or expirations — this axis belongs to dedicated e-signature tools, not Atlas.", "evidenceIds": [] } ]