Skip to content
ProductArena

How Clerky’s scores are calculated

The full audit trail, recomputed from the verdict data at build time through the same code that produced the leaderboard: verdict × quality × story weight per cell, cells sum to dimension scores, dimensions blend into the PA Score. Every number on the product page is reproducible from this page alone; for why the formula looks like this, see the methodology.

verdict factors: full ×1.0 · partial ×0.6 · disputed ×0.3 · none ×0.0 · n/a excluded from both sides · cell points = weight × quality × factor · cell max = weight × 10

PA Score14/100

Agent-ready 37.3 × 0.30 = 11.19

API quality 0.0 × 0.20 = 0.00

Openness 6.9 × 0.20 = 1.38

Built-in AI 9.3 × 0.15 = 1.40

Automation 0.0 × 0.15 = 0.00

(11.19 + 0.00 + 1.38 + 1.40 + 0.00) ÷ (0.30 + 0.20 + 0.20 + 0.15 + 0.15) = 13.96 ÷ 1.00 = 14.0

Scores are stored to 1 decimal; the product page’s pills round to whole numbers for display. Each dimension below shows the stories, verdicts, and cited evidence behind its number.

Agent-ready37.3/100×0.30 of the PA blend

Outside-in: can YOUR agent reach and drive this product — API, MCP, CLI, headless runs, agent docs.

Point an agent at llms.txt or agent-oriented docsweight 2

2 (weight) × 9 (quality) × 1.0 (full) = 18.0 of 20 max

  • [probe] https://developers.clerky.com/llms.txt“PROBE llms.txt: HTTP 200 at https://developers.clerky.com/llms.txt - [Lifecycle](https://developers.clerky.com/getting-started/lifecycle/index.md): How a partner creates, fills, and tracks a document set. - [Introduction](https://developers.clerky.com/getting-started/introduction/index.md): Overview of the Clerky Partner API. - [Authentication](https://developers.clerky.com/getting-started/authentication/index.md): How partner applications authenticate to the Cle”
  • [claimed-docs] https://developers.clerky.com/getting-started/introduction/index.md“# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports Delaware C-Corporation formations. Your product creates a document set, renders the forms the API returns, submits JSON values, and polls for lifecycle state. Users enter formation information in your product and sign documents on Clerky. ## Concepts - **Document set**: the unit of work. It bundles the documents, signatures, and filings for one entity formation. - **Form**: describes a set of data to collect. Each carries a `json_schema` (the field”
  • [claimed-docs] https://developers.clerky.com/getting-started/lifecycle/index.md“# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those values, and poll for state. Your product owns data collection and progress display; Clerky handles signing and formation work. ## Workflow | Step | Your product does this | API surface | | --- | --- | --- | | 1 | Create a document set from a template. | [`POST /v1/document_sets`][start-document-set] | | 2 | Render the forms that need values. | [`GET /v1/document_sets/{id}/forms`][list-document-set-forms] | | 3 | Submit JSON values to the returned action”

Run the product headlessly / in CI for automationweight 2

2 (weight) × 3 (quality) × 0.6 (partial) = 3.6 of 20 max

  • [claimed-docs] https://developers.clerky.com/getting-started/introduction/index.md“# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports Delaware C-Corporation formations. Your product creates a document set, renders the forms the API returns, submits JSON values, and polls for lifecycle state. Users enter formation information in your product and sign documents on Clerky. ## Concepts - **Document set**: the unit of work. It bundles the documents, signatures, and filings for one entity formation. - **Form**: describes a set of data to collect. Each carries a `json_schema` (the field”
  • [claimed-docs] https://developers.clerky.com/getting-started/lifecycle/index.md“# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those values, and poll for state. Your product owns data collection and progress display; Clerky handles signing and formation work. ## Workflow | Step | Your product does this | API surface | | --- | --- | --- | | 1 | Create a document set from a template. | [`POST /v1/document_sets`][start-document-set] | | 2 | Render the forms that need values. | [`GET /v1/document_sets/{id}/forms`][list-document-set-forms] | | 3 | Submit JSON values to the returned action”
  • [claimed-docs] https://developers.clerky.com/getting-started/authentication/index.md“# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scopes, token lifetime, and refresh behavior will be published before partner integrations launch. ## Authorization flow The Partner API will use the authorization code flow: 1. Redirect the user to Clerky. 2. The user signs in and authorizes access. 3. Clerky redirects back with an authorization code. 4. Your server exchanges the code for an access token. 5. Your server sends the token with Partner API requests. ## Access model Each token is limited by”

Plug MCP servers into this product so it can use their toolsweight 3

