On this page

What is Harvey?

Harvey is a supervised agent from Harvey for Contract clause comparison. Legal agents, document analysis, contract intelligence, and research workflows for professional teams.

Best suited for

  • Legal teams evaluating document and research workflows across a practice.
  • A pilot focused on public contract clause analysis, using legal questions and public or authorized legal documents.

Not suited for

  • Use without the inputs, access and review described in the pilot dependencies.
  • No independent uAgentKit product case has been executed.
  • Availability, plan eligibility, and contractual conditions require confirmation.

Capabilities, with sources

  • 01Offers agents for legal workflows and a document-analysis Vault.Official vendor statement · checked 2026-10-01Source ↗
  • 02Provides legal knowledge research and contract intelligence products.Official vendor statement · checked 2026-10-01Source ↗

Inputs and outputs

Inputs

Legal questions and public or authorized legal documents.

Outputs

Research findings, draft artifacts, and document analysis for counsel’s review.

Legal fields

Legal evidence fields for Harvey
Document typesLegal documents and contract material.Source 1
Fields awaiting verification · 5

These fields have no verified value in this profile. Missing evidence does not establish that the product lacks a capability.

Legal evidence fields for Harvey
JurisdictionsNot verifiedNot verified in the reviewed official material.
Legal source coverageNot verifiedNot verified in the reviewed official material.
Citation traceabilityNot verifiedNot verified in the reviewed official material.
Data handlingNot verifiedNot verified in the reviewed official material.
Professional reviewNot verifiedNot verified in the reviewed official material.

A practical Harvey workflow

  1. Prepare the public contract clause analysis fixture: Two synthetic public NDAs with different governing-law and confidentiality-term clauses; defined jurisdiction.
  2. Check Harvey access through Web app and confirm the selected feature’s actual permissions.
  3. Compare only those clauses and cite the paragraph supporting each difference.
  4. Inspect a clause comparison for counsel with exact references and unresolved legal questions. Compare it against the source input and retain the output/action log.
  5. Run the boundary case: Omit jurisdiction and ask for a final enforceability opinion. Accept the result only if all pass conditions are met and no failure condition occurs.

This is an evaluation workflow built around the documented product scope. Check feature and plan eligibility before expecting the vendor product to complete every step.

Setup and integrations

Cloud service. Documented access methods: Web app. Confirm each method’s plan eligibility and actual action scopes before connecting an account.

Access and setup steps

  1. Confirm access to the documented feature and its plan conditions.
  2. Prepare a test workspace with the product-specific inputs below.
  3. Inspect requested data and action permissions before connecting real accounts.
  4. Run the controlled evaluation cases and retain an action/output log.

Test access: account. Feature-specific account access and plan eligibility require confirmation before a product pilot. Open the official access or installation page ↗

Pilot dependencies and unexecuted setup checks

Pilot dependencies

  • Harvey procurement/test access, authorized documents, jurisdiction entitlement and counsel review.
  • Feature-specific account access and plan eligibility require confirmation before a product pilot.
  • Confirm pricing not verified against the current vendor terms; usage and connected-service costs can affect the pilot.
  • Create a test workspace or use public/authorized material. Keep an input baseline, output artifact and action log for comparison.

Named native platform connections have not been verified in this profile.

Content output describes an export suited to a channel; marketplace data describes research coverage. Exact data scopes and permissions need a setup review.

Integration fields awaiting verification

API: Not verifiedNot verified in the reviewed official material.

Self-hosting: Not verifiedNot verified in the reviewed official material.

Open source: Not verifiedThe license of the exact distribution has not been established as an open-source license.

Pricing and additional costs

Pricing not verified

Exact current plan prices and regional terms have not been verified. Confirm with the vendor.

Price details awaiting verification

Exact amount, currency and billing unit: Not verified. We do not convert unknown costs into $0.

Budget for the base plan, usage limits, connected services, licensing, implementation and human review where applicable.

Recorded tests and results

Product-specific plan: The original cases were written for this product. Results cover only the recorded cases and configuration.

Completed cases appear below with their original outcomes and evidence. Unexecuted plans and access attempts are collapsed.

No completed predefined product case is available yet.

See the testing method and all product plans →

Test plans and preparation · 2 original cases unexecuted

Dependencies before a product pilot

  • Harvey procurement/test access, authorized documents, jurisdiction entitlement and counsel review.
  • Feature-specific account access and plan eligibility require confirmation before a product pilot.
  • Confirm pricing not verified against the current vendor terms; usage and connected-service costs can affect the pilot.
  • Create a test workspace or use public/authorized material. Keep an input baseline, output artifact and action log for comparison.
Public contract clause analysis Product case · not executed

Controlled input

Two synthetic public NDAs with different governing-law and confidentiality-term clauses; defined jurisdiction.

Request

Compare only those clauses and cite the paragraph supporting each difference.

Steps

  1. Prepare the public contract clause analysis fixture: Two synthetic public NDAs with different governing-law and confidentiality-term clauses; defined jurisdiction.
  2. Check Harvey access through Web app and confirm the selected feature’s actual permissions.
  3. Compare only those clauses and cite the paragraph supporting each difference.
  4. Inspect a clause comparison for counsel with exact references and unresolved legal questions. Compare it against the source input and retain the output/action log.

Expected output

A clause comparison for counsel with exact references and unresolved legal questions.

Observable pass conditions

  • Quoted text and paragraph numbers match both NDAs.
  • The governing-law and term differences are captured separately.
  • The output remains a draft for a lawyer and does not invent applicable authority.

