Agentic Readiness · evidence
Companies with a documented agent or API path
Criterion-by-criterion evidence for every profile reviewed in November whose interface reaches some part of formation: a draft, handoff, order, application or submission. The rubric, the scoring rules and the full score matrix are on the Agentic Readiness methodology page; the remaining profiles are under companies without an agent formation path, and earlier assessments.
Scope, evidence and gaps
Open a profile to see what was reviewed, where the agent stops and why each score earns its points.
Corpus · 89 · 2026-11-14
Scope: US LLC and nonprofit; public MCP checkout is USDC on Solana only
Live discovery lists formation.checkout and formation.payment_status alongside formation.handoff. Checkout documents an order and USDC payment request; the founder pays and confirms email within 48 hours, then review follows unless expedited skip-review is elected. The tax-ID add-on is not sold on this agent path. The write path was not exercised; no resulting government filing was observed. On 2026-11-14 criterion C was rechecked after the public REST order endpoint went live, and criteria E and I after signed order-status webhooks and a dated order timeline went live; the other six criteria keep their 2026-11-13 evidence.
Capability assessment 2026-11-14; sources checked 2026-11-14. Evidence: live discovery and code. Price verification dates are separate.
- A · 14/15Native conversational intake and external-agent requirements, handoff and order tools; final legal decisions remain with the founder. source 1
- B · 20/20Anonymous live discovery returned eleven public tools with schemas, including checkout, payment status and formation status. source 1
- C · 14/15Public OpenAPI documents formation-order creation (POST /api/v1/formation/orders), order checkout and order status, plus requirements, NAICS and prices, open without an account or partner agreement. Its non-stored test mode was exercised anonymously on 2026-11-14 (create and status poll, HTTP 200). No live order was placed through REST, so one point is withheld. source 1 · source 2
- D · 6/15An order/payment-request tool is documented. Founder confirmation and subsequent filing execution were not exercised, so this is order-level credit. source 1
- E · 10/10Tracking-token status includes phases and dated milestones; filingSubmitted explicitly distinguishes state submission from payment or review. Order-state changes are pushed as signed webhooks (Standard Webhooks HMAC, retried about 45 hours): an optional callbackUrl on POST /api/v1/formation/orders, a per-order webhooks route, and the formation.webhook MCP tool. On 2026-11-14 a test-mode order with a callbackUrl delivered one signed formation.webhook.test to a receiver Corpus controls (HTTP 204) and its signature verified with the returned secret; no live order's state-change delivery was observed. source 1 · source 2
- F · 10/10Requirements expose structured state-specific fields, quotes and registered-agent acknowledgements; the public price grid is machine-readable. source 1
- G · 5/5The exposed order path needs no API key or Corpus account; USDC payment and email confirmation are deliberate owner gates. source 1
- H · 5/5Explicit founder consent and email confirmation precede filing; staff review follows with a clearly disclosed expedited skip-review option. source 1
- I · 5/5GET /api/v1/formation/orders/{orderId} returns a dated timeline of the order's public state changes (created, paid, founder confirmed, review approved, submitted, state confirmed, certificate available), with the state confirmation number on the submitted entry and the certificate URL on the certificate entry. The test-mode timeline was read anonymously on 2026-11-14; no live completed filing was retrieved. source 1 · source 2
Doola · 84 · 2026-11-13
Scope: US LLC/C-corp; Starter MCP flow; authenticated execution untested
Official docs describe start_formation, checkout, structured intake and submit_formation. The endpoint requires OAuth; authenticated tools and filing execution were not exercised. Full execution points from the older assessment are unsupported by this review. Current main docs/manifest and older compact scope descriptions disagree; the wider MCP scope was not exercised.
Capability assessment 2026-11-13; sources checked 2026-11-12. Evidence: documented auth untested. Price verification dates are separate.
- A · 14/15A formation-specific conversational tool flow covers intake and a documented submit step. source 1
- B · 17/20Official hosted MCP, OAuth metadata and a server-generated public contract; the authenticated tool list was not retrieved. source 1
- C · 13/15Public Partner API specification documents company creation, sandbox and status; partner execution remains untested. source 1
- D · 9/15submit_formation is documented to advance submission after user confirmation, but no submission or filing was observed. source 1
- E · 9/10Documented per-company status and nextAction state support resumable multi-step formation. source 1
- F · 9/10Typed intake, state/entity choices and a structured charge summary are documented; callers must use returned live values. source 1
- G · 5/5OAuth and secure owner payment/SSN links are documented; deliberate owner approval is not a deduction. source 1
- H · 4/5Owner decisions and sensitive-data steps are explicit; specialist involvement is documented without proving review of every transaction. source 1
- I · 4/5Documented company status, stored formation records and returned documents; no completed filing evidence was independently retrieved. source 1
OpenFile · 80 · 2026-11-13
Scope: US draft formations with owner review/signature/payment
create_formation saves a draft and owner review link. The owner signs and pays before the provider files. Public MCP/REST requirements and quotes were checked; no draft creation, payment or filing was executed.
Capability assessment 2026-11-13; sources checked 2026-11-13. Evidence: catalog and documents. Price verification dates are separate.
- A · 14/15Agent prompts, task planning and structured formation intake meaningfully advance an owner-review draft. source 1
- B · 20/20Live anonymous MCP discovery lists 27 schemas and published agent setup; full catalog access is observed, not paid execution. source 1
- C · 12/15Public OpenAPI covers draft creation, quotes, edits and status; the API explicitly stops at owner sign/pay. source 1
- D · 3/15Creation yields a draft/review URL, and the company states the API does not file or charge before the owner acts. source 1
- E · 8/10Formation/order status, owner steps and persistent tokens support resumption; unsigned drafts have a documented expiry. source 1
- F · 9/10Structured state fees, official-source URLs, name designators, publication rules and quotes are available with verification flags. source 1
- G · 5/5Anonymous discovery/drafts use resource tokens; owner signing/payment is an intentional safety gate, not an auth penalty. source 1
- H · 5/5Owner authorization and staff review of filings are explicitly documented. source 1
- I · 4/5Order/file numbers, signed authorization records and delivered state documents support traceability; no full audit stream was exercised. source 1
Foundingbird · 78 · 2026-11-13
Scope: Malaysia Sdn Bhd only; secretary-reviewed application
The live catalog describes application creation/submission and package selection. Owners pay, complete eKYC and sign; qualified company secretaries review and file with SSM. No write path or SSM filing was exercised.
Capability assessment 2026-11-13; sources checked 2026-11-13. Evidence: catalog and documents. Price verification dates are separate.
- A · 14/15A formation-specific agent workflow covers Malaysian application intake and package choice. source 1
- B · 19/20Thirty tool schemas and public lookups were checked; authenticated write operations were not exercised. source 1
- C · 8/15Structured application/quote/status tools provide an MCP interface; no separately verified live formation REST API is credited. source 1
- D · 6/15Submitting an application to the firm is documented, followed by owner gates and secretary filing; no government submission was observed. source 1
- E · 8/10Persistent application, task, order and company state is documented for resumption. source 1
- F · 9/10Typed flow descriptions, package quotes and structured business-classification requirements are available for the Malaysian scope. source 1
- G · 5/5OAuth and owner checkout/eKYC/signature handoffs are designed access/approval steps, not penalties. source 1
- H · 5/5Qualified company secretaries explicitly review and submit filings, with owner approval gates. source 1
- I · 4/5Company/SSM document and order access are documented; no completed filing or audit export was independently retrieved. source 1
Lovie · 76 · 2026-11-13
Scope: US formation; anonymous drafts, authenticated formation/payment links
Discovery lists 520 tools but only 38 declare anonymous access. Intake/certificate tools work on drafts; payment-link/order tools need sign-in. Founder payment is on Stripe. Operator review of every order and actual state filing were not established.
Capability assessment 2026-11-13; sources checked 2026-11-13. Evidence: catalog and documents. Price verification dates are separate.
- A · 14/15A formation chat plus agent-directed intake tools/prompts advance a structured draft. source 1
- B · 19/20Live discovery exposes schemas; anonymous tool listing must not be confused with permission to call the 482 OAuth tools. source 1
- C · 10/15Public gRPC-Web/API client documentation exists in addition to MCP; authenticated API execution was not tested. source 1
- D · 6/15Authenticated tools describe formation/order and checkout creation; anonymous certificate approval itself files nothing. source 1
- E · 8/10Persistent formation IDs, status and editable draft checkpoints support resumed work. source 1
- F · 9/10Typed intake, quotes and filing-fee tools are structured; a flat quote alone does not establish every state-specific outcome. source 1
- G · 4/5OAuth gates payment links; inconsistent discovery/endpoint guidance needs care. Deliberate owner payment is not a deduction. source 1
- H · 3/5Founder payment and contractual approval are established; a reviewer-only tool does not prove universal staff review. source 1
- I · 3/5Document and status tools are documented; government-filing evidence and a public audit stream were not retrieved. source 1
General Legal · 74 · 2026-11-13
Scope: Delaware new LLC/C-corp; shelf-company purchase is a separate path
Two start tools document a formation record and Stripe checkout link. Founder payment and natural-person signatures follow; no write tool or filing was exercised. The automated Inc. product is distinct from the law-firm engagement, and does not provide EIN application service.
Capability assessment 2026-11-13; sources checked 2026-11-13. Evidence: catalog and documents. Price verification dates are separate.
- A · 14/15Agent-first formation skills and typed start tools support a complete structured intake. source 1
- B · 19/20The verified formation server lists six schemas; it needs a stateful handshake and lacks tool-side read/write annotations. source 1
- C · 8/15A structured formation interface exists over MCP; the separate published REST API covers matters, not formation. source 1
- D · 6/15Start tools are described as creating an order/checkout, not as an observed government submission. source 1
- E · 8/10A formation capability ID, status polling and renewable short-lived document links support resumed work. source 1
- F · 8/10Filing options and typed intake fields are structured; requirements are scoped to the Delaware product. source 1
- G · 5/5No account is needed to start; capability tokens protect records and a person pays on Stripe by design. source 1
- H · 3/5Natural-person signatures and order-refusal rights are documented; staff review of every automated order is not established. source 1
- I · 3/5Status and document retrieval are documented; no public action log or completed paid flow was inspected. No signing vendor is inferred. source 1 · source 2
Northwest Registered Agent · 74 · 2026-11-13
Scope: US formation via account MCP; final filing forms completed in portal
The official catalog documents create_company, formation cart and saved-payment checkout tools. The person supplies sensitive fields and reviews/submits the filing form in the portal. Authenticated actions were not exercised.
Capability assessment 2026-11-13; sources checked 2026-11-12. Evidence: documented auth untested. Price verification dates are separate.
- A · 13/15The account assistant and external connector support formation-cart workflows; final form submission remains in the portal. source 1
- B · 17/20An official hosted MCP and detailed tool catalog are documented; signed-in discovery/execution was not performed. source 1
- C · 8/15Structured formation/cart/form tools provide a documented machine interface; no separately verified production formation REST contract is credited. source 1
- D · 6/15Company/cart/order checkout is documented, followed by owner portal form submission; no agent-caused filing was observed. source 1
- E · 8/10Account action items, order/filing state and persistent company records support resumed work. source 1
- F · 8/10Entity catalogs, filing options, prices and required form fields are structured in the official tool catalog. source 1
- G · 5/5OAuth/account connection and saved payment methods support agents; owner approval and portal signature steps are intentional. source 1
- H · 5/5Owner confirmation and specialist support/review are explicit in the documented formation workflow. source 1
- I · 4/5Order, invoice, document and filing-status tools provide retrievable records; a completed filing was not retrieved in this review. source 1
PaperOS / Savvi Legal · 74 · 2026-11-13
Scope: US entity-setup assessment/workflow; authenticated execution untested
Published plugins document entity-setup assessments and workflow initiation. submit_formation finalizes an assessment, not a government filing. The owner reviews decisions and pays in-app; the filing/support team handles filing.
Capability assessment 2026-11-13; sources checked 2026-11-12. Evidence: documented auth untested. Price verification dates are separate.
- A · 14/15Entity-setup skills guide a conversational assessment, steering questions and reviewed predictions. source 1
- B · 16/20Official plugin repositories document multiple OAuth MCP servers; live authenticated tools were not listed or executed. source 1
- C · 11/15Public partner developer docs describe workflow-template and workflow-creation endpoints, with partner access limits. source 1
- D · 3/15The submit tool finalizes an Entity Assessment; it is not documented as the agent submitting a government filing. source 1
- E · 8/10Documented run IDs, workflows, tasks and process/payment state support resumed work. source 1
- F · 8/10Structured assessments, template catalogs, records and citable knowledge-base results are documented. source 1
- G · 5/5OAuth SSO and owner Stripe payment are intentional gates in the documented user workflow. source 1
- H · 5/5The owner reviews important decisions and assistance charges; filing/support and counsel escalation are documented. source 1
- I · 4/5Document/signature/task records and delivered artifacts are documented; no full agent audit ledger or live filing was inspected. source 1
OtoCo · 73 · 2026-11-13
Scope: Delaware/Wyoming standalone LLC checkout; instant series is not a new state filing
Production discovery/read tools were checked; keyed checkout is documented but untested. Standalone LLCs are distinguished from series under OtoCo master LLCs. Some client docs target staging and do not prove a live filing.
Capability assessment 2026-11-13; sources checked 2026-11-13. Evidence: catalog and documents. Price verification dates are separate.
- A · 13/15AI/Genco and agent tools support entity discovery and documented checkout workflows. source 1
- B · 18/20Production public tools and typed catalogs are observed; broader keyed tool access remains documentation-only. source 1
- C · 10/15Versioned REST routes and capability documentation exist; keyed execution is untested and some examples target staging. source 1
- D · 6/15Standalone checkout/order creation is documented; series minting is not credited as a new government filing. source 1
- E · 8/10Entity/payment records and keyed status operations are documented for resumed workflows. source 1
- F · 8/10Structured jurisdiction, product and checkout-option data are available; registry name checks are not state clearance. source 1
- G · 4/5Key/wallet and owner-payment paths are documented, but production versus staging guidance is inconsistent. source 1
- H · 3/5Explicit confirmation and owner payment are described; universal pre-state staff review of standalone filings is not established. source 1
- I · 3/5Entity IDs and document/compliance access are documented; public entity counts do not prove standalone filing volume. source 1
StartGlobal · 73 · 2026-11-13
Scope: US signup draft; authenticated onboarding only after owner payment
The public start_signup tool creates a signup draft/link, not an account, order or payment. Fourteen account tools are documented and untested; writes require the human to have paid. The person checks, signs and confirms submission.
Capability assessment 2026-11-13; sources checked 2026-11-13. Evidence: catalog and documents. Price verification dates are separate.
- A · 13/15An assistant can prepare signup and, after payment/authorization, documented onboarding fields. source 1
- B · 19/20Six public schemas were checked; the fourteen authenticated tools come from the company catalog, not signed-in discovery. source 1
- C · 10/15A documented onboarding API supplies typed step schemas and updates; it does not create or pay for formation orders. source 1
- D · 3/15Only a signup draft is created on the public path; human payment/signature/submission remain outside agent authority. source 1 · source 2
- E · 8/10Documented company/filing/document/deadline tools support persistent account state; none was authenticated in this review. source 1
- F · 9/10Typed signup/onboarding schemas, prices and requirements are published; public versus account scopes are separated. source 1
- G · 4/5OAuth and owner payment are designed gates; documented client/write and file-upload limits constrain usable connectors. source 1
- H · 4/5Owner detail checks, identity documents and signatures are explicit before the company files. source 1
- I · 3/5Status and document links are documented; no paid order, filing receipt or complete action trail was retrieved. source 1
Naïve · 71 · 2026-11-15
Scope: US LLC via its formation provider (doola); API-key MCP and REST; execution untested
Public OpenAPI documents verification, company creation and a submit route for LLCs; doola, per its announcement, files. Members pass hosted identity checks and formation calls default to asking for approval. The MCP server returned 401 without a key, so its tools were not listed; nothing was executed.
Capability assessment 2026-11-15; sources checked 2026-11-15. Evidence: documented auth untested. Price verification dates are separate.
- A · 12/15An agent platform: formation is a primitive driven by a coding agent or Naïve's own agent session through documented legal tools; no end-customer conversational intake. source 1
- B · 13/20An MCP server generated from the API route table, authenticated by API key or session token; it returned 401 to unauthenticated tools/list on November 15 and is not in the official registry. source 1 · source 2
- C · 12/15Self-serve REST API with a public OpenAPI 3.1 spec: legal verifications, companies, submit, documents, NAICS codes and states. LLC only; nothing executed. source 1 · source 2
- D · 9/15A documented submit route files through the formation provider after identity verification and payment from prepaid credits; not executed and no public count of formed companies. source 1 · source 2
- E · 8/10Company status machine (awaiting payment, paid, submitted, formed or failed) with required actions and retry; no formation-specific outbound webhook is documented. source 1
- F · 7/10Typed schemas plus NAICS and state reference routes; the live per-state price list needs a key. source 1
- G · 4/5Self-serve API keys and prepaid credits let an agent pay without a checkout page once approved; hosted identity checks are a designed human step. source 1 · source 2
- H · 3/5Hosted identity verification for every member and approval-by-default on formation calls; operator review of filings is not described. source 1
- I · 3/5Formation documents (articles, operating agreement, EIN letter) are retrievable by route; no filing evidence was observed. source 1
OffshoreProz · 71 · 2026-11-13
Scope: Live Agent Company Wyoming/Nevis requests; separate Agent API sandbox
Live MCP descriptions create requests and payment instructions; the team files. A self-published case study and counter are company claims. The separate REST Agent API is sandbox-only and is not credited as live formation execution.
Capability assessment 2026-11-13; sources checked 2026-11-13. Evidence: catalog and documents. Price verification dates are separate.
- A · 14/15An agent-specific company product and guided request tools advance formation intake. source 1
- B · 19/20The live Agent Company catalog has eleven typed tools; the separate sandbox API is distinguished. source 1
- C · 6/15Structured live MCP requests are documented; the separately specified formation REST API is sandbox-only with simulated providers. source 1
- D · 6/15Request/checkout creation is documented. Neither the company counter nor its case study establishes tested government submission. source 1 · source 2
- E · 8/10Request IDs and formation/payment/KYC status polling support resumed work; sandbox-only event features receive no live credit. source 1
- F · 9/10Requirements and structured quotes are available for the supported live product; conflicting product documentation is disclosed. source 1
- G · 4/5Key issuance and card/USDC paths are documented, but registration-host and product/auth guidance were not fully verified. source 1
- H · 3/5Team filing review is described; live product KYC statements conflict and sandbox consent gates are not imported into the live offer. source 1
- I · 2/5Request/document retrieval exists; case-study identities and filing numbers are withheld, and the detailed audit ledger belongs to the sandbox API. source 1 · source 2
Stripe Atlas · 70 · 2026-11-13
Scope: Delaware LLC/C-corp draft applications; human Dashboard submission
The documented atlas_company_formation tool and CLI prepare, validate and resume an Atlas draft. The person pays, signs and submits in the Dashboard. Authenticated execution was not performed.
Capability assessment 2026-11-13; sources checked 2026-11-12. Evidence: documented auth untested. Price verification dates are separate.
- A · 13/15A dedicated agent formation guide and draft-application workflow meaningfully advance intake. source 1
- B · 16/20Official OAuth-gated MCP and a documented Atlas tool; tool listing and execution require an account and were not exercised. source 1
- C · 8/15Structured MCP/CLI draft operations are documented; no public formation REST API is credited. source 1 · source 2
- D · 3/15The company expressly states agent/CLI draft preparation does not submit or form the company; credit is limited to draft handoff. source 1
- E · 8/10Drafts are saved, retrieved and advanced across sessions; post-submission agent visibility is more limited. source 1
- F · 8/10Typed application fields and validation/next-action responses are documented; no broad public requirements/fee schema endpoint is credited. source 1
- G · 5/5OAuth or scoped agent keys support the workflow; founder payment/signature gates are intentional and not penalised. source 1
- H · 5/5The founder reviews, pays, signs and submits; application/identity checks and support escalation are documented. source 1
- I · 4/5Dashboard documents and MCP call logs support provenance; no formation audit-log API or live filing was inspected. source 1
Corply · 68 · 2026-11-15
Scope: Delaware C-corp only; OAuth-gated MCP; authenticated execution untested
The anonymous MCP catalog lists 264 tools (November 15), all OAuth-gated. Tool descriptions cover application, documents, founder e-signatures and a checkout link; after payment an operator reviews the packet and files with Delaware. No tool was called and no filing was observed.
Capability assessment 2026-11-15; sources checked 2026-11-15. Evidence: documented auth untested. Price verification dates are separate.
- A · 13/15The product is built to be driven from the founder's own agent (Claude, Claude Code, Codex, Cursor, OpenCode), with a separate chat intake; the formation flow is described end to end in tool descriptions. source 1
- B · 17/20Hosted MCP server in the official registry; tools/list works without sign-in (264 tools with annotations on November 15) and OAuth uses dynamic client registration. No tool is callable without an account. source 1
- C · 6/15No REST or OpenAPI formation API was found; typed MCP tool schemas are the only structured formation interface. source 1 · source 2
- D · 6/15request_payment returns a checkout link and, per the descriptions, payment queues the signed packet for operator review and filing. Documented only; not executed. source 1
- E · 8/10get_status, await_payment polling, revision and history tools, and saved company state that a new conversation resumes. No webhooks found. source 1 · source 2
- F · 6/10JSON Schemas with enums on every tool; the pricing catalog tool is sign-in only and there is no public requirements dataset beyond Delaware. source 1 · source 2
- G · 4/5Standard MCP OAuth with PKCE and dynamic registration works with stock clients; payment is a deliberate founder step on Corply's checkout page. source 1
- H · 5/5Founder signature consent, founder payment and operator review before the Delaware filing are all documented. source 1 · source 2
- I · 3/5Revision and history tools and generated documents are described; no filing receipt or audit stream was retrieved. source 1
GatewayBase · 67 · 2026-11-13
Scope: Wyoming LLC MCP; authenticated catalog/write path untested
Official docs describe saving a formation draft, email verification and creating a Stripe payment link. The owner pays in the browser and GatewayBase handles filing. The authenticated tool list and write path were not exercised.
Capability assessment 2026-11-13; sources checked 2026-11-12. Evidence: documented auth untested. Price verification dates are separate.
- A · 13/15A documented formation-specific conversational MCP flow advances a Wyoming LLC draft. source 1
- B · 16/20The endpoint responds with OAuth metadata; thirteen tool names are company-documented, not live authenticated discovery. source 1
- C · 8/15Typed formation/order/payment-link operations are documented through MCP; no independent public REST formation spec is credited. source 1
- D · 6/15Payment-link/order creation is documented; no order, charge or state filing was executed. source 1
- E · 7/10Documented draft/order/status/document IDs support account-based continuation. source 1
- F · 6/10Offer tools describe required fields and prices for the narrow product; no broader structured state-rule/fee dataset is credited. source 1
- G · 5/5Self-serve OAuth/email verification and safe Stripe owner checkout are documented and intentional. source 1
- H · 3/5Owner email/payment and EIN signature links are explicit; staff review of every formation filing is not established. source 1
- I · 3/5Document/download links and file-vault receipts are described; no public action ledger or completed formation evidence was retrieved. source 1
GVRN · 66 · 2026-11-13
Scope: Non-US incorporation review requests; Delaware MCP coverage unestablished
submit_incorporation sends intake to staff review, not a paid order or legal incorporation. The checked MCP does not establish Delaware formation despite site-wide marketing. Email/owner verification and staff follow-up remain.
Capability assessment 2026-11-13; sources checked 2026-11-13. Evidence: catalog and documents. Price verification dates are separate.
- A · 12/15An agent can collect incorporation intake and request staff review. source 1
- B · 18/20Seven public schemas and transport discovery were checked; OAuth and email verification variants have different access behavior. source 1
- C · 6/15Typed draft/review-request tools provide an intake interface, without a checkout or filing-order API. source 1
- D · 3/15Submission is explicitly a request for staff review; the server says it does not legally incorporate the company. source 1
- E · 7/10Draft and review-request status support continuation, with limited documented end-state/cancellation semantics. source 1
- F · 7/10Draft fields are structured, but jurisdiction/entity values are free text and no machine-priced package flow establishes US coverage. source 1
- G · 5/5Documented OTP/OAuth authorization and owner interaction support the review-request path. source 1
- H · 5/5A corporate-secretary specialist reviews intake and contacts the verified owner with next steps and document requests. source 1
- I · 3/5Draft/request IDs and review status provide a limited trace; no payment receipt or government-filing evidence API was established. source 1
Start Companies · 66 · 2026-11-13
Scope: US LLC lead intake and payment/signup handoff
create_llc_lead registers a lead/reference and returns links. The human pays and uploads documents before an order proceeds. A website/MCP platform-fee conflict is disclosed; lead creation is not scored as an order.
Capability assessment 2026-11-13; sources checked 2026-11-13. Evidence: catalog and documents. Price verification dates are separate.
- A · 13/15Package/requirements tools and typed lead intake support a conversational formation handoff. source 1
- B · 19/20A live public MCP catalog and schemas are checked; state-changing lead tools were not invoked. source 1
- C · 6/15A structured MCP lead/payment-link interface is documented; no independent formation-order REST contract is credited. source 1
- D · 3/15The documented effect is a lead and links; the terms say the request does not form a company or oblige purchase. source 1
- E · 6/10Lead references and order-status descriptions support limited continuation; authenticated post-payment depth is unverified. source 1
- F · 7/10Packages and renewal data are structured, but official fee and package descriptions conflict. source 1
- G · 5/5Public lookups/lead flow and owner browser payment are documented; the owner gate is intentional. source 1
- H · 4/5Owner documents and pre-filing documentation review are described in the legal terms. source 1
- I · 3/5Reference numbers, confirmations and panel documents provide a partial trail; a filing-evidence API was not verified. source 1
Clemta · 63 · 2026-11-15
Scope: US LLC/C-corp; partner API orders; customer MCP covers accounting, not formation; execution untested
A public OpenAPI spec documents company creation with service orders for approved partners, a sandbox, events and webhooks; Clemta Operations performs the filing. Its customer MCP servers are OAuth-gated and cover accounting and invoicing rather than formation. Nothing was executed.
Capability assessment 2026-11-15; sources checked 2026-11-12. Evidence: documented partner untested. Price verification dates are separate.
- A · 8/15The in-app assistant Clem handles bookkeeping, tax and documents; a formation-performing agent interface was not established. source 1
- B · 8/20OAuth MCP servers with published metadata, whose documented scopes cover company, sales, banking and accounting data rather than formation orders; scored like other non-formation MCP servers. source 1 · source 2
- C · 13/15Public OpenAPI 3.1 partner spec (45 paths, re-read November 15) with POST /companies, service orders, price previews, a test mode and versioning. source 1 · source 2
- D · 6/15With an approved partner's live key, creating a company bills service orders and Clemta Operations files. Documented only; not executed. source 1 · source 2
- E · 9/10Company status and stage, service-order state machine, open-requirements list, an events endpoint and signed webhooks. source 1
- F · 8/10Requirement forms return typed field schemas and the product catalog exposes availability rules and price previews. source 1
- G · 3/5Test keys are self-serve but live keys need an approved partner application; MCP uses standard OAuth. source 1
- H · 4/5Clemta Operations performs formation work; identity documents gate formation; tax filings are reviewed before filing. source 1
- I · 4/5Immutable event objects, request and webhook logs, and retrievable deliverable files are documented; no filing evidence was retrieved. source 1
Corpo · 62 · 2026-11-15
Scope: Wyoming LLC and DAO LLC; agent-first API and stdio MCP; filing currently unavailable
Corpo documents a full agent path (create, crypto payment, submit, status) through a public REST API, CLI and open-source stdio MCP server. On November 15 its quote endpoint still returned 503 filing_unavailable (the filing provider is not yet connected), and the MCP server is labelled sandbox. No filing can be caused today.
Capability assessment 2026-11-15; sources checked 2026-11-12. Evidence: catalog and documents. Price verification dates are separate.
- A · 13/15Agent-first CLI, API and MCP cover formation, governance and documents. source 1 · source 2
- B · 10/20An open-source MCP server with 16 tools, stdio only and labelled sandbox; no hosted endpoint or registry entry. source 1
- C · 9/15A public REST API documents the formation lifecycle; formation calls return filing_unavailable. source 1 · source 2
- D · 3/15Submission is documented, but the filing provider is not connected (503 on November 15), so only validated drafts can be prepared. source 1
- E · 8/10Formation status and list routes, idempotency keys and resume guidance. source 1
- F · 8/10A published formation JSON Schema and live option catalogs. source 1 · source 2
- G · 5/5Name-only agent registration returns an API key; payment is programmatic in SOL or USDC. source 1
- H · 3/5Approval gates and a vetted professional marketplace; staff review of filings is not described. source 1
- I · 3/5Evidence-pack commands and pinned templates; no filed record exists yet. source 1
Clerky · 61 · 2026-11-13
Scope: Delaware C-corp Partner API; current MCP is read-only cap-table/team access
The Partner API documents formation document sets, forms and lifecycle state; people sign and pay on Clerky. Current MCP tools are read-only and do not start formation. Partner onboarding is described as coming soon; availability/execution remains unverified.
Capability assessment 2026-11-13; sources checked 2026-11-12. Evidence: documented partner untested. Price verification dates are separate.
- A · 8/15External software can prepare a documented partner formation workflow; the current assistant tools themselves are read-only account tools. source 1
- B · 12/20An official OAuth MCP is documented, but its current tools read teams/cap tables rather than create formations. source 1
- C · 12/15A public structured Partner API specification documents document-set creation and form actions for Delaware incorporation. source 1
- D · 3/15Document-set/form preparation is documented; owner payment/signature and unverified partner availability prevent submission/execution credit. source 1
- E · 8/10Persistent document sets expose lifecycle states and saved form values for polling/resume. source 1
- F · 8/10Form responses carry JSON Schema and UI schema with required fields, constraints and action payloads. source 1
- G · 2/5Standards-based OAuth is documented, but formation partner onboarding is not self-serve and is announced as coming soon. source 1 · source 2
- H · 4/5Reviewers/collaborators and owner signature/payment checkpoints are documented; no universal Clerky-side attorney review is claimed. source 1
- I · 4/5Document-set IDs, stored executed documents and logged workspace changes are documented; no public audit export was exercised. source 1
LegalZoom · 51 · 2026-11-13
Scope: US formation checklists/package handoff; public formation tools are read-only
The six formation tools collect checklist state and return packages/checkout links. They create no formation order or cart. Write tools for other products do not establish formation submission.
Capability assessment 2026-11-13; sources checked 2026-11-13. Evidence: catalog and documents. Price verification dates are separate.
- A · 10/15The assistant can conduct structured formation intake and package discovery, then hand the user to checkout. source 1
- B · 19/20Live versioned MCP catalog and formation tool schemas are published across multiple integrations. source 1
- C · 3/15Formation-specific structured collectors exist, but the checked catalog has no formation order-creating API/tool. source 1
- D · 0/15All checked formation tools are read-only collectors; no formation order/submission tool exists in this catalog. source 1
- E · 2/10Checklist collectedData is client-held; the catalog does not establish a persistent formation-status workflow. source 1
- F · 8/10Structured checklist fields, package/state fees and published filing-requirement data are available. source 1
- G · 5/5The checked anonymous formation variant works without credentials; owner checkout is a designed handoff, not an auth defect. source 1
- H · 3/5A founder completes checkout; staffed services exist, but the checked tools do not establish universal pre-filing staff review. source 1
- I · 1/5The formation catalog exposes no filing receipt/document-retrieval workflow; client-held checklist data supplies only a limited trace. source 1
FileForms · 48 · 2026-11-15
Scope: US formation in all states through a business REST API; MCP none; execution untested
FileForms sells formation as a REST API: a published OpenAPI spec (17 paths, re-read November 15) documents POST /orders, and its docs say live orders are really submitted to states while test orders never reach one. Keys need a human-onboarded organisation with a prepaid balance. No consumer chat or MCP; nothing executed.
Capability assessment 2026-11-15; sources checked 2026-11-12. Evidence: documented auth untested. Price verification dates are separate.
- A · 0/15No conversational or agent intake; the product is an API for businesses. source 1
- B · 0/20No MCP server; llms.txt and the OpenAPI spec are documentation, not an agent-tool protocol. source 1
- C · 13/15A public OpenAPI 3.1 spec with test and live environments and formation orders. source 1 · source 2
- D · 9/15POST /orders with a formation object is documented to submit live orders to the state; not exercised. source 1 · source 2
- E · 8/10Order status plus signed webhooks for filing status changes and documents. source 1
- F · 8/10Typed schemas with enums for states, entity types and exception codes. source 1
- G · 3/5A single API key and prepaid balance once a person onboards the organisation; not self-provisioned by an agent. source 1
- H · 3/5A filing team resolves exceptions; no per-order human approval in the API path. source 1
- I · 4/5Order, company and document IDs with retrievable documents and webhook logs. source 1
Agentico · 45 · 2026-11-15
Scope: Wyoming series under an Agentico master LLC; customer files with the state; API-key MCP untested
A documented MCP server and SDK let an agent adopt a master LLC, create series records and receive formation document packages, with a named human approval on each formation verb. Agentico states it does not file with the Wyoming Secretary of State in v0.1; the customer files after counsel review. Nothing was executed.
Capability assessment 2026-11-15; sources checked 2026-11-12. Evidence: documented auth untested. Price verification dates are separate.
- A · 9/15The product is agent-facing: ten documented MCP/SDK tools carry the formation workflow up to the document package. source 1
- B · 10/20A documented MCP server package with ten tools and approval schemas; access needs a paid account key, so tools were not listed. source 1 · source 2
- C · 3/15The SDK is the only documented programmatic surface; no public REST formation API. source 1
- D · 3/15Tools return illustrative formation documents; the developer page says the customer completes the Wyoming filing. Draft-level credit only. source 1
- E · 6/10Account summary, series list and guided-setup state tools support resuming work. source 1
- F · 4/10llms.txt and structured encyclopedia content; no requirements or fee endpoints. source 1
- G · 3/5Bearer key once issued, but signup, a web checkout and MFA come first. The homepage labels its prices illustrative, not a binding offer. source 1 · source 2
- H · 4/5A named human approval is required on every formation verb. source 1
- I · 3/5Hashed contract records and approval records are described; nothing filed was retrieved. source 1
Institution · 44 · 2026-11-15
Scope: Delaware formation in a startup back-office app; OAuth MCP that prepares but does not pay, sign or file
Institution has an in-app assistant and an OAuth MCP server (401 without a token on November 15). Its MCP page says payments, signatures, staff approvals and provider authorization stay in the user's own workflow; an assistant can help prepare or inspect them. Nothing was executed.
Capability assessment 2026-11-15; sources checked 2026-11-13. Evidence: documented auth untested. Price verification dates are separate.
- A · 8/15An in-app assistant and an external MCP connection can help prepare formation work. source 1
- B · 8/20A documented hosted OAuth MCP server with scoped consent for the founder's company records; the cited page describes accounting and company data, not formation tools. It returned 401 without an account, so tools were not listed. Scored like other non-formation MCP servers. source 1
- C · 2/15No public formation REST API is documented. source 1
- D · 3/15Preparation only: Institution's help article says actual payments, signatures, staff-only approvals and provider authorization stay in the user's own workflow. source 1
- E · 6/10Open work items persist and an assistant can find and prepare them; formation filing status lives in the dashboard. source 1
- F · 5/10A thorough llms.txt with dated prices and scope. source 1 · source 2
- G · 3/5Self-serve OAuth and scoped keys; payment stays in the human workflow. source 1
- H · 5/5Staff approvals are explicit boundaries and every request has a named owner. source 1
- I · 4/5An agent activity log per connection and a document register. source 1
CorpNet · Unscored · 2026-11-13
Scope: Formation Partner API; public MCP searches API documentation only
The public MCP is an API-documentation server, not a formation-order tool. A separate Partner API documents real formation orders/status/documents, requiring a token after a signed agreement; none was executed. Native conversational formation capability remains unscored.
Capability assessment 2026-11-13; sources checked 2026-11-13. Evidence: catalog and documents. Price verification dates are separate.
- A · UnscoredNo verified native conversational formation product was established; API reachability is scored separately and this cell remains unscored. source 1
- B · 6/20The public MCP searches specifications/endpoints; it does not execute formation requests. source 1
- C · 12/15Official Partner API docs specify formation-order operations and required inputs; partner-token execution was not performed. source 1
- D · 6/15The separate partner API documents order creation; no order or filing was exercised, and the docs MCP itself cannot create one. source 1
- E · 8/10Order GUIDs, lifecycle state, RFIs and document download endpoints support documented resumed work. source 1
- F · 9/10Partner schemas and structured filing/pricing/requirements data are published in the API documentation. source 1
- G · 3/5Partner access needs commercial agreement and token issuance, a documented business access gate. source 1
- H · 5/5The documented review lifecycle uses filing/compliance experts and RFIs before submission. source 1
- I · 4/5Order GUIDs, partner correlation IDs, invoices and downloadable filed documents provide a documented trail; no public audit stream was tested. source 1
The Markdown edition carries the same evidence. Corrections: support@corpuslaw.us.