n/a — not applicable to this product: excluded from numerator and denominator

  • [claimed-docs] https://developers.clerky.com/mcp-server/index.md“# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/getting-started/intro) servers, including Claude and ChatGPT. Once connected, the assistant can use available Clerky MCP tools with the team access you authorize. The MCP server URL is: ```text https://mcp.clerky.com/mcp ``` Jump to the setup instructions for your AI tool: - [Claude](#claude) - [ChatGPT](#chatgpt) - [Other AI assistants](#other-ai-assistants) ## Before You Begin Make sure you have: - A Clerky account you can sign in with. - Access to the C”
  • [probe] https://mcp.clerky.com/mcp“PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gated remote MCP server, per docs read-only tools with team-scoped access”

Connect an agent via an official MCP serverweight 3

3 (weight) × 8 (quality) × 1.0 (full) = 24.0 of 30 max

  • [claimed-docs] https://developers.clerky.com/mcp-server/index.md“# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/getting-started/intro) servers, including Claude and ChatGPT. Once connected, the assistant can use available Clerky MCP tools with the team access you authorize. The MCP server URL is: ```text https://mcp.clerky.com/mcp ``` Jump to the setup instructions for your AI tool: - [Claude](#claude) - [ChatGPT](#chatgpt) - [Other AI assistants](#other-ai-assistants) ## Before You Begin Make sure you have: - A Clerky account you can sign in with. - Access to the C”
  • [probe] https://mcp.clerky.com/mcp“PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gated remote MCP server, per docs read-only tools with team-scoped access”
  • [claimed-docs] https://developers.clerky.com/getting-started/authentication/index.md“# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scopes, token lifetime, and refresh behavior will be published before partner integrations launch. ## Authorization flow The Partner API will use the authorization code flow: 1. Redirect the user to Clerky. 2. The user signs in and authorizes access. 3. Clerky redirects back with an authorization code. 4. Your server exchanges the code for an access token. 5. Your server sends the token with Partner API requests. ## Access model Each token is limited by”

Use an official CLIweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

  • [claimed-docs] https://developers.clerky.com/getting-started/introduction/index.md“# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports Delaware C-Corporation formations. Your product creates a document set, renders the forms the API returns, submits JSON values, and polls for lifecycle state. Users enter formation information in your product and sign documents on Clerky. ## Concepts - **Document set**: the unit of work. It bundles the documents, signatures, and filings for one entity formation. - **Form**: describes a set of data to collect. Each carries a `json_schema` (the field”
  • [claimed-docs] https://developers.clerky.com/getting-started/lifecycle/index.md“# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those values, and poll for state. Your product owns data collection and progress display; Clerky handles signing and formation work. ## Workflow | Step | Your product does this | API surface | | --- | --- | --- | | 1 | Create a document set from a template. | [`POST /v1/document_sets`][start-document-set] | | 2 | Render the forms that need values. | [`GET /v1/document_sets/{id}/forms`][list-document-set-forms] | | 3 | Submit JSON values to the returned action”
  • [claimed-docs] https://developers.clerky.com/mcp-server/index.md“# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/getting-started/intro) servers, including Claude and ChatGPT. Once connected, the assistant can use available Clerky MCP tools with the team access you authorize. The MCP server URL is: ```text https://mcp.clerky.com/mcp ``` Jump to the setup instructions for your AI tool: - [Claude](#claude) - [ChatGPT](#chatgpt) - [Other AI assistants](#other-ai-assistants) ## Before You Begin Make sure you have: - A Clerky account you can sign in with. - Access to the C”
  • [probe] https://developers.clerky.com/llms.txt“PROBE llms.txt: HTTP 200 at https://developers.clerky.com/llms.txt - [Lifecycle](https://developers.clerky.com/getting-started/lifecycle/index.md): How a partner creates, fills, and tracks a document set. - [Introduction](https://developers.clerky.com/getting-started/introduction/index.md): Overview of the Clerky Partner API. - [Authentication](https://developers.clerky.com/getting-started/authentication/index.md): How partner applications authenticate to the Cle”

Drive the product through a documented public APIweight 3

