Firstbase vs Ironclad

Agent access

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

   weight 2 · round to Ironclad
   Firstbase—none0/10

   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.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.firstbase.io/llms.txt”

   proof ↗⚑ flag

   Ironclad✓fullprobed9/10

   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.

   • [probe] “PROBE llms.txt: HTTP 200 at https://developer.ironcladapp.com/llms.txt # Ironclad CLM API Documentation | Ironclad Developer Hub Documentati…”
   • [probe] “PROBE docs-md: HTTP 200 at https://developer.ironcladapp.com/docs/getting-started.md --- updatedAt: 2026-08-11T20:11:21.000Z --- Fetch the …”
   • [claimed-docs] “Ironclad's rich API can be used to connect your contract data and contracting process to your applications and internal platforms.”

   proof ↗⚑ flag

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

   weight 3 · round to Ironclad
   Firstbase—none0/10

   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.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.firstbase.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.firstbase.io/openapi.json, https://www.firstbase.io/swagger.json, https://www.firstbase.…”

   proof ↗⚑ flag

   Ironclad✓fullprobed7/10

   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.

   • [claimed-docs] “Ironclad's rich API can be used to connect your contract data and contracting process to your applications and internal platforms.”
   • [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
   • [claimed-docs] “Ironclad primarily uses the OAuth 2.0 Authorization Framework to generate API bearer tokens that can be used to authenticate API requests.”
   • [claimed-docs] “Webhooks allow you to specify that we should POST to your URL when certain events happen.”
   • [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
   • [claimed-docs] “Integrations can also directly control the contract process, automatically blocking or pushing forward approvals.”
   • [claimed-docs] “integrations can interface directly with underlying contract documents, reading contract text or updating new versions of the document”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.ironcladapp.com/openapi.json, https://developer.ironcladapp.com/swagger.json, http…”

   proof ↗⚑ flag

3. ai-native userBuild against official SDKs

   weight 2 · round drawn
   Firstbase—none0/10

   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.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.firstbase.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.firstbase.io/openapi.json, https://www.firstbase.io/swagger.json, https://www.firstbase.…”

   proof ↗⚑ flag

   Ironclad—none0/10

   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.

   • [claimed-docs] “Ironclad's rich API can be used to connect your contract data and contracting process to your applications and internal platforms.”
   • [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
   • [claimed-docs] “Ironclad primarily uses the OAuth 2.0 Authorization Framework to generate API bearer tokens that can be used to authenticate API requests.”
   • [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.ironcladapp.com/openapi.json, https://developer.ironcladapp.com/swagger.json, http…”

   proof ↗⚑ flag

4. ai-native userSubscribe to events via webhooks

   weight 2 · round to Ironclad
   Firstbase—none0/10

   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.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.firstbase.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.firstbase.io/openapi.json, https://www.firstbase.io/swagger.json, https://www.firstbase.…”

   proof ↗⚑ flag

   Ironclad✓fullclaimed7/10

   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.

   • [claimed-docs] “Webhooks allow you to specify that we should POST to your URL when certain events happen.”

   proof ↗⚑ flag

Agentic features

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

   weight 2 · round to Ironclad
   Firstbase—none0/10

   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.

   ⚑ flag

   Ironclad~partialclaimed3/10

   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.

   • [claimed-docs] “Built on how contracts really move.”
   • [claimed-docs] “A New Era of Contract Intelligence | Ironclad”

   proof ↗⚑ flag

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

   weight 2 · round to Ironclad
   Firstbase—none0/10

   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.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.firstbase.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.firstbase.io/openapi.json, https://www.firstbase.io/swagger.json, https://www.firstbase.…”

   proof ↗⚑ flag

   Ironclad~partialclaimed5/10

   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.

   • [claimed-docs] “Webhooks allow you to specify that we should POST to your URL when certain events happen.”
   • [claimed-docs] “Technical audiences will learn how to use Ironclad's API to launch workflows.”
   • [claimed-docs] “Integrations can also directly control the contract process, automatically blocking or pushing forward approvals.”
   • [claimed-docs] “integrations can read and write structured data from Ironclad, leaving the specifics around updating contract language and following approva…”
   • [claimed-docs] “Published workflow design and Workflow Designer access: See your internal company admin for access to Workflow Designer.”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Firstbase—none0/10

   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.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.firstbase.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.firstbase.io/openapi.json, https://www.firstbase.io/swagger.json, https://www.firstbase.…”

   proof ↗⚑ flag

   Ironclad—none0/10

   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.

   • [claimed-docs] “Built on how contracts really move.”
   • [claimed-docs] “A New Era of Contract Intelligence | Ironclad”
   • [claimed-docs] “Ironclad's rich API can be used to connect your contract data and contracting process to your applications and internal platforms.”

   proof ↗⚑ flag

Api quality

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

   weight 2 · round drawn
   Firstbase—none0/10

   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.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.firstbase.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.firstbase.io/openapi.json, https://www.firstbase.io/swagger.json, https://www.firstbase.…”

   proof ↗⚑ flag

   Ironclad—none0/10

   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.

   • [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
   • [claimed-docs] “Ironclad primarily uses the OAuth 2.0 Authorization Framework to generate API bearer tokens that can be used to authenticate API requests.”
   • [claimed-docs] “Webhooks allow you to specify that we should POST to your URL when certain events happen.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.ironcladapp.com/openapi.json, https://developer.ironcladapp.com/swagger.json, http…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Firstbase—none0/10

   Probes explicitly show no OpenAPI/swagger spec exists at any expected location, and no docs mention a public API spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://www.firstbase.io/openapi.json, https://www.firstbase.io/swagger.json, https://www.firstbase.…”

   proof ↗⚑ flag

   Ironclad—none0/10

   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.

   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.ironcladapp.com/openapi.json, https://developer.ironcladapp.com/swagger.json, http…”

   proof ↗⚑ flag

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

   weight 2 · round drawn
   Firstbase—none0/10

   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.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.firstbase.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.firstbase.io/openapi.json, https://www.firstbase.io/swagger.json, https://www.firstbase.…”

   proof ↗⚑ flag

   Ironclad—none0/10

   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.

   • [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
   • [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.ironcladapp.com/openapi.json, https://developer.ironcladapp.com/swagger.json, http…”

   proof ↗⚑ flag

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

   weight 2 · round to Ironclad
   Firstbase—none0/10

   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.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.firstbase.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.firstbase.io/openapi.json, https://www.firstbase.io/swagger.json, https://www.firstbase.…”

   proof ↗⚑ flag

   Ironclad~partialclaimed5/10

   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.

   • [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
   • [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
   • [claimed-docs] “Client submits an API request via Public API with request body payload to trigger an export job”
   • [claimed-docs] “Template IDs can be obtained in-app or via API”

   proof ↗⚑ flag

Compliance

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

   weight 2 · round to Firstbase
   Firstbase~partialclaimed5/10

   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.

   • [claimed-docs] “Get an instant overview of your company’s status in each state. Click on a state to view requirements, upcoming deadlines, and take any nece…”
   • [claimed-docs] “Need to expand your business to a new state? No problem. Just select a state on your compliance dashboard and we’ll take care of it for you.”
   • [claimed-docs] “Your bookkeeper is always available to answer any questions about accounting dates, deadlines, regulations.”

   proof ↗⚑ flag

   Ironclad—none0/10

   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.

   ⚑ flag

Compliance agentic

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

   weight 2 · round drawn
   Firstbase—none0/10

   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.

   • [claimed-docs] “Get an instant overview of your company’s status in each state. Click on a state to view requirements, upcoming deadlines, and take any nece…”
   • [claimed-docs] “Need to expand your business to a new state? No problem. Just select a state on your compliance dashboard and we’ll take care of it for you.”
   • [probe] “PROBE llms.txt: HTTP 404 at https://www.firstbase.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.firstbase.io/openapi.json, https://www.firstbase.io/swagger.json, https://www.firstbase.…”

   proof ↗⚑ flag

   Ironclad—none0/10

   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.

   • [claimed-docs] “Built on how contracts really move.”
   • [claimed-docs] “A New Era of Contract Intelligence | Ironclad”
   • [claimed-docs] “Ironclad's rich API can be used to connect your contract data and contracting process to your applications and internal platforms.”
   • [claimed-docs] “Technical audiences will learn how to use Ironclad's API to launch workflows.”

   proof ↗⚑ flag

Clm agentic

1. ai-native userHave an agent monitor contract renewals and deadlines through the product's API and act before they lapse

   weight 2 · round to Ironclad
   Firstbase—none0/10

   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.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.firstbase.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.firstbase.io/openapi.json, https://www.firstbase.io/swagger.json, https://www.firstbase.…”
   • [claimed-docs] “Get an instant overview of your company’s status in each state. Click on a state to view requirements, upcoming deadlines, and take any nece…”
   • [claimed-docs] “Need to expand your business to a new state? No problem. Just select a state on your compliance dashboard and we’ll take care of it for you.”

   proof ↗⚑ flag

   Ironclad~partialclaimed5/10

   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.

   • [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
   • [claimed-docs] “Webhooks allow you to specify that we should POST to your URL when certain events happen.”
   • [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
   • [claimed-docs] “Integrations can also directly control the contract process, automatically blocking or pushing forward approvals.”
   • [claimed-docs] “integrations can read and write structured data from Ironclad, leaving the specifics around updating contract language and following approva…”

   proof ↗⚑ flag

Doc api

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

   weight 3 · round to Ironclad
   Firstbase—none0/10

   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.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.firstbase.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.firstbase.io/openapi.json, https://www.firstbase.io/swagger.json, https://www.firstbase.…”

   proof ↗⚑ flag

   Ironclad~partialprobed6/10

   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.

   • [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
   • [claimed-docs] “Technical audiences will learn how to use Ironclad's API to launch workflows.”
   • [claimed-docs] “Published workflow design and Workflow Designer access: See your internal company admin for access to Workflow Designer.”
   • [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
   • [claimed-docs] “In Workflow Designer, publish the workflow you wish to launch if it has not been published already.”
   • [claimed-docs] “Template IDs can be obtained in-app or via API”
   • [claimed-docs] “Webhooks allow you to specify that we should POST to your URL when certain events happen.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.ironcladapp.com/openapi.json, https://developer.ironcladapp.com/swagger.json, http…”

   proof ↗⚑ flag

Fundraising

1. founderGenerate and sign SAFEs or convertible notes on standard terms without drafting from scratch

   weight 3 · round drawn
   Firstbase—none0/10

   Evidence covers incorporation, registered agent, banking, payroll, accounting, and tax services but contains no mention of SAFEs, convertible notes, or equity fundraising document generation.

   ⚑ flag

   Ironclad—none0/10

   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.

   • [claimed-docs] “Create Contracts in No-Code Builder”
   • [claimed-docs] “Contract Signing Has Never Been Easier”
   • [community] “What is up with the pre-loaded 'industry standard' templates? Are you guys a law firm? Do you carry malpractice insurance in case these temp…”

   proof ↗⚑ flag

Hiring

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

   weight 2 · round to Ironclad
   Firstbase—none0/10

   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.

   ⚑ flag

   Ironclad~partialcommunity3/10

   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.

   • [claimed-docs] “Create Contracts in No-Code Builder”
   • [claimed-docs] “Contract Signing Has Never Been Easier”
   • [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
   • [community] “We use IronClad at Zinc and they are amazing. Whenever we have a new contractor, we shoot them an email (actually now we click a button) and…”

   proof ↗⚑ flag

Esign

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

   weight 3 · round to Ironclad
   Firstbase—none0/10

   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.

   ⚑ flag

   Ironclad~partialclaimed6/10

   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.

   • [claimed-docs] “Contract Signing Has Never Been Easier”
   • [claimed-docs] “Contract Signing Has Never Been Easier | Ironclad”
   • [claimed-docs] “integrations can read and write structured data from Ironclad, leaving the specifics around updating contract language and following approva…”
   • [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
   • [claimed-docs] “Technical audiences will learn how to use Ironclad's API to launch workflows.”
   • [claimed-docs] “In Workflow Designer, publish the workflow you wish to launch if it has not been published already.”

   proof ↗⚑ flag

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

   weight 2 · round to Ironclad
   Firstbase—none0/10

   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.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.firstbase.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.firstbase.io/openapi.json, https://www.firstbase.io/swagger.json, https://www.firstbase.…”

   proof ↗⚑ flag

   Ironclad~partialprobed5/10

   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.

   • [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
   • [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
   • [claimed-docs] “Published workflow design and Workflow Designer access: See your internal company admin for access to Workflow Designer.”
   • [claimed-docs] “In Workflow Designer, publish the workflow you wish to launch if it has not been published already.”
   • [claimed-docs] “Create Contracts in No-Code Builder”
   • [claimed-docs] “Client submits an API request via Public API with request body payload to trigger an export job”
   • [probe] “PROBE openapi: all candidate paths 404 (https://developer.ironcladapp.com/openapi.json, https://developer.ironcladapp.com/swagger.json, http…”

   proof ↗⚑ flag

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

   weight 3 · round to Ironclad
   Firstbase—none0/10

   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.

   • [probe] “PROBE llms.txt: HTTP 404 at https://www.firstbase.io/llms.txt”
   • [probe] “PROBE openapi: all candidate paths 404 (https://www.firstbase.io/openapi.json, https://www.firstbase.io/swagger.json, https://www.firstbase.…”

   proof ↗⚑ flag

   Ironclad~partialclaimed5/10

   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.

   • [claimed-docs] “Client submits an API request via Public API with request body payload to trigger an export job”
   • [claimed-docs] “The corresponding Records API allows you to retrieve, update, and create records.”
   • [claimed-docs] “The corresponding Workflows API allows you to retrieve, create, and interact with active and completed workflows.”
   • [claimed-docs] “integrations can read and write structured data from Ironclad, leaving the specifics around updating contract language and following approva…”

   proof ↗⚑ flag

1. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Firstbase—none0/10

   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.

   ⚑ flag

   Ironclad—none0/10

   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'.

   ⚑ flag

Templates

1. founderAnswer guided questionnaires that fill in legal documents correctly and flag choices that need attorney review

   weight 1 · round to Ironclad
   Firstbase—none0/10

   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.

   ⚑ flag

   Ironclad~partialcommunity3/10

   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.

   • [claimed-docs] “Create Contracts in No-Code Builder”
   • [claimed-docs] “Create Contracts in No-Code Builder | Ironclad”
   • [claimed-docs] “Published workflow design and Workflow Designer access: See your internal company admin for access to Workflow Designer.”
   • [claimed-docs] “In Workflow Designer, publish the workflow you wish to launch if it has not been published already.”
   • [community] “This appears to be the unauthorized practice of law... I'll give you guys a week to rethink your service and get a lawyer on board, but next…”
   • [community] “What is up with the pre-loaded 'industry standard' templates? Are you guys a law firm? Do you carry malpractice insurance in case these temp…”
   • [community] “Full disclosure: Actual flesh-and-blood lawyer here. These tools are great when things are going well... you might be pushing off minor expe…”

   proof ↗⚑ flag

2. founderStart from a library of vetted standard legal templates (NDAs, agreements, policies) instead of hiring counsel for routine documents

   weight 2 · round to Ironclad
   Firstbase—none0/10

   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.

   ⚑ flag

   Ironclad!disputedcontradicted3/10

   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.

   • [claimed-docs] “Create Contracts in No-Code Builder”
   • [claimed-docs] “Create Contracts in No-Code Builder | Ironclad”
   • [community] “This appears to be the unauthorized practice of law... I'll give you guys a week to rethink your service and get a lawyer on board, but next…”
   • [community] “What is up with the pre-loaded 'industry standard' templates? Are you guys a law firm? Do you carry malpractice insurance in case these temp…”
   • [community] “Hey everyone, thanks a ton for your comments and interest. Now that we've had a chance to get some feedback, we'll be closing up the site wh…”
   • [community] “Full disclosure: Actual flesh-and-blood lawyer here. These tools are great when things are going well... you might be pushing off minor expe…”

   proof ↗⚑ flag