UniCourt

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.

Machine learning is the mechanism that turns fragmented court filings into a usable dataset, on a platform whose delivery layer would function without it. The vendor describes AI-powered data extraction surfacing data buried deep in dockets and documents, with standardisation and deduplication as the stated output, and names DEEP as its AI-powered docket extraction and enrichment platform. Remove the models and what remains is aggregation and delivery of raw court records through APIs, which is a real product but a materially worse one. That places the AI as the engine of the core capability layered on a data pipeline, which is the B band rather than the A.

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 total and measurement is absent, which is the B profile exactly. Every record UniCourt returns is the actual court document or docket entry, retrievable to source, so there is no gap between what the platform asserts and what a user can open and read; this is the strongest grounding limb in the pull. The vendor also publishes a real limitation rather than hiding it: the public records policy states that records may contain errors or be incomplete, inaccurate, or not the most currently available information, and are provided as is. What is missing is any measurement of the thing the AI actually does. Extraction, standardisation and deduplication are claimed as unmatched with no accuracy or error rate, no benchmark, no test set and no published evaluation located on 31 Aug 2026. One limb of this axis does not bite: a citator or good-law check is not applicable to a platform that delivers records rather than legal propositions, and is neither credited nor penalised here.

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 extraction runs unattended and no oversight model is published. Machine learning classifies, normalises and deduplicates docket data before a customer ever sees it, and for API and customers that output flows straight into their own systems with no review surface in between. Searched the home page, pricing page, enterprise API page, PACER API page, general disclaimer, terms of service and public records policy on 31 Aug 2026: nothing describes what the models decide alone, no confidence or exception handling is documented, and no correction or reporting route for mis-extracted data was located. The mitigation is structural rather than stated, in that every extracted field sits alongside a retrievable source document, so an attentive user can check any value against the original.

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.

Logos stand in for evidence. The pricing page carries a customer strip including DLA Piper, Paul Hastings, Morrison Foerster, Alston & Bird, Akerman, Pillsbury, Manatt, Stikeman Elliott and Seyfarth Shaw, alongside CNN, The Wall Street Journal, Financial Times, NBC News, RBC, Colliers and Coindesk, which is a serious roster spanning large firms, media and financial services. Nothing sits behind it. Searched the same surfaces on 31 Aug 2026 and located no named individual, no attributed testimonial, no case study, no figure for what any customer achieved, and no deployment scope or date. Two names in the strip are misspelled, as Seyearth Saw and Stikeman Elliot, which is a small quality signal on the one page carrying the vendor's customer evidence.

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.

The product's central confidentiality question is disclosed plainly and then left unaddressed. UniCourt's CrowdSourced Library works by pooling retrieval: the vendor states that any time one user downloads a court document or docket it is added to the library and made freely available to all UniCourt users, which is why no court fee applies to material already pulled. The material is public court record and the vendor states that sealed and restricted documents are not available and nonpublic information is not distributed, so this is not disclosure of privileged content. But the pattern is exposed, and the PACER API page confirms that search results show which cases are already held and when they were added and last updated, so a subscriber can infer that someone retrieved a given docket and roughly when. Nothing published addresses whether a firm's own search history, tracked cases or saved work are visible to anyone else, and no training, retention or matter-segregation position was located on 31 Aug 2026.

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.

A published disclaimer that addresses the advice line directly and in the product's own terms. The general disclaimer states that information on the site should not be construed as legal advice, that others may reach contrary conclusions on the same or different information, that UniCourt expressly disclaims all liability for actions taken or not taken based on the information, that it makes no opinion or endorsement as to the quality, competency or character of any person or entity on the site, and that transmission of information creates no attorney-client relationship. The endorsement limb is the notable one, since the platform sells analytics on named attorneys and firms and the vendor declines to stand behind any inference a user draws about them. What holds this at B rather than higher: no bar or ethics guidance is named anywhere, including ABA Formal Opinion 512, and no jurisdiction or practice limits are stated. Checked 31 Aug 2026.

AI Governance and Bias Disclosure

Published governance over model behaviour: who owns it inside the vendor, what is tested before release, and what is disclosed about disparate output across matter types, parties, or populations.

No governance position for model behaviour was located. Searched the home page, pricing page, enterprise API page, PACER API page, general disclaimer, terms of service, public records policy and privacy policy on 31 Aug 2026, and ran two targeted searches for a security, trust or responsible AI page; none exists. Nothing names an accountable owner, describes pre-release testing, publishes a responsible AI framework, or addresses uneven output. The exposure here is quieter than on a judicial prediction product but real: extraction and entity resolution decide which attorneys, firms and parties are matched to which cases, and errors in that matching propagate into the analytics customers buy and into downstream systems the data is pushed to.

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.

A privacy policy covers the collection relationship and no operational security material exists. The policy addresses what is collected, the CCPA framework and user rights, and offers a redaction request route for a court record appearing in online search engines, which is a real remedy rather than a statement of principle. Beyond that the ground is empty: searched the home page, pricing page, API pages and the full published document set on 31 Aug 2026, and ran two targeted searches for a security or trust page, and located no encryption standard, no access control model, no retention period, no named subprocessor, no incident or breach notification practice and no business continuity position. The privacy policy itself was recovered in fragments through the search index rather than read end to end, so a complete read is the rebuttal route for anything recorded here as absent.

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.