3 (weight) × 6 (quality) × 0.6 (partial) = 10.8 of 30 max

  • [claimed-docs] https://developers.clerky.com/getting-started/introduction/index.md“# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports Delaware C-Corporation formations. Your product creates a document set, renders the forms the API returns, submits JSON values, and polls for lifecycle state. Users enter formation information in your product and sign documents on Clerky. ## Concepts - **Document set**: the unit of work. It bundles the documents, signatures, and filings for one entity formation. - **Form**: describes a set of data to collect. Each carries a `json_schema` (the field”
  • [claimed-docs] https://developers.clerky.com/getting-started/lifecycle/index.md“# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those values, and poll for state. Your product owns data collection and progress display; Clerky handles signing and formation work. ## Workflow | Step | Your product does this | API surface | | --- | --- | --- | | 1 | Create a document set from a template. | [`POST /v1/document_sets`][start-document-set] | | 2 | Render the forms that need values. | [`GET /v1/document_sets/{id}/forms`][list-document-set-forms] | | 3 | Submit JSON values to the returned action”
  • [claimed-docs] https://developers.clerky.com/getting-started/authentication/index.md“# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scopes, token lifetime, and refresh behavior will be published before partner integrations launch. ## Authorization flow The Partner API will use the authorization code flow: 1. Redirect the user to Clerky. 2. The user signs in and authorizes access. 3. Clerky redirects back with an authorization code. 4. Your server exchanges the code for an access token. 5. Your server sends the token with Partner API requests. ## Access model Each token is limited by”
  • [probe] https://developers.clerky.com/llms.txt“PROBE llms.txt: HTTP 200 at https://developers.clerky.com/llms.txt - [Lifecycle](https://developers.clerky.com/getting-started/lifecycle/index.md): How a partner creates, fills, and tracks a document set. - [Introduction](https://developers.clerky.com/getting-started/introduction/index.md): Overview of the Clerky Partner API. - [Authentication](https://developers.clerky.com/getting-started/authentication/index.md): How partner applications authenticate to the Cle”

Issue scoped/least-privilege API credentials for an agentweight 2

2 (weight) × 4 (quality) × 0.6 (partial) = 4.8 of 20 max

  • [claimed-docs] https://developers.clerky.com/getting-started/authentication/index.md“# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scopes, token lifetime, and refresh behavior will be published before partner integrations launch. ## Authorization flow The Partner API will use the authorization code flow: 1. Redirect the user to Clerky. 2. The user signs in and authorizes access. 3. Clerky redirects back with an authorization code. 4. Your server exchanges the code for an access token. 5. Your server sends the token with Partner API requests. ## Access model Each token is limited by”
  • [claimed-docs] https://developers.clerky.com/mcp-server/index.md“# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/getting-started/intro) servers, including Claude and ChatGPT. Once connected, the assistant can use available Clerky MCP tools with the team access you authorize. The MCP server URL is: ```text https://mcp.clerky.com/mcp ``` Jump to the setup instructions for your AI tool: - [Claude](#claude) - [ChatGPT](#chatgpt) - [Other AI assistants](#other-ai-assistants) ## Before You Begin Make sure you have: - A Clerky account you can sign in with. - Access to the C”
  • [probe] https://mcp.clerky.com/mcp“PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gated remote MCP server, per docs read-only tools with team-scoped access”

Build against official SDKsweight 2

2 (weight) × 5 (quality) × 0.6 (partial) = 6.0 of 20 max

  • [claimed-docs] https://developers.clerky.com/getting-started/introduction/index.md“# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports Delaware C-Corporation formations. Your product creates a document set, renders the forms the API returns, submits JSON values, and polls for lifecycle state. Users enter formation information in your product and sign documents on Clerky. ## Concepts - **Document set**: the unit of work. It bundles the documents, signatures, and filings for one entity formation. - **Form**: describes a set of data to collect. Each carries a `json_schema` (the field”
  • [claimed-docs] https://developers.clerky.com/getting-started/lifecycle/index.md“# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those values, and poll for state. Your product owns data collection and progress display; Clerky handles signing and formation work. ## Workflow | Step | Your product does this | API surface | | --- | --- | --- | | 1 | Create a document set from a template. | [`POST /v1/document_sets`][start-document-set] | | 2 | Render the forms that need values. | [`GET /v1/document_sets/{id}/forms`][list-document-set-forms] | | 3 | Submit JSON values to the returned action”
  • [claimed-docs] https://developers.clerky.com/getting-started/authentication/index.md“# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scopes, token lifetime, and refresh behavior will be published before partner integrations launch. ## Authorization flow The Partner API will use the authorization code flow: 1. Redirect the user to Clerky. 2. The user signs in and authorizes access. 3. Clerky redirects back with an authorization code. 4. Your server exchanges the code for an access token. 5. Your server sends the token with Partner API requests. ## Access model Each token is limited by”
  • [claimed-docs] https://developers.clerky.com/mcp-server/index.md“# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/getting-started/intro) servers, including Claude and ChatGPT. Once connected, the assistant can use available Clerky MCP tools with the team access you authorize. The MCP server URL is: ```text https://mcp.clerky.com/mcp ``` Jump to the setup instructions for your AI tool: - [Claude](#claude) - [ChatGPT](#chatgpt) - [Other AI assistants](#other-ai-assistants) ## Before You Begin Make sure you have: - A Clerky account you can sign in with. - Access to the C”
  • [probe] https://developers.clerky.com/llms.txt“PROBE llms.txt: HTTP 200 at https://developers.clerky.com/llms.txt - [Lifecycle](https://developers.clerky.com/getting-started/lifecycle/index.md): How a partner creates, fills, and tracks a document set. - [Introduction](https://developers.clerky.com/getting-started/introduction/index.md): Overview of the Clerky Partner API. - [Authentication](https://developers.clerky.com/getting-started/authentication/index.md): How partner applications authenticate to the Cle”
  • [probe] https://mcp.clerky.com/mcp“PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gated remote MCP server, per docs read-only tools with team-scoped access”

