---
title: "Use cases"
description: "Nace use cases: Drex for browser use and Drex for Search for developers, Nace for enterprise finance teams and for audit and accounting firms. Small models that make decisions, with the numbers behind each one."
canonical: "https://nace.ai/use-cases"
updated: 2026-10-22
---

# Use cases

> Nace use cases: Drex for browser use and Drex for Search for developers, Nace for enterprise finance teams and for audit and accounting firms. Small models that make decisions, with the numbers behind each one.

## Put a small model to work. Pick the job.

Drex is a small model that makes decisions: which element to click, which page answers the question, whether an entry is ready to post. Each use case below shows the job, the numbers behind it and how to start.

## Developers

Drop Drex into the agent you already run.

### [Drex for browser use](https://nace.ai/drex/browser-use)

Every click is one decision.

- 74.5 Decision Index Vision, vs 63.9
- 174 ms per screenshot, vs 253 ms
- 0.780 OSWorld-Verified, vs 0.734

### [Drex for Search](https://nace.ai/drex/search)

Supercharge your agentic search.

- #1 on MADQA, 94.7% accuracy
- 16.6× fewer search calls, BrowseComp-Plus
- −57% input tokens for coding agents

## Business

Models trained on your own work, running inside your perimeter.

### [Nace for enterprise](https://nace.ai/business/enterprise)

Finance that runs on decisions, not headcount.

- 1 week from one ledger to receivables and payables live
- 4 deployment boundaries, on-premises to cloud

### [Nace for professional firms](https://nace.ai/business/professional-firms)

Decide the whole population, not a sample.

- 1 day from one engagement to the first triage loop
- SOC 2 Type II audited, inside the firm's tenant

## 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 Intelligence](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
- [Use cases](https://nace.ai/use-cases.md): every Drex use case with its proof figures: browser use and search for developers, enterprise finance teams and professional firms
- [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