AI Agent StoreNace.AI · Native API contract verified
Drex v1.5 · native API
Send a document to Nace’s online Drex service and ask it to choose an answer, route a ticket or score a condition. It returns the requested decision instead of a paragraph.
Released 2026-09-28 · First reviewed 2026-10-11 · Checked 2026-10-15.
We still need comparable independent tests. You can compare the confirmed features and limits below, but we cannot yet give this version an Agent Fit or Practical Value rating. Test it on records with known answers, including cases that should go to a person.
What you can use today
Token prices measure the small pieces of text the model reads or produces. Capacity is the amount the service accepts in a request; check the limits below for any fallback to another model. A dash means the rate is unverified.
Exact provider API ID: drex-v1.5. Send model drex-v1.5 to POST /v1/systemone at console.nace.ai. The provider documents text state and yes/no, choice and rating questions. It returns probabilities; validate calibration on your own records.
Send drex-v1.5 to keep this version. On October 12, the default and drex-latest moved to v2.0. Retired drex-v1.1 still falls back to v1.5. Current v2.0 refuses requests above its own limits instead of handing them to v1.5.
State alone can contain 131,072 tokens; state plus the longest question can contain 139,264. Other questions do not add to that row limit. A request allows up to 512 questions and 4,194,304 serialized UTF-8 bytes for state plus questions. Check all boundaries.
Output: Yes/no probabilities, multiple-choice probabilities and ordered rating scores. No generated explanation. Compare decision models, limits and input costs ↗
Nace charges $0.05 per million input tokens for v1.5, with no separate charge for answers, requests or questions. Only successful requests (HTTP 200) are billed. Use the input-token count in your response to estimate usage. OpenRouter advertises $0.04, but this model was missing from both catalogs we checked, so we could not confirm access or billing for that offer. Use actual billed usage and the model named in each response to check your estimate.
Provider release and specifications ↗
Check availability and plans ↗
More setup and licensing details ↗
Test it before switching
Give each model the same examples, tools and definition of success. Record correct outcomes, response time, retries and total cost. Check whether confidence scores match the answers you can verify.
Compare caching and long-context costs ↗