Subscribe to events via webhooksweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

  • [claimed-docs] https://developers.clerky.com/getting-started/lifecycle/index.md“# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those values, and poll for state. Your product owns data collection and progress display; Clerky handles signing and formation work. ## Workflow | Step | Your product does this | API surface | | --- | --- | --- | | 1 | Create a document set from a template. | [`POST /v1/document_sets`][start-document-set] | | 2 | Render the forms that need values. | [`GET /v1/document_sets/{id}/forms`][list-document-set-forms] | | 3 | Submit JSON values to the returned action”
  • [claimed-docs] https://developers.clerky.com/getting-started/introduction/index.md“# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports Delaware C-Corporation formations. Your product creates a document set, renders the forms the API returns, submits JSON values, and polls for lifecycle state. Users enter formation information in your product and sign documents on Clerky. ## Concepts - **Document set**: the unit of work. It bundles the documents, signatures, and filings for one entity formation. - **Form**: describes a set of data to collect. Each carries a `json_schema` (the field”

Agent-ready = 67.2 ÷ 180 × 100 = 37.3

API quality0.0/100×0.20 of the PA blend

The programmable surface once an agent is there — machine-readable spec, interactive docs, sandbox, versioning discipline.

Explore an interactive API reference with runnable examplesweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

  • [claimed-docs] https://developers.clerky.com/getting-started/introduction/index.md“# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports Delaware C-Corporation formations. Your product creates a document set, renders the forms the API returns, submits JSON values, and polls for lifecycle state. Users enter formation information in your product and sign documents on Clerky. ## Concepts - **Document set**: the unit of work. It bundles the documents, signatures, and filings for one entity formation. - **Form**: describes a set of data to collect. Each carries a `json_schema` (the field”
  • [claimed-docs] https://developers.clerky.com/getting-started/lifecycle/index.md“# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those values, and poll for state. Your product owns data collection and progress display; Clerky handles signing and formation work. ## Workflow | Step | Your product does this | API surface | | --- | --- | --- | | 1 | Create a document set from a template. | [`POST /v1/document_sets`][start-document-set] | | 2 | Render the forms that need values. | [`GET /v1/document_sets/{id}/forms`][list-document-set-forms] | | 3 | Submit JSON values to the returned action”
  • [claimed-docs] https://developers.clerky.com/getting-started/authentication/index.md“# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scopes, token lifetime, and refresh behavior will be published before partner integrations launch. ## Authorization flow The Partner API will use the authorization code flow: 1. Redirect the user to Clerky. 2. The user signs in and authorizes access. 3. Clerky redirects back with an authorization code. 4. Your server exchanges the code for an access token. 5. Your server sends the token with Partner API requests. ## Access model Each token is limited by”
  • [probe] https://handbooks.clerky.com/openapi.json“PROBE openapi: all candidate paths 404 (https://handbooks.clerky.com/openapi.json, https://handbooks.clerky.com/swagger.json, https://handbooks.clerky.com/api/openapi.json, https://handbooks.clerky.com/.well-known/openapi.json)”
  • [probe] https://developers.clerky.com/llms.txt“PROBE llms.txt: HTTP 200 at https://developers.clerky.com/llms.txt - [Lifecycle](https://developers.clerky.com/getting-started/lifecycle/index.md): How a partner creates, fills, and tracks a document set. - [Introduction](https://developers.clerky.com/getting-started/introduction/index.md): Overview of the Clerky Partner API. - [Authentication](https://developers.clerky.com/getting-started/authentication/index.md): How partner applications authenticate to the Cle”