The allocation of loss is published, readable before signing, and unusually explicit about the risk this product creates. The terms of service define the subscription agreement as comprising the general terms and conditions, the privacy policy, the public records policy and an applicable transactional rate schedule, which ties the published price schedule into the contract. The limitation clause excludes indirect, incidental, special, punitive and consequential damages in contract, tort or strict liability; excludes any claim relating to the customer's inability or failure to perform research or other work, or to perform it properly or completely, even if assisted by UniCourt; and excludes any decision made or action taken in reliance on information made available through the platform. The general disclaimer adds an as-is provision disclaiming all warranties express or implied, including merchantability, fitness for a particular purpose and non-infringement. Two things could not be established from the text retrievable on 31 Aug 2026: the liability cap, and whether any indemnity runs to the customer.

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.

Integration is the product rather than a feature attached to it, and it is documented to implementer level. Delivery routes are named and distinct: REST APIs, bulk data downloads, webhooks, and data shares pushed into a customer's data warehouse or data lake, alongside pre-built integrations. Target systems are named specifically, covering matter management, CRM, document management systems, internal legal databases, docketing applications and experience management systems. Structured output is aligned to SALI standards, which is a named industry data standard and the only instance of one located in this pull. What an implementer gets is stated rather than implied: API documentation, sample code and a Python library, with billable calls itemised as Search, Case, Download Document, Order Document Confirm and Update Cases and all other APIs and webhooks included, so a buyer can size an integration before committing. A PACER-specific API additionally reports whether a case is already held and when it was last updated, so a customer can avoid paying twice.

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.

Nothing published on where the software runs or where customer data sits. Searched the home page, pricing page, enterprise API page, PACER API page and the full published document set on 31 Aug 2026, plus two targeted searches for a security or trust page. No hosting provider is named, no tenancy model is stated, no region or residency option is offered, and nothing distinguishes processing from storage. The gap is more consequential here than on a self-contained application, because the delivery model actively moves data into customer-controlled warehouses and lakes, so a buyer needs to know where UniCourt's side sits in order to reason about the whole pipeline, and no answer is published.

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 was located, and no security page exists. Searched the home page, pricing page, enterprise API page, PACER API page, general disclaimer, terms of service, public records policy, privacy policy and cancellation policy on 31 Aug 2026, and ran two targeted searches specifically for a UniCourt security, trust or compliance page. No certification is named, no auditor identified, no scope or coverage period given, no penetration testing referenced, no badge displayed and no trust centre or portal exists. The absence stands out against how much else this vendor publishes: full pricing, a five-document legal set and API documentation are all open, which makes security the one area where nothing is offered.

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.

Nothing published about the models behind the extraction. The vendor describes AI-powered data extraction, sophisticated data normalisation and an AI-driven analytics layer, and names DEEP as its AI extraction platform, but searched across the home page, pricing page, enterprise API page, PACER API page and the full document set on 31 Aug 2026 no model provider is identified, no model or version is named, no architecture is described, no processing location is given, no subprocessor list exists and nothing commits the vendor to notifying customers when any of it changes. For a platform whose output flows automatically into customer data warehouses, the inability to tell which model produced a field, or when that changed, is a live operational question rather than a documentation nicety.

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 most complete pricing disclosure located in either pull. Rates are published for every self-serve tier: Personal at 49 dollars a month, Professional at 149 and Premium at 299, with annual billing shown as two months free at an effective 40.83, 124.17 and 249.17. The unit of charge is defined and so are the limits attached to it, covering searches at 50, 200 and unlimited, users at 1, 3 and 7, case tracking at 3, 15 and 50, automated searches, and case export at 1,000, with enterprise custom above that. API billing is itemised rather than gestured at, with billable calls named as Search, Case, Download Document, Order Document Confirm and Update Cases and all other APIs and webhooks stated to be included. Pass-through costs are addressed head on: court fees apply where a court charges and not where it does not, and no fee applies to material already in the CrowdSourced Library. Contract length, cancellation, plan switching, upgrade and downgrade timing and accepted payment methods are all answered, and the absence of a free trial is stated with the reason rather than left blank.

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.

Segments are documented by role and use case, and coverage is quantified with two real limits stated. Law firms are addressed through four named applications, covering docket research, litigation strategy, docket tracking and experience management, and insurance through litigation risk and strategy and master data management, with the buying question named in each case. Coverage is stated as more than 3,000 state and federal courts across over 40 states with more than a billion dockets and documents, all federal courts including district, bankruptcy and appellate, and a dedicated court coverage page is published for detail. Two boundaries are stated plainly: 40-plus states is not 50, and sealed or restricted documents not publicly available online are explicitly excluded. What is missing is depth within the covered states, since nothing published indicates which state systems are complete and which are partial, and the coverage page itself was not opened on 31 Aug 2026.