Annlex vs Descrybe: how they compare in 2026
Annlex and Descrybe both offer AI research over roughly eleven million United States court opinions, priced from $25 a month for solo lawyers, students and the public. Descrybe is stronger on what it checks and where it connects. Its own citator, Cytator, flags whether a case is still good law. A coverage page lists each of its 492 courts with date ranges, and its Legal Engine plugs verification tools into Claude, ChatGPT and Perplexity. Annlex is stronger on the advice line. It tells users on the product itself that it is a research tool, not a lawyer, which matters because it names pro se litigants first among its users. Descrybe also serves non lawyers. Annlex names Claude Sonnet as its model and lets users switch off saved history. Neither holds a security certification of its own.
Which one fits
Choose Annlex if
- You represent yourself or advise people who do. Annlex puts a line on the chat page that it is a research tool, not legal advice, and its terms open by stating the service is not your lawyer and direct users to a licensed attorney.
- You want to check the AI's reading against the opinion. Annlex's Opinion Lens keeps the opinion on screen, anchors the question presented, rule and holding to paragraph numbers, answers only from that opinion, and says so when it cannot.
- You want search free and AI by the question. Annlex gives Boolean, semantic and hybrid search free and unlimited, charges $25 a month for 200 AI queries or $10 for 100 that never expire, and names Claude Sonnet as the model behind answers.
Choose Descrybe if
- You need to know whether a case is still good law. Descrybe's Cytator shows positive, negative, cautionary and neutral treatment at issue level, with forward and backward citing cases, and exposes treatment review as a tool.
- You research inside Claude, ChatGPT or Perplexity. Descrybe Legal Engine supplies citation lookup, quote verification, treatment review and source retrieval to those assistants through an MCP interface, for $25 a month.
- You want to know what the corpus covers before you search. Descrybe's coverage page lists 492 courts and tribunals with an opinion count and date range for each, plus statutes, regulations and court rules, and shows where coverage stops.
At a glance
All 15 axes, side by side
The same grid applied to every vendor in the index, graded from public sources. Hover a grade to see what the letter means on that axis.
AI Centrality
How much of the product is actually AI. Whether the machine learning is the mechanism the buyer is paying for or a feature layered onto conventional software, and whether the vendor is specific about which is which.
The metered unit is the model. Every paid plan, the credit pack and the free allowance count AI queries, which the pricing page defines as each Annlex Chat question, each AI case analysis and each synthesis request. Boolean, semantic and hybrid search are free and unlimited. Customers pay for Annlex Chat's retrieval and synthesis over 10.5 million opinions and for the Opinion Lens tools (Key Passages, Summary, Case Brief, Ask AI). Even the free semantic search runs on ModernBERT embeddings fine tuned for legal text by the Free Law Project. Without the models, what remains is a free search box over a public collection Annlex does not own.
The content itself is model output, which is as central as AI can be. The product was built by AI summarizing judicial opinions, now 10,969,112 opinions across 492 courts and tribunals per the July 2026 coverage page, and that summarization is how the database was built, not a feature on top of it. On top sit DescrybeLM, a purpose built legal reasoning engine; Cytator, an AI citator giving treatment analysis by issue; and an engine layer offering retrieval and verification tools to outside assistants. Without the models there would be no summaries, no citator and no product, only public domain opinions the company never had rights to sell.
Citation Accuracy and Hallucination Disclosure
Whether the vendor publishes measured accuracy on citations and assertions, grounds output to primary sources, and says plainly what its system does when it does not know. Legal has a documented public record of fabricated citations reaching filed briefs, so an untested claim of accuracy is not evidence.
Grounding is real and documented, and Annlex is candid about its limits. The FAQ (version 1.2, March 2026) describes the method. Each question is classified, matched to one of ten research patterns and sent through a pipeline that retrieves opinions before the model writes. Every claim must cite a case from the database, and every citation opens the full opinion, which Annlex holds on its own servers from the CourtListener bulk export. Answers carry a Verify link into Opinion Lens, where a characterization can be checked against the opinion passage by passage. Annlex names the failure grounding leaves: a real case cited correctly and described wrongly, a dissent quoted as the majority, a rule applied in the wrong jurisdiction. The terms list misread precedent, missed or inappropriate authority, outdated law and missed controlling authority as expected failures. No measured accuracy is published, with no test set, citation resolution rate or characterization error rate, and returned authority is not checked for subsequent history. The FAQ's opening answer says the design eliminates the conditions that cause hallucination, while the same page and the terms describe a constraint that shifts the failure mode instead.
Grounding is well structured, without a published measurement. DescrybeLM answers carry a table of authorities linked to primary law, the reasoning is shown at each step, and quote verification and citation resolution are built in as tools. The vendor also discloses against its own interest: the terms say Descrybe does not review or validate outputs for accuracy, truthfulness, relevance or reliability, or to confirm they are not misleading, and earlier material warned users to check summaries against the original opinion. No accuracy figure of any kind is published: no summary fidelity rate, citation resolution accuracy, hallucination rate or test set. A claim in third party material that DescrybeLM beats named frontier models on bar exam benchmarks was not found in vendor material with any method or results, and is not relied on.
Autonomy and Oversight Model
What the system decides on its own, what a lawyer must approve, and whether the vendor documents where the review point sits. A tool that drafts under review and a tool that files without one are different products and different risks.
The product is built around a person checking the machine, and the review surfaces are real. Opinion Lens keeps the opinion on screen at all times, and the generative tools sit beside the text and point to the paragraph an answer rests on. Key Passages anchors the question presented, rule, holding and limitation to paragraph numbers, and Ask AI declines when the opinion does not contain the answer. Annlex Chat links each citation to its opinion and offers a Verify route into Opinion Lens. Annlex's FAQ states that attorneys remain responsible for independently verifying all authority before relying on it, that the tool suits preliminary research rather than replacing verification, and that it should not be anyone's sole source. Nothing acts on a matter; output is research text and downloadable summaries and briefs. The control structure stops short. No threshold at which Annlex Chat declines is described, the FAQ's promise to show confidence levels where applicable is not explained, and nothing addresses what happens after an answer is found wrong.
Oversight is described as product behavior rather than as policy, which is the useful form. DescrybeLM is documented to clarify jurisdiction, posture and key facts with the user before proceeding, which puts a human checkpoint at the start of the task rather than only at the end, and it is documented to tell the user when it needs more information and to flag uncertainty rather than filling gaps with guesses. Reasoning is visible at each step and work product is exported deliberately to Word rather than acted on. In the engine configuration the user can see which Descrybe tools an external assistant called and read the data each returned, which is oversight of a tool chain and not merely of an answer. None of it is quantified or bounded: no statement of when the system proceeds without clarification, no confidence threshold, and no description of what the uncertainty flag actually triggers.
Operational and Outcome Evidence
Named, dated evidence that the product works in production at real firms or legal departments. Case studies with figures and identified customers count. Unattributed testimonials and launch announcements do not.
No production evidence is published: no named customer, firm, law school, library or user count, no case study, testimonial or usage figure, and no outcome measure appears on the Annlex Chat page, pricing, the FAQ, the terms or the Opinion Lens page. The sitemap lists no customer, news or blog page. The product is live with published self serve pricing, and the founder's public profile records a pitch at the Dig South Tech Summit in Charleston, which is launch activity rather than evidence of deployment.
Institutional adoption claims are specific, but none was found in vendor material. Third party research says Descrybe was added to the NSLT curriculum in place of Casetext and approved as a NELLCO electronic resource reaching nearly 150 law libraries. Those would be strong evidence if the vendor published them, since library consortiums and curricula evaluate research tools carefully, but as found they are third party claims. Dated and checkable: coverage by a named legal technology journalist across four product stages from 2024 to 2026, an ABA Woman of Legal Tech award for cofounder Kara Peterson in 2024, and an Anthem Award for Responsible Technology. No customer, deployment, usage figure or outcome measure published by the vendor was found, and the coverage milestones describe the vendor's own build, not customer results. The source basis is recorded as third party estimated.
Privilege and Confidentiality Posture
How client confidences are handled: attorney client privilege and work product treatment, segregation of one client matter from another, whether client data trains any model, and what the vendor commits to in writing rather than in marketing.
Annlex writes real commitments on training and on the model provider into its terms; separation between users is not addressed, and the account of storage is inconsistent. Section 10 of the terms (last modified date shown as 27 February 2026) says saved conversations are not used to train any AI model, Annlex's or anyone else's. Annlex Chat history saves by default to Annlex's own servers for registered accounts, is kept up to one year and then deleted, and can be switched off or deleted immediately. Queries go to Anthropic's API, which does not train on API data and may keep query content up to 30 days, longer where a safety system is triggered. Zero Data Retention with Anthropic is stated to be not yet active. The FAQ ties attorney client privilege to that future arrangement, as positioning rather than a stated handling position. Nothing addresses separation between users or any team or matter structure. The terms' third party section says chat text is stored in no database, and the pricing FAQ says queries are not stored; both conflict with the history paragraph. No data processing addendum or separate customer agreement exists for a firm to sign.
Published commitments cover what firms ask first, but not privilege itself. The security page, updated 30 July 2026 and read 11 September 2026, says customer prompts, files and history are not used to train Descrybe owned models; OpenAI's API is the main model provider, opted out of training, with abuse logs kept up to 30 days; uploaded briefs are not kept once text is extracted; users can delete research history at any time; and the product uses individual accounts with no shared or matter workspaces, so separation is per user and matter walls do not exist. The binding terms of service, described as the legal equivalent of a signed contract, say nothing on these points, so the commitments are policy, not contract. Privilege and work product are not addressed anywhere, including the privacy policy (updated 29 September 2025) and the security page, though the product now takes in users' briefs and pleadings. Where OpenAI processes requests is not stated.
UPL and Professional Responsibility Posture
Whether the vendor is clear that it supplies a tool rather than legal advice, who its audience is, and how it addresses unauthorized practice of law, competence and supervision duties, and jurisdiction limits. ABA Formal Opinion 512 is the reference point. Where the advice line is not the duty a product raises, the axis is read through the nearest professional duty it does raise: judicial conduct rules and the reviewing duty for products sold only to courts, and the duty to bill for time actually spent for products that draft time entries.
Annlex takes a real position on the advice line and repeats it on the product page, without full treatment. The terms open with a section saying the service is not your lawyer, calling it an experimental research tool that does not give legal advice and directing users to a licensed attorney. The FAQ adds that payment does not create an attorney client relationship and lists prohibited uses, including reliance as legal advice, sole source research and FCRA purposes. The Annlex Chat page, which names pro se litigants first among its audiences, says it is a research tool only, not legal advice, and to consult a licensed attorney, so the notice sits at the point of use, facing consumers. Competence is covered in outline: attorneys are told they remain responsible for verifying all authority before relying on it. No jurisdiction limits are named beyond the collection being American case law, bar guidance is left to each practitioner's jurisdiction, and nothing covers supervising the paralegals Annlex lists among its users.
Not addressed, on a product where it most obviously should be. The vendor says the product brings legal reasoning to anyone who needs it, lawyers and nonlawyers alike, and its founding mission is access to justice for people without legal training. A guided reasoning engine that takes a member of the public's question and returns a cited analysis raises the unauthorized practice question directly, and no position was found: no statement that output is not legal advice, no guidance on when to consult a lawyer, and no engagement with any bar rule. The closest is the terms disclaiming review or validation of outputs, which allocates risk without addressing the professional question.
AI Governance and Bias Disclosure
Published governance over model behavior: who owns it inside the vendor, what is tested before release, and what is disclosed about disparate output across matter types, parties, or populations.
Nothing is published: no AI policy, evaluation or release testing, bias or accuracy monitoring, model card, named owner or outside standard. The nearest material is a list of limitations in the terms and FAQ and a design statement on the Opinion Lens page that credibility rests on falsifiability, which describes a product choice rather than a governance mechanism. The gap matters here because the ten research patterns that route every question decide which opinions the model ever sees, and nothing describes how those patterns were built, tested or changed.
Nothing is published on governance: no AI policy, evaluation method, bias or fairness assessment, accuracy monitoring, drift statement, model card, governance body or external standard. The gap matters here because every summary is machine generated, so any systematic bias in summarization flows into every search result and citator treatment, unseen by a user who reads the summary rather than the opinion. The vendor has already rebuilt all its summaries once on newer models, showing that quality depends on the model, and published no evaluation of either version. On 11 September 2026 the privacy policy and the security page, updated 30 July 2026, were also read; the security page says models may be updated for quality, safety, performance or reliability without notice unless the change is material, which concerns the supply chain, not governance.
AI Safety and Data Stewardship
Retention, deletion, access control, and what happens to prompts and documents after they are processed. Whether the vendor states its subprocessors and its incident practice, or leaves the buyer to assume.
Retention and deletion are specific enough to hold Annlex to; the rest is thin. Saved conversations are kept up to one year and then deleted automatically, a user toggle stops saving, saved conversations can be deleted immediately and irreversibly, and no history is saved for users without an account. Google Analytics data is deleted after 26 months with IP anonymization, and server access logs are said to hold request metadata only. Named third parties are listed with their data terms: Anthropic (no training on API data, retention up to 30 days, longer on a safety trigger), Stripe for payments and Google Analytics. Access, correction and deletion requests go to a published privacy address. There are four gaps. The server infrastructure provider is referred to but not named, so the subprocessor list is incomplete. No access control practice is described. Security is stated only as reasonable measures including HTTPS, with nothing on encryption at rest. No incident or breach practice is published. The terms' third party section, which says chat text is kept in no database, also conflicts with the default history described earlier in the same document.
Most of the ground is covered, specifically enough to hold the vendor to. The security page, updated 30 July 2026 and read 11 September 2026, says what is kept (prompts, research history, outputs, metadata and logs) and what is not (uploaded files are discarded once text is extracted). Users can delete history at any time and accounts on request; no zero retention mode is offered; production access is limited to authorized technical staff on a need to know basis; and data is encrypted in transit and at rest on DigitalOcean managed services in the New York region. It names subprocessors with links to their attestations: OpenAI's API, DigitalOcean, Clerk and Stripe, with Google Analytics in the privacy policy. OpenAI API training is opted out. Two gaps remain: no incident or breach practice is published, and no retention period is given for logs and metadata outside the user's deletion control.
AI Liability and Recourse
What the vendor stands behind contractually when its output is wrong. Indemnities, caps, carve outs, insurance, and whether any of it is published or only reachable through a negotiated agreement.
Liability is handled through a standard clause that disclaims all of it. The terms provide the service as is with every warranty disclaimed, and exclude liability for any direct, indirect, incidental, special or consequential damages from use, with no cap figure because nothing is retained to cap. Disputes go to binding AAA arbitration under the Consumer Arbitration Rules seated in Charleston, South Carolina, with class action and jury waivers, under South Carolina law. The recourse that exists concerns availability, not output: prorated credit or refund for a substantial outage, full refunds for billing errors, and 30 days' notice with prorated refunds if the service is discontinued. The terms list the ways AI output can be wrong and put reliance at the user's risk. No indemnity, accuracy undertaking or correction route for wrong output is published.
A published liability position exists and runs almost entirely one way. The terms of service make the user indemnify and hold Descrybe harmless for liability, loss, claims and expenses, including reasonable attorneys' fees, related to use of the service or its outputs, and limit any Descrybe liability to what the user paid in the twelve months before the claim. At published prices, that caps vendor exposure at $300 to $600 per user. The terms also say Descrybe does not review or validate outputs for accuracy. A specific, readable cap is real disclosure a buyer can price. No warranty, accuracy undertaking, service level or correction route was found.
Practice Systems Integration Depth
How deeply the product reaches into the systems legal work already lives in: document management such as iManage and NetDocuments, Word and Outlook, contract lifecycle management, matter management, e-billing, and court filing systems.
No integration into practice systems is published: no document management, practice management, Word or Outlook add in, API or connector. Summaries and case briefs download as formatted documents, which is export rather than integration. The absence is a stated choice: the FAQ argues that tools reaching Claude through MCP connectors cannot qualify for Anthropic's Zero Data Retention while a direct API setup can, so Annlex has chosen not to be an assistant plugin.
Integration is the product, documented at tool level. Descrybe Legal Engine offers citation lookup, quote verification, treatment review and source retrieval to outside assistants over MCP, naming Claude, ChatGPT and Perplexity as supported hosts, plus an Open Connector for building more tools. A user guide describes the flow: the assistant calls one or more Descrybe tools, Descrybe runs the search, lookup, verification or retrieval and returns focused results, and the user can see which tools were called and what each returned. Work exports to Word. The integrations are to AI assistants, not legal practice systems: there is no connection to document management, practice management or a firm's matters.
Deployment Model and Data Residency
Where the software runs and where the data sits. Multi tenant cloud, single tenant, private deployment, on premises, and whether region of residence is a published option or an enterprise conversation.
Annlex is a hosted web application, and little else is stated. The case law collection sits on Annlex's own servers, and research queries are processed through Anthropic's Claude API. No hosting provider, region, tenancy model or processing location is named, and the terms refer only to an unnamed server infrastructure provider. There are no deployment options to compare.
Tenancy and storage region are stated; processing location is half stated. The security page, updated 30 July 2026 and read 11 September 2026, says customer data is stored on DigitalOcean servers in the New York City region, the product runs on provider managed multitenant infrastructure, it is built around individual user accounts, and no single tenant, private or shared workspace option exists. Research requests are processed by OpenAI's API, and nothing says in which region. Queries routed through an outside assistant such as Claude, ChatGPT or Perplexity add a leg whose location is also not described. No residency options are offered.
Security Certifications and Trust Center
Independent attestation a buyer can pull without a sales call: SOC 2, ISO 27001, penetration test summaries, a trust center with current reports and named scope rather than a badge image.
No independent security attestation is published. No SOC 2, ISO 27001 or other certification is claimed, there is no trust center, and the terms describe security only as reasonable measures including HTTPS encryption, with no guarantee of absolute security. Stripe's PCI DSS standards are cited for payment handling, which covers Stripe, not Annlex.
The vendor states plainly that it holds no attestation of its own. The security page, updated 30 July 2026 and read 11 September 2026, says Descrybe does not hold its own SOC 2 or ISO 27001 certification and has begun work toward SOC 2. It relies on providers' programs, linking to trust portals for DigitalOcean (SOC 2 Type II, SOC 3), OpenAI (SOC 2 Type 2, ISO 27001, 27017, 27018, 27701), Stripe (PCI Level 1, SOC 2 Type 2) and Clerk (SOC 2 Type 2). Data is encrypted in transit over TLS and at rest on DigitalOcean, and production access is need to know. A provider's report covers its infrastructure, not the application layer where Descrybe's code, access controls and data handling sit, which is what a firm's security questionnaire asks about. Descrybe is a self funded two founder company charging $25 to $50 a month, and a SOC 2 examination is a material cost against that model. The security page sits in the site footer.
Model Supply Chain Disclosure
Which models sit underneath, whose they are, where they run, and whether the vendor commits to telling customers when that changes. A legal buyer inherits every dependency it cannot see.
The models are named; notice of changes is the gap. Annlex's FAQ states that Annlex presently runs Anthropic's Claude Sonnet as its leading model, calling the Claude Messages API directly, and that semantic search uses ModernBERT embeddings fine tuned for legal text by the Free Law Project. It describes Annlex's own contribution as an orchestration layer that directs leading models. The provider's data terms are stated alongside: no training on API data, retention up to 30 days, and Zero Data Retention not yet active. No model version is pinned, the word presently signals change without any commitment to tell customers when it happens, and where the provider processes requests is not stated.
The provider is named, and change notification is the gap. The security page, updated 30 July 2026 and read 11 September 2026, says Descrybe uses OpenAI API models for summaries and research outputs, that OpenAI's API is its main LLM provider, that the exact model may vary by feature and change over time for quality, safety, performance or reliability, and that users are not notified of each update unless it materially affects terms, privacy or data processing. This settles earlier conflicting signals: the terms disclose third party models without naming them, and a third party directory had called DescrybeLM the company's own model. The page also says OpenAI training is opted out and abuse logs are kept up to 30 days, linking to OpenAI's data controls. No specific model or version is named, there is no commitment to notify of model changes, and where OpenAI processes requests is not stated.
Commercial Transparency
Whether a buyer can learn what this costs without entering a sales process: published rates, the unit being charged, what sits behind an enterprise tier, and what implementation adds.
The full price list is public and the unit is defined. Starter is $25 a month for 200 AI queries and Power is $75 a month for 600, both with a seven day trial that requires a card; a one time pack of 100 queries costs $10 and never expires; three AI queries are free without an account, and Opinion Lens allows three questions per opinion before signup. Boolean, semantic and hybrid search are free and unlimited. The pricing page defines what counts as a query, and the terms publish trial conversion, the absence of rollover, 30 days notice of price increases and the refund rules for packs and subscriptions. Signup is self serve, so nothing is added for implementation, and only volume beyond the Power plan is by contact. One loose end: the refund terms refer to annual subscriptions, and no annual plan is published.
Exact prices are published for every tier: $25 per month for Descrybe Legal Engine and $50 per month for the full Descrybe Platform with the Engine included. The unit is a monthly subscription per user. The vendor says every feature is included at either tier, so the headline price does not buy a limited subset. It also explains its pricing: it is self funded, without outside investor timelines or enterprise sales costs, and prices for the work rather than the market. A buyer can work out total cost from the public site without contacting anyone.
Firm and Practice Coverage
Who the product is actually built for. AmLaw, midlaw, small firm and solo, in house departments, government and courts, and which practice areas are supported rather than merely claimed.
Audience and use limits are stated precisely; the limits of the case law collection are not. Annlex names pro se litigants, law students, solo practitioners and small firms priced out of Westlaw and Lexis, paralegals and journalists. It lists appropriate uses (case discovery, preliminary research, academic work, journalism) and prohibited ones (legal advice, sole source research, FCRA purposes), and says plainly the tool suits preliminary research rather than replacing verification. The collection is described as 10.5 million full text opinions from 3,355 federal and state courts, 1658 to the present, with 71 million citation links and a taxonomy of 20 legal areas and more than 1,125 concepts, updated quarterly from CourtListener's bulk export. Annlex's own site does not list courts or date ranges by court, say what curation from CourtListener left out, or say that statutes, regulations and secondary sources are not included. The FAQ also describes opinions as retrieved live from CourtListener, while the Annlex Chat page and the quarterly cadence describe a stored copy.
Coverage is listed court by court, with limits stated. The coverage page (descrybe.com/coverage, data as of 18 July 2026) lists 492 courts and tribunals and 10,969,112 opinions: federal (137 courts, 3,221,272 opinions), state (201 courts, 7,324,869), bankruptcy (97 courts, 80,941), specialized and agency tribunals (47 tribunals, 340,850) and tribal courts, plus statutes, regulations, constitutions, session laws and court rules. Each court shows its opinion count and first and latest dates, so a researcher can check whether a recent decision should be present. Most active supreme and appellate courts run to the first days of July 2026, and gaps are shown, such as Connecticut Superior Court ending in December 2014 and the Alabama Court of Appeals in 1999. No refresh schedule is stated beyond the as of date, and a few rows, including the New Hampshire district court and the Minnesota and Arizona appellate courts, show latest dates in the future, which look like source metadata. The vendor says it serves lawyers and nonlawyers alike.
The 12 legal signals, side by side
Recorded rather than graded. These are the questions a practitioner has to answer before a tool touches a client matter, and the answers are taken from public material only.
Client Data in Training
Can material a lawyer puts into this product be used to train a model?
The terms a user accepts by using the site carry the commitment in their privacy section: saved conversations are not used to train any AI model, Annlex's or anyone else's. The model provider position is stated too, with Anthropic's commercial API terms described as excluding API data from training. As written the commitment covers saved conversations, and unsaved queries are said not to be kept by Annlex at all. It is contractual because the privacy policy is section 10 of the terms document itself, not a separate policy page.
Stated in policy, in the form that matters. The security page, updated 30 July 2026 and read 11 September 2026, says Descrybe does not use customer prompts, files or conversational history to train Descrybe owned models, that its main model provider is OpenAI's API, that API inputs are not used for OpenAI training by default, and that Descrybe has opted out. That covers both the vendor's own models and the provider underneath.
It is policy rather than contract: the terms of service only disclose that third party AI models process primary law and carry no matching term. The privacy policy, updated 29 September 2025, was also read and is silent on training.
Prompt and Output Retention
How long does the product keep what a lawyer typed, and can that be set to zero?
Retention on Annlex's side is under the user's control: history saves by default for registered accounts, a Save history toggle stops it, saved conversations delete immediately and irreversibly, and anything kept is deleted automatically after one year. Zero is not available end to end, and Annlex says so: queries pass through Anthropic's API, which may keep content up to 30 days, longer where a safety system is triggered, and Zero Data Retention is stated as not yet active.
The third party section of the same terms says chat text is kept in no database, which the history paragraph contradicts.
Retention is described and the user controls it by deletion rather than by a window. The security page (updated 30 July 2026, read 11 September 2026) states that Descrybe retains account and product data needed to operate the service, which may include prompts, research history, generated outputs, metadata and operational logs; that the only upload surface is brief review and uploaded files are not kept once the text is extracted; that no customer facing zero retention mode is offered; and that users can delete their historical entries at any time.
On the provider side it states that OpenAI may retain API abuse monitoring logs for up to 30 days. Recorded as customer controlled with no zero option: deletion on demand is real control over the research history, and the vendor says plainly that zero retention is not available. What the deletion statement does not reach is the operational log and metadata retention, for which no period is stated. Corrected from not addressed on 11 September 2026.
Ethical Walls and Matter Segregation
Does retrieval respect the firm’s ethical walls, or can the model read across them?
Nothing addresses separation between users, teams or matters. The product is built around individual accounts, each with its own history, and no shared workspace or permission model is described.
The permission model is documented and it is the simplest one there is: one user, one account, nothing shared. The security page (updated 30 July 2026, read 11 September 2026) states that Descrybe is structured around individual user accounts rather than shared organization workspaces, that saved searches, history and product data are associated only with that user's own account, that access is protected through application and database access controls, and, stated rather than left to inference, that no shared organization workspaces, matter based workspaces or separate file and vault permissioning are offered, on provider managed multi tenant infrastructure.
So walls at matter level do not exist in the product and the vendor says so. A firm that needs them keeps them outside the tool, by giving each user a separate account. Recorded as own model, documented, because the isolation model is published and enforced by the vendor; the summary carries the limit. Corrected from not addressed on 11 September 2026.
Third Party Request and Subpoena Notice
If someone subpoenas the vendor for a firm’s data, does the firm hear about it first?
The terms say saved conversations are not shared with third parties except as needed to operate the service or where the law requires it. Nothing commits Annlex to telling the user about a legal demand, or reserves the right not to, and no transparency report is published.
No clause on government or law enforcement requests, no commitment to notify a user before producing their data and no transparency report is published. The terms of service cover termination, permitted use and liability, not third party requests. The privacy policy, updated 29 September 2025, covers account information, named third party services and children's data, not this. The security page, updated 30 July 2026, lists legal and compliance obligations among reasons authorized staff may access production data, but says nothing about disclosure to authorities or notice to the user.
Primary Law Corpus Provenance
Where does the law in this product come from, and does the vendor have the right to use it?
Sources are named at dataset level with a stated cadence. The opinions are described as loaded from the CourtListener bulk export maintained by the Free Law Project. Historical material is attributed to the Harvard Law School Library Innovation Lab's Caselaw Access Project, the Library of Congress, Public.Resource.Org, Lawbox and Justia, and the data is updated quarterly. The rights basis is described only as publicly available legal data and public court records, which speaks to availability rather than a license or public domain basis for each source, and Annlex's own site publishes no list by court.
Sources are named at dataset level and listed court by court, with no license basis stated. The Harvard Caselaw Access Project is named as a source. The coverage page (data as of 18 July 2026, read 11 September 2026) lists 492 courts and tribunals and 10,969,112 opinions across federal, state, bankruptcy, specialized and agency, and tribal courts, plus statutes, regulations, constitutions, session laws and court rules, with an opinion count and date range for every court and source availability shown where applicable.
Not stated: the license or public domain basis for any source, or which source feeds which court. The content is AI summaries of opinions rather than the opinions alone, so provenance raises a second question the vendor does not address: what the summarization step did to the source.
Good Law Verification
Does the product tell you when the authority it just cited has been overruled?
The product tells the user to verify and does not check subsequent history itself. The terms direct users to verify independently and consult primary sources, and list output that does not reflect current law as a known failure; Annlex's FAQ says attorneys remain responsible for verifying all authority. A citation network of 71 million links shows which cases cite an opinion, without treatment flags. The Verify link in Annlex Chat checks a characterization against the opinion, not whether the authority is still good law. No citator, licensed or computed, is named.
The vendor has its own treatment signal. Cytator launched June 2025 in the Legal Research Toolkit, showing treatment flags in the familiar positive, negative, cautionary and neutral convention, with analysis by issue rather than a single verdict per case. It shows forward treatment with binding and nonbinding citing cases, and a backward citator showing how an opinion treated each authority it relied on. Treatment review is also offered to outside assistants through Descrybe Legal Engine.
It is the vendor's own AI citator, not a licensed one such as Shepard's or KeyCite, and no accuracy, coverage or agreement measure against an established citator is published, which a practitioner would want before relying on a negative flag.
Refusal and Uncertainty Behavior
What does the product do when the answer is not in the corpus?
Documented for Opinion Lens, where Ask AI answers only from the open opinion, and Annlex says that when the opinion does not answer, it says so rather than guessing, calling that refusal the feature. The public demo on the page shows answered questions only, so the no answer path is described, not shown. For Annlex Chat, the FAQ promises confidence levels where applicable without describing them, and no abstention path is stated.
Documented. The vendor says DescrybeLM tells users when it needs more information and flags uncertainty rather than filling gaps with guesses, and that the engine clarifies jurisdiction, posture and key facts before answering an underspecified question. That is an explicit no answer path described as product behavior. The terms add that outputs are not reviewed or validated for accuracy. No published evaluation, transcript or example shows the behavior working, and no threshold or trigger for the uncertainty flag is described.
Fabricated Citation Record
Does a public court record exist addressing fabricated or hallucinated legal citations in output from this product?
The AI Hallucination Cases database maintained by Damien Charlotin, in its full downloadable export, and the wider public record show no court order, opinion or disciplinary record addressing fabricated or hallucinated citations in output from Annlex.
None located. General web searches combining the vendor and product names with court, opinion, sanction, hallucination and fabricated citation terms returned nothing on 29 Aug 2026. No docket database or court record tracker was searched. This records what the search found and is not a clearance. The vendor's terms disclose that it does not validate outputs, so a defective citation is an acknowledged possibility rather than one the vendor denies.
Bar Guidance Alignment
Has the vendor engaged in public with the ethics opinions its buyers are bound by?
Annlex's FAQ says bar association guidance on AI use in legal practice is evolving and that practitioners should consult their own jurisdiction's rules. No ethics opinion, including ABA Formal Opinion 512, is named or mapped.
No named ethics opinion, ABA Formal Opinion 512, state bar guidance or engagement with professional conduct rules is published, though the cofounder holds an ABA Woman of Legal Tech recognition and the company positions itself around access to justice. The product is offered to non lawyers alongside lawyers.
Billing and Fee Posture
Does the vendor address what happens to the bill when the work takes an hour instead of six?
Annlex sells speed and price to the researcher, with case law searchable in seconds and relevant opinions surfaced quickly for solo and small firm practitioners, and says nothing about how AI assisted research should be billed or disclosed to a client. Part of the named audience sits outside any fee relationship (pro se litigants, students, journalists), which does not change the question for the practitioners Annlex also targets.
Nothing published covers billing for AI assisted time or a record a practitioner could show a client of what was machine generated. The vendor's own prices, $25 and $50 a month with all features included, are its charge to the subscriber, not a position on the practitioner's billing. No time record, audit record or fee guidance is published.
Outside Counsel Guideline Readiness
Can a firm get this vendor through a client’s AI clause without a bespoke negotiation?
The terms name the third parties that process data, Anthropic for AI queries, Stripe for payments and Google Analytics, each linked to its privacy terms, and Annlex's FAQ names Claude Sonnet as the model. The server infrastructure provider is referred to without being named, so the list is incomplete, and no disclosure material for clients is published.
A subprocessor and model provider list is published, each entry linked to that provider's own attestation. The security page (updated 30 July 2026, read 11 September 2026) names OpenAI's API as the primary model provider, DigitalOcean for hosting and storage in its New York region, Clerk for authentication and Stripe for payments, with links to each provider's trust portal or security documentation and the certifications each holds; the privacy policy (updated 29 September 2025) adds Google Analytics for site analysis.
That is the list a firm forwards to a client under outside counsel guidelines, and it exists without a sales conversation. What is not published is client facing disclosure material of Descrybe's own, and Descrybe holds no attestation of its own to add to the pack, which it states plainly. Corrected from not addressed on 11 September 2026.
Court Disclosure Support
If a judge’s standing order requires an AI disclosure, can the product produce one?
Nothing addresses court disclosure orders or certification of AI use. Case briefs and summaries download as formatted documents, and Opinion Lens output says it was generated from the one opinion alone, but no record of the model used, sources retrieved or human check is produced for a filing.
Partial record, strong on sources. DescrybeLM answers carry a table of authorities with verified citations linked back to the primary law, the reasoning is stated to be visible at every step, quote verification and citation resolution are available as discrete tools, research sessions are saved and revisitable, and work product exports to Word, so a practitioner can produce what was retrieved and relied on. In the engine configuration the user can additionally see which tools an assistant called and read what each returned, a trail at the tool level.
What is missing is the other two elements a standing order asks for: nothing records which model produced a given output, and no human verification record is captured or exportable. The vendor's disclosure that it does not validate outputs makes the human verification gap more consequential, since the checking is entirely the practitioner's and nothing in the product evidences that it happened.
The questions both sides leave open
Derived from the records above rather than written, so it cannot favor either vendor. Take these into both conversations and ask each side the same question.
- AI Governance and Bias Disclosure
- Security Certifications and Trust Center
Product updates
The latest logged changes from each vendor, newest first, each linked to its source.
Descrybe
-
Integration / interoperability
Descrybe released its Legal Engine plugin for ChatGPT Enterprise.
Source -
Privilege / confidentiality
Descrybe published a security page stating its data handling position: customer prompts, files and conversational history are not used to train Descrybe owned models; the primary model provider is OpenAI's API, with Descrybe opted out of training and OpenAI abuse monitoring logs retained up to 30 days; uploaded files are discarded once text is extracted; research history can be deleted by the user at any time, with no zero retention mode offered; data is stored on DigitalOcean in the New York region on multi tenant infrastructure, encrypted in transit and at rest; the product runs on individual user accounts with no shared or matter based workspaces; and Descrybe holds no SOC 2 or ISO 27001 certification of its own, with SOC 2 work begun.
Source -
Product / capability
Descrybe published a coverage page enumerating its primary law corpus court by court: 492 courts and tribunals and 10,969,112 opinions as of 18 July 2026, across federal, state, bankruptcy, specialized and agency, and tribal courts, plus statutes, regulations, constitutions, session laws and court rules, with an opinion count and a first to most recent date range for every court.
Source
In summary
Annlex
Annlex, from Annlex Systems LLC of Charleston, South Carolina, is a case law research platform over 10.5 million United States opinions from 3,355 courts. Its collection is loaded from the CourtListener bulk export and updated quarterly. Annlex Chat routes questions through ten research patterns and links every citation to the full opinion, and Opinion Lens analyzes a single opinion paragraph by paragraph. According to the AI Legal Index, Annlex names Claude Sonnet as its model, prices AI queries from $25 a month with search free, and states it is not legal advice.
Descrybe
Descrybe, founded in 2023 in the Boston area and self funded, is a US primary law research platform over 10,969,112 AI summarized opinions from 492 courts and tribunals, with statutes, regulations and court rules. DescrybeLM answers with a table of authorities, Cytator gives issue level treatment flags, and Descrybe Legal Engine exposes its tools to Claude, ChatGPT and Perplexity. According to the AI Legal Index, Descrybe names OpenAI as its model provider and stores data with DigitalOcean in New York. Its coverage page lists each court with an opinion count and date range, and it charges $25 a month for its Legal Engine and $50 for the full platform.
Questions buyers ask
Annlex vs Descrybe: which is better for low cost case law research?
Descrybe adds its own citator, a court by court coverage list and a connector for AI assistants. Annlex draws the advice line clearly on the product and offers free unlimited search. People researching without a lawyer have the clearer warning from Annlex. From the AI Legal Index, based on each vendor's own published materials as of September 27, 2026. No vendor pays for placement.
Does Annlex or Descrybe check whether a case is still good law?
Descrybe does, through its own citator, Cytator, which shows positive, negative, cautionary and neutral treatment at issue level. Annlex does not check subsequent history. It shows which cases cite an opinion through 71 million citation links and tells users to verify authority themselves. From the AI Legal Index, based on each vendor's own published materials as of September 27, 2026. No vendor pays for placement.
Which AI models do Annlex and Descrybe use?
Annlex names Anthropic's Claude Sonnet, called directly through the API, and ModernBERT embeddings for semantic search. It states zero data retention with Anthropic is not yet active. Descrybe names OpenAI's API as its primary provider, opted out of training, with abuse logs kept up to 30 days. Neither pins a model version or commits to notice of changes. From the AI Legal Index, based on each vendor's own published materials as of September 27, 2026. No vendor pays for placement.
How much do Annlex and Descrybe cost?
Annlex charges $25 a month for 200 AI queries or $75 for 600, with 100 queries for $10 that never expire and search free. Descrybe charges $25 a month for its Legal Engine and $50 a month for the full platform, with every feature at either tier. Both are self serve with no setup fee. From the AI Legal Index, based on each vendor's own published materials as of September 27, 2026. No vendor pays for placement.
Neither vendor paid for inclusion, placement or a grade, and neither reviewed this page before it published. Everything on it comes from public material on the dates shown. How the index grades.
Three points to weigh. Descrybe's product serves non lawyers alongside lawyers and publishes no statement that its output is not legal advice. Annlex's terms say in one place that chat text is stored in no database and in another that history is saved for a year by default. Neither vendor holds a SOC 2 or ISO certification of its own. Descrybe states that SOC 2 work has begun. On 17 September 2026 Descrybe released a Legal Engine plugin for ChatGPT Enterprise. Neither vendor reviewed this page.