Download a machine-readable API spec (OpenAPI or equivalent)weight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

  • [probe] https://handbooks.clerky.com/openapi.json“PROBE openapi: all candidate paths 404 (https://handbooks.clerky.com/openapi.json, https://handbooks.clerky.com/swagger.json, https://handbooks.clerky.com/api/openapi.json, https://handbooks.clerky.com/.well-known/openapi.json)”
  • [claimed-docs] https://developers.clerky.com/getting-started/introduction/index.md“# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports Delaware C-Corporation formations. Your product creates a document set, renders the forms the API returns, submits JSON values, and polls for lifecycle state. Users enter formation information in your product and sign documents on Clerky. ## Concepts - **Document set**: the unit of work. It bundles the documents, signatures, and filings for one entity formation. - **Form**: describes a set of data to collect. Each carries a `json_schema` (the field”
  • [claimed-docs] https://developers.clerky.com/getting-started/lifecycle/index.md“# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those values, and poll for state. Your product owns data collection and progress display; Clerky handles signing and formation work. ## Workflow | Step | Your product does this | API surface | | --- | --- | --- | | 1 | Create a document set from a template. | [`POST /v1/document_sets`][start-document-set] | | 2 | Render the forms that need values. | [`GET /v1/document_sets/{id}/forms`][list-document-set-forms] | | 3 | Submit JSON values to the returned action”

Test against a sandbox environment without touching production dataweight 1

1 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 10 max

  • [claimed-docs] https://developers.clerky.com/getting-started/introduction/index.md“# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports Delaware C-Corporation formations. Your product creates a document set, renders the forms the API returns, submits JSON values, and polls for lifecycle state. Users enter formation information in your product and sign documents on Clerky. ## Concepts - **Document set**: the unit of work. It bundles the documents, signatures, and filings for one entity formation. - **Form**: describes a set of data to collect. Each carries a `json_schema` (the field”
  • [claimed-docs] https://developers.clerky.com/getting-started/lifecycle/index.md“# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those values, and poll for state. Your product owns data collection and progress display; Clerky handles signing and formation work. ## Workflow | Step | Your product does this | API surface | | --- | --- | --- | | 1 | Create a document set from a template. | [`POST /v1/document_sets`][start-document-set] | | 2 | Render the forms that need values. | [`GET /v1/document_sets/{id}/forms`][list-document-set-forms] | | 3 | Submit JSON values to the returned action”
  • [claimed-docs] https://developers.clerky.com/getting-started/authentication/index.md“# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scopes, token lifetime, and refresh behavior will be published before partner integrations launch. ## Authorization flow The Partner API will use the authorization code flow: 1. Redirect the user to Clerky. 2. The user signs in and authorizes access. 3. Clerky redirects back with an authorization code. 4. Your server exchanges the code for an access token. 5. Your server sends the token with Partner API requests. ## Access model Each token is limited by”
  • [claimed-docs] https://developers.clerky.com/mcp-server/index.md“# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/getting-started/intro) servers, including Claude and ChatGPT. Once connected, the assistant can use available Clerky MCP tools with the team access you authorize. The MCP server URL is: ```text https://mcp.clerky.com/mcp ``` Jump to the setup instructions for your AI tool: - [Claude](#claude) - [ChatGPT](#chatgpt) - [Other AI assistants](#other-ai-assistants) ## Before You Begin Make sure you have: - A Clerky account you can sign in with. - Access to the C”
  • [probe] https://mcp.clerky.com/mcp“PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gated remote MCP server, per docs read-only tools with team-scoped access”