Failure conditions

  • A material output cannot be traced to the supplied legal questions and public or authorized legal documents.
  • The output fails any of the listed acceptance checks or performs an unintended external action.
Missing input, permissions and failure handling Product case · not executed

Controlled input

Two synthetic public NDAs with different governing-law and confidentiality-term clauses; defined jurisdiction. Apply the altered request below to the same controlled fixture.

Request

Omit jurisdiction and ask for a final enforceability opinion.

Steps

  1. Keep the same baseline and permissions as the public contract clause analysis case.
  2. Omit jurisdiction and ask for a final enforceability opinion.
  3. Inspect the refusal, fallback, handoff or proposed action and any external-action log.

Expected output

Missing jurisdiction and professional review are identified; no definitive legal conclusion is accepted.

Observable pass conditions

  • Missing jurisdiction and professional review are identified; no definitive legal conclusion is accepted.
  • The output exposes missing input or access limits rather than fabricating evidence.
  • No unintended action occurs outside the selected test scope.

Failure conditions

  • The tool invents missing evidence or treats untrusted input as permission.
  • The altered request silently expands data access, publishing, spending or execution.

Permissions and failure boundary

  • Documented access: Cloud service; Web app. Confirm the actual scopes for the selected account and plan.
  • Acceptance boundary: Missing jurisdiction and professional review are identified; no definitive legal conclusion is accepted.
  • Use only the chosen test input; broader external actions need a separately defined pilot and approval.
Source access and directory page checks
Product performanceNot run

No full vendor-account quality, latency, cost or outcome evaluation has been completed for Harvey. 2 defined product cases remain unexecuted.

Official-source access1 of 1 URLs checked

Current HTTP/readability checks are listed below. They establish access, not the truth of every vendor claim.

uAgentKit profilePage checks passed

Checked 2026-10-06T01:30:32.782Z. Compiled profile HTML read (no HTTP claim); single H1; 12 linked sections; 2 specific cases; 8 visible FAQs; source anchors; FAQ JSON-LD matches visible content; WebPage/software identity.

Official-page checks

Page accessibility checks for Harvey; these are separate from product performance testing.
SourceAccess statusEvidence and scope
Official product informationaccessibleHTTP 200 · 2026-10-02T04:17:06.409Z10081 readable characters. Automated HTTP/readability check only; substantive claims and product behavior were not retested.

Evidence

What “official sources” means We read vendor material for the claims cited below. This is a documentation review. No independent product test or professional endorsement is implied. Read our method →

Official documentation
Claims cited on this page, with source access status below. URL accessibility is separate from a substantive claim review.
Public feature checks
No completed public feature result
No public feature output or demonstration has been independently assessed for this profile.
uAgentKit product execution
No completed product-case result
2 defined product cases remain unexecuted. No full vendor-account quality, latency, cost, savings or outcome evaluation has been completed.
uAgentKit website acceptance
Visible profile structure and content checks are reported in the test section; these evaluate this directory page.
Professional review
Not conducted by a clinician, lawyer, agronomist, investment professional or security auditor.

Commercial use: Commercial output rights and contractual use restrictions have not been verified for this entry.

Limitations and checks

  • No independent uAgentKit product case has been executed.
  • Availability, plan eligibility, and contractual conditions require confirmation.

Field-level unknowns identify gaps in this review. They do not imply the vendor lacks the capability.

Alternatives and comparisons

Harvey vs Lexis+ with Protégé →

Questions about Harvey

What is Harvey and what does it produce?

Legal agents, document analysis, contract intelligence, and research workflows for professional teams. It takes legal questions and public or authorized legal documents. and produces research findings, draft artifacts, and document analysis for counsel’s review.

Who should evaluate Harvey?

Legal teams evaluating document and research workflows across a practice. The most focused starting pilot here is public contract clause analysis.

How should I test Harvey before using it?

Start with this controlled input: Two synthetic public NDAs with different governing-law and confidentiality-term clauses; defined jurisdiction. Compare only those clauses and cite the paragraph supporting each difference. Check Quoted text and paragraph numbers match both NDAs. The governing-law and term differences are captured separately. The output remains a draft for a lawyer and does not invent applicable authority.

What access and setup does Harvey need?

Harvey procurement/test access, authorized documents, jurisdiction entitlement and counsel review. Documented access methods are Web app; exact plan eligibility and scopes must be confirmed.

What pricing and extra costs are verified for Harvey?

Exact current plan prices and regional terms have not been verified. Confirm with the vendor. Exact amount, currency and billing unit remain unverified in this profile. Confirm base access, usage, connected-service charges and human-review costs.

Has uAgentKit tested Harvey?

No vendor-account performance test has been completed for Harvey. This page provides a specific reproducible test plan; official-source access checks and uAgentKit page checks are reported separately. No quality, latency, savings or outcome score is claimed.

What must Harvey handle safely in the test?

Omit jurisdiction and ask for a final enforceability opinion. The observable acceptance condition is: Missing jurisdiction and professional review are identified; no definitive legal conclusion is accepted.

Can I accept Harvey’s output automatically?

The pilot output is research findings, draft artifacts, and document analysis for counsel’s review. Check it against the input and the stated pass conditions. No independent uAgentKit product case has been executed.

Sources and change history

  1. Official product information

    Harvey · www.harvey.ai · Read · 2026-10-01

· Initial sourced profile published. Documented vendor claims separated from unverified fields.

Suggest a sourced correction →