Execute your workflows with Nace Small Models
One API key for Drex, which puts a probability on every call, and NDI, which reads 36 file types and cites the source of every answer.
Works with
Builders on Drex, in their words.
- VVishesh Baghel@VisheshBaghell · Sep 25$499,235 of unbilled work across 1000 work orders. @NaceAI's drex found $482,260. drex reads the note and the invoice and flags what's missing. code does the math. when drex isn't sure, a human decides.
- IIvan Fioravanti@ivanfioravanti · Sep 25Drex: faster, cheaper, better than jev, 32k context and with open weights coming soon? I will surely give it a try!
- SSuperSaiyanColtSep 26I’m using Drex as a fast decision layer inside my project Elyreon/NOVA mainly for routing tasks, choosing tools/models, classifying failures, retries, urgency, and handoffs. the bot already responds sub 1s so i cant imagine how much better drex will make it
- IIsrafil@Israfilv2 · Sep 30Nace shows Drex playing a strategy game. i gave it a harder opponent: my timeline Spoiler Guard sends each post to the new decision model and blurs the spoilers, 352 post checked in one session with sub-second calls
- EEduardo OrdaxSep 25Using a massive LLM to decide which tool to call feels like hiring a CEO to sort your inbox. Drex targets those decisions: routing, ranking, classification and guardrails.
- KKai@hqmank · Sep 25Switching was easy. I pointed my existing Jev setup at Drex, kept the same SDK, changed 3 environment variables, and it worked. I see a good fit for agent routing, tool selection, document classification, and choosing the next action in browser automation.
- DDean W. Perkins@deanwperkins · Oct 6someone wired a small open model to a real security camera 389 ms per call the vision model sees, drex decides
- GGipp@gippp69 · Sep 30128k context means it can route with real state instead of tiny summaries. the interesting part isn’t more generation. it’s better decisions before generation starts.
See it work from a terminal.
An agent with a Console key reads an AP packet, finds the page that matters and decides what to do with it. Every call in the window is a Console endpoint, and every value comes back with the page it was read from.
$ export NACE_API_KEY="nace_sk_…"
$ claude
> This AP packet from Halden Supply mixes invoices, a contract amendment and a W-9. Which invoice can we pay today, and did the terms change?
console · split(file: "halden-packet.pdf")
38 pages → 5 documents
1 Invoice INV-2291 p. 1–3
2 Invoice INV-2304 p. 4–6
3 Contract amendment No. 3 p. 7–19
4 W-9 p. 20
5 Purchase order PO-77120 p. 21–38
console · classify(document: 3, classes: "procurement")
contract_amendment · 0.97
console · extract(document: 3, schema: { payment_terms, effective_date, parties })
payment_terms "Net 45, 2% discount within 10 days" found
effective_date "2026-10-01" found
parties Halden Supply Co., Meridian Logistics found
console · ground(document: 3, text: "Net 45")
page 11 · box 0.12 0.41 0.88 0.47 · exact · 0.99
console · extract(documents: [1, 2], schema: { invoice_no, total, payment_terms, po_number })
INV-2291 $18,420.00 "Net 30" PO-77120 p. 2
INV-2304 $9,870.00 "Net 45" PO-77120 p. 5
console · systemone(state: "INV-2304 · $9,870.00 · Net 45 · matches PO-77120 · terms per amendment No. 3", questions: { approve: noul, route: choice })
approve noul 0.93
route payments 0.88 · review 0.09 · reject 0.03
Pay INV-2304 today: $9,870.00 against PO-77120 on Net 45, the terms Contract amendment No. 3 sets on page 11, effective 1 October 2026. Drex puts 93% on approving it and routes it to payments.
Hold INV-2291. It still carries Net 30 on page 2, which predates the amendment. Want me to flag it for AP review?
Everything your agent needs, behind one key.
Authorization: Bearer $NACE_API_KEY
One key, one credit and one error envelope for both series.
- Decision
- Perception
Works where your agent works.
Console is plain HTTPS and JSON. Any harness that can call a tool can call it; these are the ones we test with.
Three ways in.
One platform. Four boundaries.
Same models, same API, same serving stack at every tier. The only thing that changes is the boundary around your data, from our cloud to your metal.
Your data trains your models. The weights, adapters and eval sets stay yours, inside the boundary you pick.
- Managed Cloud- Start on our GPUs, behind our API, with a key from Console. - Shared GPU pool with strict tenant isolation
- Public API over TLS, no training on your data
- Usage-based pricing, no infrastructure to run
- For: pilots, evaluations, mid-market teams moving fast.
- Dedicated Cloud- Your own GPU cluster in our cloud, reached over private links instead of the public internet. - Single-tenant compute, pinned to your region
- PrivateLink or VPC peering into your network
- Customer-managed keys, dedicated throughput
- For: regulated teams that are cloud-first but done with shared infrastructure.
- Your Cloud- The platform installs inside your AWS or Azure account. Data stays within your boundary. - Runs in your VPC with your keys, your logs, your IAM
- Updates pull from our registry; nothing flows back out
- The deployment model our audit and banking customers run in production
- On-Prem & Air-Gapped- Your datacenter, your hardware, zero outbound. - No egress, no telemetry, offline license activation
- Signed offline update bundles on your schedule
- Ships as software on your servers or as a pre-configured appliance
Questions
First request today. Your own cloud when you need it.
Create a key in Console and send your first request in a minute. When the data cannot leave your network, we bring the platform inside it.