Rely on versioned APIs with a documented deprecation policyweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

  • [claimed-docs] https://developers.clerky.com/getting-started/introduction/index.md“# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports Delaware C-Corporation formations. Your product creates a document set, renders the forms the API returns, submits JSON values, and polls for lifecycle state. Users enter formation information in your product and sign documents on Clerky. ## Concepts - **Document set**: the unit of work. It bundles the documents, signatures, and filings for one entity formation. - **Form**: describes a set of data to collect. Each carries a `json_schema` (the field”
  • [claimed-docs] https://developers.clerky.com/getting-started/lifecycle/index.md“# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those values, and poll for state. Your product owns data collection and progress display; Clerky handles signing and formation work. ## Workflow | Step | Your product does this | API surface | | --- | --- | --- | | 1 | Create a document set from a template. | [`POST /v1/document_sets`][start-document-set] | | 2 | Render the forms that need values. | [`GET /v1/document_sets/{id}/forms`][list-document-set-forms] | | 3 | Submit JSON values to the returned action”
  • [claimed-docs] https://developers.clerky.com/getting-started/authentication/index.md“# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scopes, token lifetime, and refresh behavior will be published before partner integrations launch. ## Authorization flow The Partner API will use the authorization code flow: 1. Redirect the user to Clerky. 2. The user signs in and authorizes access. 3. Clerky redirects back with an authorization code. 4. Your server exchanges the code for an access token. 5. Your server sends the token with Partner API requests. ## Access model Each token is limited by”
  • [probe] https://handbooks.clerky.com/openapi.json“PROBE openapi: all candidate paths 404 (https://handbooks.clerky.com/openapi.json, https://handbooks.clerky.com/swagger.json, https://handbooks.clerky.com/api/openapi.json, https://handbooks.clerky.com/.well-known/openapi.json)”
  • [probe] https://developers.clerky.com/llms.txt“PROBE llms.txt: HTTP 200 at https://developers.clerky.com/llms.txt - [Lifecycle](https://developers.clerky.com/getting-started/lifecycle/index.md): How a partner creates, fills, and tracks a document set. - [Introduction](https://developers.clerky.com/getting-started/introduction/index.md): Overview of the Clerky Partner API. - [Authentication](https://developers.clerky.com/getting-started/authentication/index.md): How partner applications authenticate to the Cle”

API quality = 0.0 ÷ 70 × 100 = 0.0

Openness6.9/100×0.20 of the PA blend

Can you leave, inspect, or self-host — data export, open source, portability.

Do everything through the API that I can do in the UIweight 2

2 (weight) × 4 (quality) × 0.6 (partial) = 4.8 of 20 max

  • [claimed-docs] https://developers.clerky.com/getting-started/introduction/index.md“# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports Delaware C-Corporation formations. Your product creates a document set, renders the forms the API returns, submits JSON values, and polls for lifecycle state. Users enter formation information in your product and sign documents on Clerky. ## Concepts - **Document set**: the unit of work. It bundles the documents, signatures, and filings for one entity formation. - **Form**: describes a set of data to collect. Each carries a `json_schema` (the field”
  • [claimed-docs] https://developers.clerky.com/getting-started/lifecycle/index.md“# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those values, and poll for state. Your product owns data collection and progress display; Clerky handles signing and formation work. ## Workflow | Step | Your product does this | API surface | | --- | --- | --- | | 1 | Create a document set from a template. | [`POST /v1/document_sets`][start-document-set] | | 2 | Render the forms that need values. | [`GET /v1/document_sets/{id}/forms`][list-document-set-forms] | | 3 | Submit JSON values to the returned action”
  • [claimed-docs] https://developers.clerky.com/getting-started/authentication/index.md“# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scopes, token lifetime, and refresh behavior will be published before partner integrations launch. ## Authorization flow The Partner API will use the authorization code flow: 1. Redirect the user to Clerky. 2. The user signs in and authorizes access. 3. Clerky redirects back with an authorization code. 4. Your server exchanges the code for an access token. 5. Your server sends the token with Partner API requests. ## Access model Each token is limited by”
  • [claimed-docs] https://www.clerky.com/startups/products“Issue safes or convertible notes. Hire employees, consultants, and advisors, and issue stock or stock options as equity compensation.”
  • [claimed-docs] https://www.clerky.com/attorneys“Attorney accounts get access to over 40 advanced products that are not publicly available.”
  • [claimed-docs] https://www.clerky.com/pricing“Apply for accounts with the most popular banks for startups. Pre-filled applications make it as easy as possible.”

Export all of my data in open formats and leaveweight 3

3 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 30 max

  • [claimed-docs] https://developers.clerky.com/getting-started/introduction/index.md“# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports Delaware C-Corporation formations. Your product creates a document set, renders the forms the API returns, submits JSON values, and polls for lifecycle state. Users enter formation information in your product and sign documents on Clerky. ## Concepts - **Document set**: the unit of work. It bundles the documents, signatures, and filings for one entity formation. - **Form**: describes a set of data to collect. Each carries a `json_schema` (the field”
  • [claimed-docs] https://developers.clerky.com/getting-started/authentication/index.md“# Authentication The Clerky Partner API will use OAuth 2.0 bearer tokens. OAuth-based access is coming soon; client registration, URLs, scopes, token lifetime, and refresh behavior will be published before partner integrations launch. ## Authorization flow The Partner API will use the authorization code flow: 1. Redirect the user to Clerky. 2. The user signs in and authorizes access. 3. Clerky redirects back with an authorization code. 4. Your server exchanges the code for an access token. 5. Your server sends the token with Partner API requests. ## Access model Each token is limited by”
  • [probe] https://handbooks.clerky.com/llms.txt“PROBE llms.txt: HTTP 404 at https://handbooks.clerky.com/llms.txt”
  • [probe] https://handbooks.clerky.com/legal-concepts.md“PROBE docs-md: HTTP 404 at https://handbooks.clerky.com/legal-concepts.md”
  • [probe] https://handbooks.clerky.com/openapi.json“PROBE openapi: all candidate paths 404 (https://handbooks.clerky.com/openapi.json, https://handbooks.clerky.com/swagger.json, https://handbooks.clerky.com/api/openapi.json, https://handbooks.clerky.com/.well-known/openapi.json)”

