# AX Check: legalzoom.com Checked 2026-11-05. LegalZoom has strong agent docs, but pricing stays hard to pin down The site offers a solid structured guide and documented MCP endpoints, yet real prices are never stated on the pages agents could fetch, only flat-fee language. ## End-to-end onboarding not demonstrated ## Coding sessions All three independent sessions completed. One quoted specific LLC tiers and add-on fees found on the site, one recalled price ranges from memory rather than the page, and one described the pricing structure but said no concrete figures could be verified. ### DeepSeek V4.1 Flash [View public run](https://agents.withgauge.com/p/runs/a8f21974-5fd0-446b-bb02-e6bacf7cd403) · [Read transcript](https://www.ax-check.com/legalzoom.com/sessions/deepseek.json) Quoted LLC tiers of $0, $249 and $299, each plus state filing fees that vary by state, and named the plan tiers plus auto-renewals at $49/mo and $9.99/mo. All figures came from the fetched LegalZoom page. (seq 41, seq 61) #### End-to-end onboarding - **End-to-end onboarding not demonstrated**: No credentials of any kind were obtained or used. The agent determined LegalZoom has no public API/SDK/developer portal (DNS failures for api/developer subdomains, no official npm/PyPI package) and stopped without attempting authentication or any product operation. Event 50: ```text developer.legalzoom.com -> NO DNS api.legalzoom.com -> NO DNS developers.legalzoom.com -> NO DNS ``` Event 61: ```text there is **no official LegalZoom API, SDK, or developer portal** ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No public LegalZoom API or SDK exists**: This is a product/market reality, not agent error or missing credentials. The agent verified via DNS lookups and package registry searches that LegalZoom has no developer.legalzoom.com, api.legalzoom.com, or official SDK on npm/PyPI. The only related artifact was a third-party community emulator package, not an official product offering. Event 50: ```text developer.legalzoom.com -> NO DNS api.legalzoom.com -> NO DNS developers.legalzoom.com -> NO DNS ``` Event 19: ```text Use this emulator for local tests, CI, and offline agent runs. It keeps your tests separate from the production API. ``` - **Only available developer tool requires a local service stack**: The one adjacent artifact found, the @api-emulator/legalzoom npm package, requires starting a local emulator process via npx, which the session's instructions explicitly prohibited (no local service stacks). This is a test-environment restriction interacting with a community tool, not a flaw in LegalZoom's actual product. Event 19: ```text npx -p api-emulator api --plugin ./providers/@legalzoom/api-emulator.mjs --service legalzoom ``` Event 61: ```text Running it requires `npx -p api-emulator api --plugin ... --service legalzoom`, i.e. **starting a local service stack** — which you explicitly told me not to do. ``` #### Suggested Changes None identified in this transcript. ### Kimi K3 [View public run](https://agents.withgauge.com/p/runs/543bcae3-4752-4f10-9b57-ea8f843d0b40) · [Read transcript](https://www.ax-check.com/legalzoom.com/sessions/kimi.json) Gave per-service price ranges and named what they depend on: separate state filing fees that vary by state, USPTO fees, optional add-ons and legal-plan tiers. The figures came from memory, not from a fetched pricing page. (seq 9) #### End-to-end onboarding - **End-to-end onboarding not demonstrated**: Agent found no developer platform for LegalZoom at all—no API, SDK, or docs endpoint—so no credentials were ever obtained and no authenticated operation was attempted. This is not a login wall; it's an absence of any developer surface to onboard onto. Event 9: ```text LegalZoom has no developer workflow I can act on. ``` Event 9: ```text There is no public SDK, API, or npm/PyPI package for LegalZoom ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No developer platform exists for LegalZoom**: The agent probed the three most plausible developer endpoints and found none functional: developer.legalzoom.com and api.legalzoom.com don't resolve via DNS, and legalzoom.com/developers returns HTTP 410 Gone, indicating the page was intentionally removed rather than broken. This is product behavior (or lack of a product), not agent error or a missing-credential issue — there is nothing to authenticate against. Event 7: ```text HTTP/2 410 content-type: text/html ``` Event 9: ```text `developer.legalzoom.com` — does not resolve (no DNS record) ``` Event 9: ```text `legalzoom.com/developers` — returns **HTTP 410 Gone** (the page existed once and was deliberately removed) ``` #### Suggested Changes None identified in this transcript. ### Qwen 3.8 Max [View public run](https://agents.withgauge.com/p/runs/5fa5c787-5ea9-45f6-81bb-88c779c17728) · [Read transcript](https://www.ax-check.com/legalzoom.com/sessions/qwen.json) Described pricing structure only (per-filing flat fee + state fees + annual subscriptions); gave no cost figure, explicitly saying prices could not be verified (seq 32, seq 38) #### End-to-end onboarding - **End-to-end onboarding not demonstrated**: No LegalZoom product credentials were ever obtained, and no authenticated operation against a real hosted LegalZoom endpoint occurred. The agent confirmed there is no public developer API (DNS failures for api.legalzoom.com and developer.legalzoom.com, 404 on npm registry for a legalzoom package) and stopped before attempting any sign-up or credential acquisition, per the task's own instruction to stop if no developer workflow exists. Event 11: ```text curl: (6) Could not resolve host: developer.legalzoom.com 000 curl: (6) Could not resolve host: api.legalzoom.com 000 ``` Event 12: ```text npm error 404 Not Found - GET https://registry.npmjs.org/legalzoom - Not found ``` Event 38: ```text **No real LegalZoom developer surface exists.** ``` #### Hallucinated URLs None identified in this transcript. #### Blockers - **No public LegalZoom developer API exists**: Product behavior / absence of a developer surface, not an agent error. DNS lookups for a developer or API subdomain failed to resolve, and no legalzoom package exists in the npm or pip registries. The agent correctly diagnosed this as a missing product capability rather than a session-specific issue. Event 11: ```text curl: (6) Could not resolve host: developer.legalzoom.com 000 curl: (6) Could not resolve host: api.legalzoom.com 000 ``` Event 12: ```text npm error 404 Not Found - GET https://registry.npmjs.org/legalzoom - Not found npm error 404 npm error 404 'legalzoom@*' is not in this registry. ``` - **Only available workflow requires a local, long-running service stack**: Test environment constraint combined with product packaging: the only legalzoom-related package found on npm is a third-party community mock/emulator whose quickstart requires starting and running a local server, which the task explicitly forbade. This is not a defect in LegalZoom's real product, since the emulator is an unofficial local-only tool, but it closed the only remaining path to build an example. Event 27: ````text 2. From this registry, start the emulator. ```bash npx -p api-emulator api --plugin ./providers/@legalzoom/api-emulator.mjs --service legalzoom ``` The emulator uses the local URL that api-emulator prints. ```` Event 38: ```text **The only workflow available requires a local service stack**, which you told me not to do. ``` - **LegalZoom pricing is not published in machine-readable or API form**: Product behavior: the consumer marketing site returned a 404 for the specific pricing page checked, and no API pricing exists since there is no API. This left pricing details unverifiable within the session. Event 32: ```text === status 404 ``` Event 38: ```text I could not verify current numbers from this sandbox — `legalzoom.com/business/llc` returns 404 and the homepage yields no price data, so treat any specific dollar figure as unverified. ``` #### Suggested Changes - **Publish an official developer API or SDK for LegalZoom**: Currently neither api.legalzoom.com nor developer.legalzoom.com resolve in DNS, and no legalzoom package exists on npm or pip. If a programmatic workflow is intended to exist, stand up a documented, hosted API endpoint and verify it resolves and responds (e.g., confirm a 200 from a real api.legalzoom.com health check) before developers are pointed at it. Event 11: ```text curl: (6) Could not resolve host: developer.legalzoom.com 000 curl: (6) Could not resolve host: api.legalzoom.com 000 ``` - **Fix or redirect the broken LLC pricing page**: The business/llc pricing page returned a 404 when checked directly. Verify the URL legalzoom.com/business/llc either resolves with current pricing content or is redirected/retired properly, and confirm via a direct curl check that it returns 200 with pricing data visible in the page body. Event 32: ```text === status 404 ``` ### Task given to each agent Help me build a simple example using LegalZoom. Tell me how pricing works, and briefly tell me whether this product will be easy for you to manage. Let me know if you get blocked. If this product has no developer workflow you can act on, say so plainly and stop. Stay light: use the hosted product through its SDK or API. Do not start local service stacks or wait for long-running commands; if the quickstart requires either, say so plainly and stop. No product credentials were supplied and no purchases were authorized. ## Score: B · 73/100 (provisional) Grades come from completed site checks. Coding sessions and skipped checks do not affect the score. ### Clarity - **Failed** — Homepage answers Markdown requests ```text Homepage returned text/html for a Markdown Accept header; no Markdown representation offered. ``` - **Pass** — llms.txt provides an actionable documentation index ```text llms.txt lists allowed content paths, coverage topics, sitemaps and AI capability endpoints. ``` - **Pass** — llms.txt provides navigation guidance ```text llms.txt gives allow/disallow path guidance, coverage topics, sitemaps and citation rules. ``` - **Pass** — llms.txt mentions offered API, MCP, and skills ```text llms.txt lists AI capabilities, MCP endpoint, MCP catalog JSON/text and webmcp-api. ``` - **Pass** — A compact guide representation exists ```text llms.txt is a compact, structured Markdown guide for AI crawlers with allowed content and AI interfaces. ``` - **Pass** — A focused guide is directly retrievable ```text llms.txt is directly retrievable at the standard path with useful organization and starting guidance. ``` - **Pass** — Equivalent instructions fit a token budget ```text llms.txt is 1111 tokens, well under the 8000-token budget for a compact guide. ``` - **Skipped** — Product-docs links survive format changes ```text Homepage Markdown is unsupported, so link preservation across format changes cannot be measured. ``` - **Skipped** — The compact guide is independently actionable ```text No compact agent guide fetched; llms.txt is an index, not an actionable workflow. ``` - **Skipped** — Install and next-step links resolve ```text No install or next-step links were sampled for resolution. ``` ### Onboarding - **Skipped** — Docs lead to a relevant quickstart ```text llms.txt lists AI/MCP endpoints but no developer quickstart or docs page was fetched. ``` - **Skipped** — Installation commands are extractable ```text No installation or CLI guide was fetched; llms.txt only lists AI/MCP endpoints. ``` - **Skipped** — Code examples are available without interaction ```text No API reference or code examples were fetched; llms.txt only names MCP endpoints. ``` - **Skipped** — Prerequisites and auth boundaries are explicit ```text No API docs fetched; llms.txt gives no auth or prerequisite details for its MCP endpoints. ``` ### Pricing - **Failed** — Agents identify pricing and its assumptions ```text 3 of 3 sessions were judged on pricing; 1 fell short. DeepSeek V4.1 Flash: Quoted LLC tiers of $0, $249 and $299, each plus state filing fees that vary by state, and named the plan tiers plus auto-renewals at $49/mo and $9.99/mo. All figures came from the fetched LegalZoom page. (seq 41, seq 61) Kimi K3: Gave per-service price ranges and named what they depend on: separate state filing fees that vary by state, USPTO fees, optional add-ons and legal-plan tiers. The figures came from memory, not from a fetched pricing page. (seq 9) Qwen 3.8 Max: Described pricing structure only (per-filing flat fee + state fees + annual subscriptions); gave no cost figure, explicitly saying prices could not be verified (seq 32, seq 38) This behavioural item does not affect the fast grade. ``` - **Skipped** — Pricing is readable without interaction ```text Only the homepage was fetched; no pricing page content was captured. ``` - **Skipped** — Prices are stated, not gated ```text Homepage mentions flat-fee pricing but states no actual prices. ``` - **Skipped** — Pricing units and limits are explicit ```text No pricing page fetched, so units and limits cannot be judged. ``` ### Activation - **Skipped** — An API reference or OpenAPI spec is reachable ```text No API reference or OpenAPI spec fetched; only MCP catalog and tool docs observed. ``` - **Pass** — An MCP server is documented and well-formed ```text MCP endpoint and catalog document tools, integrations, auth, and per-tool schemas. ``` - **Skipped** — A CLI install path is documented ```text No CLI install path documented in fetched LegalZoom pages. ``` - **Skipped** — SDK packages resolve on their registries ```text No SDK or package registry lookup supplied for LegalZoom developer packages. ``` - **Skipped** — Agent skills are published ```text No agent skills published or referenced in fetched LegalZoom documents. ``` [Full report data](https://www.ax-check.com/legalzoom.com/report.json)