---
title: "Legal"
description: "Document Processing extracts terms from contracts and filings, cited to the clause. Drex for Search finds the passage across the portfolio, and Drex scores what it permits, for a lawyer to confirm."
canonical: "https://nace.ai/industries/legal"
updated: 2026-11-06
---

# Legal

> Document Processing extracts terms from contracts and filings, cited to the clause. Drex for Search finds the passage across the portfolio, and Drex scores what it permits, for a lawyer to confirm.

## What the contract says, and where it says it.

Document Processing extracts terms from contracts and filings, cited to the clause. Drex for Search finds the passage across the portfolio, and Drex scores what it permits, for a lawyer to confirm.

Runs on: Document Processing (reads), Drex (decides), Drex for Search (finds).

| Value | Result | Source |
| --- | --- | --- |
| 75.9 | on ContractNLI, what a contract does and does not say. Jev 1.14: 57.7 | [Drex benchmarks](https://nace.ai/drex) |
| #1 | on grounding in Nace's Perception evaluation | [Perception evaluation](https://nace.ai/perception) |
| <200 ms | model latency per decision, not end-to-end workflow time | [Drex benchmarks](https://nace.ai/drex) |

## Associates spend their hours locating clauses, not weighing them.

Diligence, playbook review and discovery all start with finding the right passage. Nace finds it, extracts it, scores the first call and cites the clause, so lawyers spend their hours on judgment.

## Where Nace fits

Each workflow names the model that does the work.

| Workflow | What it does | Model |
| --- | --- | --- |
| Contract abstraction | Parties, dates, renewal, termination and liability terms, each cited to its clause. | Document Processing |
| Clause questions | The clause found, then a probability on whether it permits, say, assignment. | Drex + Drex for Search |
| Playbook review | Each clause rated against your playbook: standard, acceptable or escalate. | Document Processing + Drex |
| Privilege and responsiveness | A responsiveness and privilege score for each document, for reviewers to confirm. | Drex |
| Discovery processing | Large productions of scans, emails and attachments split and classified. | Document Processing |
| Matter intake routing | Each new request sent to the right practice group and priority. | Drex |

## Playbook review, end to end

1. Contract set in: Agreements and amendments
2. Document Processing reads: Every clause, located
3. Drex decides: Standard, acceptable or escalate
4. Your lawyers: Review only the escalations
5. Drex for Search finds: Any clause across the portfolio

What it reads: Contracts and amendments, NDAs, Leases, Data room files, Court filings, Discovery productions, Emails and attachments.

## Runs where your data already lives.

Same models and the same API at every tier. Only the boundary around your data changes.

- Managed Cloud: Our GPUs, our API, a key from Console.
- Dedicated Cloud: Your own cluster in our cloud, reached over private links.
- Your Cloud: Installs in your AWS or Azure account. Data stays inside.
- On-Prem & Air-Gapped: Your datacenter, your hardware, zero outbound.

SOC 2 Type II audited. [Visit the Trust Center](https://trust.nace.ai).

## See it on your own files.

Send us a file and the decision you make on it. We'll show you the result on your own documents.

- [Get started](https://console.nace.ai/?utm_campaign=industries&utm_content=industry-legal_md&utm_medium=website&utm_source=nace.ai)
- [Talk to sales](https://nace.ai/contact?source=industry-legal)

Related industries: [Professional services](https://nace.ai/industries/professional-services) · [Insurance](https://nace.ai/industries/insurance) · [Government](https://nace.ai/industries/government)

## For agents

- [Drex API guide](https://nace.ai/drex.md): the decision model: request shape, question types, benchmarks and deployment, as markdown
- [Decision endpoint](https://console.nace.ai/v1/systemone): POST with model "drex-latest", a state string and typed questions (choice, noul, score); https://console.nace.ai/v1/models lists checkpoints
- [Document endpoints](https://console.nace.ai/v1/documents/{parse|split|classify|extract|ground}): POST a source (a public URL, an uploaded workspace file or a finished parse job) and poll GET https://console.nace.ai/v1/documents/jobs/{id}; the same key and credit as decisions
- [Console](https://console.nace.ai): API keys, the playground, usage and billing; send `Authorization: Bearer $NACE_API_KEY` on every request
- [Console docs](https://console.nace.ai/docs): quickstart, question types, the document routes, errors, limits and pricing
- [Nace Document Processing](https://nace.ai/perception.md): the Perception series: parse, split, classify, extract and ground any file type with a location on every value
- [Drex for Search](https://nace.ai/drex/search.md): Drex for Search: decision-powered retrieval for agents, Drex finds the page, cited search through the CLI, SDKs, MCP and REST, and the public benchmark ranks
- [Industries](https://nace.ai/industries.md): Nace by industry: the files Document Processing reads and the decisions Drex makes for accounting, banking, mortgage, insurance, legal, healthcare, government, construction, logistics and professional services
- [Developers](https://nace.ai/developers.md): The execution layer for agents: Perception, Decision and Search behind one key, the Drex Max frontier, install steps, a scripted agent session and the four deployment boundaries
- [Site index](https://nace.ai/llms.txt): every page on nace.ai; append `.md` to any page URL or send `Accept: text/markdown` for the markdown version