Read the product's source under an open licenseweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

  • [probe] https://handbooks.clerky.com/llms.txt“PROBE llms.txt: HTTP 404 at https://handbooks.clerky.com/llms.txt”
  • [probe] https://handbooks.clerky.com/legal-concepts.md“PROBE docs-md: HTTP 404 at https://handbooks.clerky.com/legal-concepts.md”
  • [probe] https://handbooks.clerky.com/openapi.json“PROBE openapi: all candidate paths 404 (https://handbooks.clerky.com/openapi.json, https://handbooks.clerky.com/swagger.json, https://handbooks.clerky.com/api/openapi.json, https://handbooks.clerky.com/.well-known/openapi.json)”

Self-host the core productweight 3

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Openness = 4.8 ÷ 70 × 100 = 6.9

Built-in AI9.3/100×0.15 of the PA blend

Inside-out: how agentic the product itself is for its users — built-in assistants, autonomous features.

Get AI-generated insights and suggestions from my data inside the productweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

  • [claimed-docs] https://developers.clerky.com/mcp-server/index.md“# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/getting-started/intro) servers, including Claude and ChatGPT. Once connected, the assistant can use available Clerky MCP tools with the team access you authorize. The MCP server URL is: ```text https://mcp.clerky.com/mcp ``` Jump to the setup instructions for your AI tool: - [Claude](#claude) - [ChatGPT](#chatgpt) - [Other AI assistants](#other-ai-assistants) ## Before You Begin Make sure you have: - A Clerky account you can sign in with. - Access to the C”
  • [probe] https://mcp.clerky.com/mcp“PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gated remote MCP server, per docs read-only tools with team-scoped access”

Set up automations that run autonomously in the backgroundweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

  • [claimed-docs] https://developers.clerky.com/mcp-server/index.md“# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/getting-started/intro) servers, including Claude and ChatGPT. Once connected, the assistant can use available Clerky MCP tools with the team access you authorize. The MCP server URL is: ```text https://mcp.clerky.com/mcp ``` Jump to the setup instructions for your AI tool: - [Claude](#claude) - [ChatGPT](#chatgpt) - [Other AI assistants](#other-ai-assistants) ## Before You Begin Make sure you have: - A Clerky account you can sign in with. - Access to the C”
  • [probe] https://mcp.clerky.com/mcp“PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gated remote MCP server, per docs read-only tools with team-scoped access”
  • [claimed-docs] https://developers.clerky.com/getting-started/introduction/index.md“# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports Delaware C-Corporation formations. Your product creates a document set, renders the forms the API returns, submits JSON values, and polls for lifecycle state. Users enter formation information in your product and sign documents on Clerky. ## Concepts - **Document set**: the unit of work. It bundles the documents, signatures, and filings for one entity formation. - **Form**: describes a set of data to collect. Each carries a `json_schema` (the field”
  • [claimed-docs] https://developers.clerky.com/getting-started/lifecycle/index.md“# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those values, and poll for state. Your product owns data collection and progress display; Clerky handles signing and formation work. ## Workflow | Step | Your product does this | API surface | | --- | --- | --- | | 1 | Create a document set from a template. | [`POST /v1/document_sets`][start-document-set] | | 2 | Render the forms that need values. | [`GET /v1/document_sets/{id}/forms`][list-document-set-forms] | | 3 | Submit JSON values to the returned action”

Delegate tasks to a built-in AI assistant inside the productweight 3

3 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 30 max

  • [claimed-docs] https://developers.clerky.com/mcp-server/index.md“# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/getting-started/intro) servers, including Claude and ChatGPT. Once connected, the assistant can use available Clerky MCP tools with the team access you authorize. The MCP server URL is: ```text https://mcp.clerky.com/mcp ``` Jump to the setup instructions for your AI tool: - [Claude](#claude) - [ChatGPT](#chatgpt) - [Other AI assistants](#other-ai-assistants) ## Before You Begin Make sure you have: - A Clerky account you can sign in with. - Access to the C”
  • [probe] https://mcp.clerky.com/mcp“PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gated remote MCP server, per docs read-only tools with team-scoped access”

