Clerky vs Firstbase

Agent access

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

   weight 2 · round to Clerky
   Clerky✓fullprobed9/10

   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.

   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.clerky.com/llms.txt - [Lifecycle](https://developers.clerky.com/getting-started/lifecycle/ind…”
   • [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
   • [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”

   proof ↗⚑ flag

   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

2. ai-native userUse an official CLI

   weight 2 · round drawn
   Clerky—none0/10

   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.

   • [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
   • [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
   • [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.clerky.com/llms.txt - [Lifecycle](https://developers.clerky.com/getting-started/lifecycle/ind…”

   proof ↗⚑ flag

   Firstbase—none0/10

   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.

   ⚑ flag

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

   weight 3 · round to Clerky
   Clerky~partialprobed6/10

   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.

   • [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
   • [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
   • [claimed-docs] “# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scop…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.clerky.com/llms.txt - [Lifecycle](https://developers.clerky.com/getting-started/lifecycle/ind…”

   proof ↗⚑ flag

   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

4. ai-native userBuild against official SDKs

   weight 2 · round to Clerky
   Clerky~partialprobed5/10

   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.

   • [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
   • [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
   • [claimed-docs] “# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scop…”
   • [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.clerky.com/llms.txt - [Lifecycle](https://developers.clerky.com/getting-started/lifecycle/ind…”
   • [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”

   proof ↗⚑ flag

   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

5. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Clerky—none0/10

   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.

   • [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
   • [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”

   proof ↗⚑ flag

   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

Agentic features

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

   weight 2 · round drawn
   Clerky—none0/10

   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.

   • [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
   • [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Clerky—none0/10

   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.

   • [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
   • [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”
   • [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
   • [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Clerky
   Clerky~partialprobed7/10

   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.

   • [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
   • [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.clerky.com/llms.txt - [Lifecycle](https://developers.clerky.com/getting-started/lifecycle/ind…”

   proof ↗⚑ flag

   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

Api quality

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

   weight 2 · round drawn
   Clerky—none0/10

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

   • [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
   • [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
   • [claimed-docs] “# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scop…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://handbooks.clerky.com/openapi.json, https://handbooks.clerky.com/swagger.json, https://handbo…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.clerky.com/llms.txt - [Lifecycle](https://developers.clerky.com/getting-started/lifecycle/ind…”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Clerky—none0/10

   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.

   • [probe] “PROBE openapi: all candidate paths 404 (https://handbooks.clerky.com/openapi.json, https://handbooks.clerky.com/swagger.json, https://handbo…”
   • [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
   • [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Clerky—none0/10

   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.

   • [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
   • [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
   • [claimed-docs] “# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scop…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://handbooks.clerky.com/openapi.json, https://handbooks.clerky.com/swagger.json, https://handbo…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.clerky.com/llms.txt - [Lifecycle](https://developers.clerky.com/getting-started/lifecycle/ind…”

   proof ↗⚑ flag

   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

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

   weight 2 · round drawn
   Clerky—none0/10

   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.

   • [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
   • [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
   • [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
   • [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”

   proof ↗⚑ flag

   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

Compliance

1. founderFile annual reports and franchise tax on time through the platform

   weight 2 · round to Firstbase
   Clerky—none0/10

   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.

   ⚑ flag

   Firstbase~partialcommunity6/10

   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.

   • [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] “Register for Payroll™ to compliantly hire remote employees, process payroll, and file tax returns. Available in all 50 states.”
   • [claimed-docs] “Subscribe by April 15 and we'll file an extension form ASAP”
   • [community] “Used Firstbase, it's cheaper and took me 2 weeks to get up and running. From Uganda. Firstbase supports Stripe, sets up US bank account with…”

   proof ↗⚑ flag

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

   weight 2 · round to Firstbase
   Clerky—none0/10

   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.

   ⚑ flag

   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

3. founderUse the platform as my registered agent and receive scanned legal mail and service of process digitally

   weight 2 · round to Firstbase
   Clerky—none0/10

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

   ⚑ flag

   Firstbase✓fullclaimed7/10

   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.

   • [claimed-docs] “Appoint Firstbase as your Registered Agent — or switch if you already have one — and forget the stress of staying compliant.”
   • [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] “We’ll manage all your mail and securely convert them into easily viewable, high-resolution PDFs. Any action you can perform with email, you …”

   proof ↗⚑ flag

Compliance agentic

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

   weight 2 · round to Clerky
   Clerky~partialprobed4/10

   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.

   • [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
   • [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
   • [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
   • [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”
   • [claimed-docs] “Use Clerky to complete IRS forms and submit them to the IRS, completely online. No need for a fax machine.”
   • [claimed-docs] “Use Clerky to complete IRS forms and submit them to the IRS, completely online. No need for a fax machine. 100% in-house, not outsourced.”

   proof ↗⚑ flag

   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

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 drawn
   Clerky—none0/10

   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.

   • [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
   • [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
   • [claimed-docs] “# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/…”
   • [probe] “PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gat…”

   proof ↗⚑ flag

   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

Doc api

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

   weight 3 · round to Clerky
   Clerky~partialprobed5/10

   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.

   • [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
   • [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
   • [claimed-docs] “# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scop…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://developers.clerky.com/llms.txt - [Lifecycle](https://developers.clerky.com/getting-started/lifecycle/ind…”

   proof ↗⚑ flag

   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

Fundraising

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

   weight 3 · round to Clerky
   Clerky✓fullcommunity8/10

   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.

   • [claimed-docs] “Issue safes or convertible notes. Hire employees, consultants, and advisors, and issue stock or stock options as equity compensation.”
   • [claimed-docs] “Our software makes it easy to customize the key terms of the legal paperwork you're working on.”
   • [claimed-docs] “you can easily loop in your attorney to have them review and comment on the information you're entering.”
   • [claimed-docs] “Our software makes it easy to invite other people to collaborate on a document set, in real-time.”
   • [community] “Wow, this is great. Props to the Clerky team. If this had existed in 2015 we would have used it, instead we paid a few thousand extra.”
   • [community] “We were among the first companies to use this product at Crowdbotics... the process was almost totally frictionless and Clerky's support was…”

   proof ↗⚑ flag

   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

Hiring

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

   weight 2 · round to Clerky
   Clerky✓fullcommunity8/10

   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.

   • [claimed-docs] “Issue safes or convertible notes. Hire employees, consultants, and advisors, and issue stock or stock options as equity compensation.”
   • [claimed-docs] “Adopt a stock plan to easily issue restricted stock or stock options to employees, consultants, and advisors.”
   • [claimed-docs] “Forming a startup on Clerky enables access to a legal dashboard that makes it easy to do additional legal paperwork.”
   • [claimed-docs] “you can easily loop in your attorney to have them review and comment on the information you're entering.”
   • [community] “Clerky gives me management tools (including the post-incorporation package: Fundraising, Hiring and Maintenance) although this does not give…”

   proof ↗⚑ flag

   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

Esign

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

   weight 3 · round to Clerky
   Clerky~partialclaimed4/10

   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.

   • [claimed-docs] “Our software makes it easy to invite other people to collaborate on a document set, in real-time.”
   • [claimed-docs] “Our software makes it easy to invite other people to collaborate on a document set, in real-time. Rest easy knowing everyone is looking at t…”
   • [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
   • [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”

   proof ↗⚑ flag

   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

Formation

1. founderObtain a federal EIN for my new company through the platform

   weight 2 · round to Clerky
   Clerky✓fullcommunity8/10

   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.

   • [claimed-docs] “Use Clerky to complete IRS forms and submit them to the IRS, completely online. No need for a fax machine.”
   • [claimed-docs] “Use Clerky to complete IRS forms and submit them to the IRS, completely online. No need for a fax machine. 100% in-house, not outsourced.”
   • [community] “We were among the first companies to use this product at Crowdbotics... the process was almost totally frictionless and Clerky's support was…”

   proof ↗⚑ flag

   Firstbase—none0/10

   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.

   • [claimed-docs] “Open a business bank account without an EIN\*”

   proof ↗⚑ flag

2. founderIncorporate a Delaware startup end-to-end online, including the filing, bylaws, and initial board approvals

   weight 3 · round to Clerky
   Clerky✓fullcommunity8/10

   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.

   • [claimed-docs] “Forming a startup on Clerky enables access to a legal dashboard that makes it easy to do additional legal paperwork.”
   • [claimed-docs] “Our software makes it easy to customize the key terms of the legal paperwork you're working on.”
   • [claimed-docs] “Issue safes or convertible notes. Hire employees, consultants, and advisors, and issue stock or stock options as equity compensation.”
   • [claimed-docs] “Adopt a stock plan to easily issue restricted stock or stock options to employees, consultants, and advisors.”
   • [community] “I used Clerky in 2016. I found them pleasant and easy to work with. Took the time to answer all of my questions. Prices quite reasonable.”
   • [community] “We were among the first companies to use this product at Crowdbotics... the process was almost totally frictionless and Clerky's support was…”
   • [community] “I love Stripe Atlas overall for fast/excellent UX, but Clerky supports PBCs and a higher degree of customization (eg useful for incorporatin…”

   proof ↗⚑ flag

   Firstbase~partialcommunity3/10

   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.

   • [claimed-docs] “Open a business bank account without an EIN\*”
   • [community] “Used Firstbase, it's cheaper and took me 2 weeks to get up and running. From Uganda. Firstbase supports Stripe, sets up US bank account with…”

   proof ↗⚑ flag

3. founderComplete post-incorporation setup — founder stock purchases, IP assignment, and 83(b) elections — with correct standard paperwork

   weight 2 · round to Clerky
   Clerky~partialcommunity7/10

   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.

   • [claimed-docs] “Use Clerky to complete IRS forms and submit them to the IRS, completely online. No need for a fax machine.”
   • [claimed-docs] “Issue safes or convertible notes. Hire employees, consultants, and advisors, and issue stock or stock options as equity compensation.”
   • [claimed-docs] “Use Clerky to complete IRS forms and submit them to the IRS, completely online. No need for a fax machine. 100% in-house, not outsourced.”
   • [claimed-docs] “Adopt a stock plan to easily issue restricted stock or stock options to employees, consultants, and advisors.”
   • [community] “Clerky gives me management tools (including the post-incorporation package: Fundraising, Hiring and Maintenance) although this does not give…”

   proof ↗⚑ flag

   Firstbase—none0/10

   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.

   ⚑ flag

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

   weight 2 · round to Clerky
   Clerky~partialclaimed4/10

   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.

   • [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
   • [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
   • [claimed-docs] “# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scop…”
   • [claimed-docs] “Issue safes or convertible notes. Hire employees, consultants, and advisors, and issue stock or stock options as equity compensation.”
   • [claimed-docs] “Attorney accounts get access to over 40 advanced products that are not publicly available.”
   • [claimed-docs] “Apply for accounts with the most popular banks for startups. Pre-filled applications make it as easy as possible.”

   proof ↗⚑ flag

   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

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

   weight 3 · round drawn
   Clerky—none0/10

   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.

   • [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
   • [claimed-docs] “# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scop…”
   • [probe] “PROBE llms.txt: HTTP 404 at https://handbooks.clerky.com/llms.txt”
   • [probe] “PROBE docs-md: HTTP 404 at https://handbooks.clerky.com/legal-concepts.md”
   • [probe] “PROBE openapi: all candidate paths 404 (https://handbooks.clerky.com/openapi.json, https://handbooks.clerky.com/swagger.json, https://handbo…”

   proof ↗⚑ flag

   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

1. ai-native userControl data retention and deletion

   weight 2 · round drawn
   Clerky—none0/10

   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.

   ⚑ flag

   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

Templates

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

   weight 1 · round to Clerky
   Clerky~partialclaimed6/10

   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.

   • [claimed-docs] “# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports …”
   • [claimed-docs] “# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those v…”
   • [claimed-docs] “Our software makes it easy to customize the key terms of the legal paperwork you're working on.”
   • [claimed-docs] “you can easily loop in your attorney to have them review and comment on the information you're entering.”
   • [claimed-docs] “Our software makes it easy to invite other people to collaborate on a document set, in real-time.”

   proof ↗⚑ flag

   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

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

   weight 2 · round to Clerky
   Clerky~partialcommunity5/10

   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.

   • [claimed-docs] “Issue safes or convertible notes. Hire employees, consultants, and advisors, and issue stock or stock options as equity compensation.”
   • [claimed-docs] “Adopt a stock plan to easily issue restricted stock or stock options to employees, consultants, and advisors.”
   • [claimed-docs] “Use Clerky to complete IRS forms and submit them to the IRS, completely online. No need for a fax machine.”
   • [claimed-docs] “Our software makes it easy to customize the key terms of the legal paperwork you're working on.”
   • [community] “Clerky gives me management tools (including the post-incorporation package: Fundraising, Hiring and Maintenance) although this does not give…”

   proof ↗⚑ flag

   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