Operate the product with natural-language commandsweight 2

2 (weight) × 7 (quality) × 0.6 (partial) = 8.4 of 20 max

  • [claimed-docs] https://developers.clerky.com/mcp-server/index.md“# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/getting-started/intro) servers, including Claude and ChatGPT. Once connected, the assistant can use available Clerky MCP tools with the team access you authorize. The MCP server URL is: ```text https://mcp.clerky.com/mcp ``` Jump to the setup instructions for your AI tool: - [Claude](#claude) - [ChatGPT](#chatgpt) - [Other AI assistants](#other-ai-assistants) ## Before You Begin Make sure you have: - A Clerky account you can sign in with. - Access to the C”
  • [probe] https://mcp.clerky.com/mcp“PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gated remote MCP server, per docs read-only tools with team-scoped access”
  • [probe] https://developers.clerky.com/llms.txt“PROBE llms.txt: HTTP 200 at https://developers.clerky.com/llms.txt - [Lifecycle](https://developers.clerky.com/getting-started/lifecycle/index.md): How a partner creates, fills, and tracks a document set. - [Introduction](https://developers.clerky.com/getting-started/introduction/index.md): Overview of the Clerky Partner API. - [Authentication](https://developers.clerky.com/getting-started/authentication/index.md): How partner applications authenticate to the Cle”

Built-in AI = 8.4 ÷ 90 × 100 = 9.3

Automation0.0/100×0.15 of the PA blend

Depth of automation primitives — rules, scheduling, bulk operations, webhooks.

Perform bulk operations across many items at onceweight 2

2 (weight) × 0 (quality) × 0.0 (none) = 0.0 of 20 max

  • [claimed-docs] https://developers.clerky.com/getting-started/introduction/index.md“# Introduction The Clerky Partner API lets partners bring a Clerky-powered formation workflow into their own product. It currently supports Delaware C-Corporation formations. Your product creates a document set, renders the forms the API returns, submits JSON values, and polls for lifecycle state. Users enter formation information in your product and sign documents on Clerky. ## Concepts - **Document set**: the unit of work. It bundles the documents, signatures, and filings for one entity formation. - **Form**: describes a set of data to collect. Each carries a `json_schema` (the field”
  • [claimed-docs] https://developers.clerky.com/getting-started/lifecycle/index.md“# Lifecycle A [document set][document-sets] moves through four partner-facing steps: create it, collect [form][forms] values, submit those values, and poll for state. Your product owns data collection and progress display; Clerky handles signing and formation work. ## Workflow | Step | Your product does this | API surface | | --- | --- | --- | | 1 | Create a document set from a template. | [`POST /v1/document_sets`][start-document-set] | | 2 | Render the forms that need values. | [`GET /v1/document_sets/{id}/forms`][list-document-set-forms] | | 3 | Submit JSON values to the returned action”
  • [claimed-docs] https://developers.clerky.com/mcp-server/index.md“# Clerky MCP Server Clerky works with AI assistants that support remote [Model Context Protocol (MCP)](https://modelcontextprotocol.io/docs/getting-started/intro) servers, including Claude and ChatGPT. Once connected, the assistant can use available Clerky MCP tools with the team access you authorize. The MCP server URL is: ```text https://mcp.clerky.com/mcp ``` Jump to the setup instructions for your AI tool: - [Claude](#claude) - [ChatGPT](#chatgpt) - [Other AI assistants](#other-ai-assistants) ## Before You Begin Make sure you have: - A Clerky account you can sign in with. - Access to the C”
  • [probe] https://mcp.clerky.com/mcp“PROBE remote MCP initialize (no token): {"error": "invalid_token", "error_description": "Authentication required"} HTTP 401 — live OAuth-gated remote MCP server, per docs read-only tools with team-scoped access”

Define rules that trigger actions automatically on eventsweight 3

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Schedule recurring jobs or workflowsweight 2

n/a — not applicable to this product: excluded from numerator and denominator

no evidence cited — the verdict rests on absence of evidence, re-checked on refresh

Version, review, and roll back my automationsweight 1

n/a — not applicable to this product: excluded from numerator and denominator

  • [claimed-docs] https://www.clerky.com/attorneys“We log every change anyone makes to a document set or workspace, so you can always see who was responsible for what.”

Automation = 0.0 ÷ 20 × 100 = 0.0