Sign-up and API keys are open. Paid top-ups open soon.What changed

Pricing

Output is free. You pay for input tokens.

Dex never writes text, so nothing is billed on the way out. You pay per million input tokens: the state once, plus your questions. Prepaid in euros. No subscription, no minimum spend beyond a first top-up.

Sign-up and API keys are open, and test keys are free. Paid top-ups open soon.

Per million input tokens

EUR 0.05per million input tokens, at every volume

  • 015 micro-cents per billable token. Every charge is an exact whole number.
  • 02Output tokens are free. The fixed prompt text around your content is free.
  • 03The state is billed once, however many questions share it.
  • 04Prices exclude VAT.
What a call is billed forExample from the API contract
state 142questions 131answers: free273 input tokens, billed273 x 5 micro-cents = EUR 0.00001365

What calls cost

CallBillable tokensCharge
One check on a short message150EUR 0.0000075
The Dutch support example in the docs273EUR 0.00001365
A typical 450-token call450EUR 0.0000225
A 1,000-token state with 8 questions of 60 tokens1,480EUR 0.000074

One million calls of 450 tokens cost EUR 22.50.

Estimate a month

Billable tokens 450,000,000
Monthly cost, excl. VAT EUR 22.50

Cost and speed

Cost and speed per model.

Median time per workflow against cost per 1,000 workflows, both from our recorded runs. Lower and further left is better. The runs are on the home page.

Cost and speed per modelmean over 4 workflows, 2026-09-25
0.10.20.5125100.020.050.10.20.5125102050Median time per workflow (s, log scale)Cost per 1,000 workflows (EUR, log scale)Dex, GPU computeDex, round tripGPT-5.4 miniGPT-5.3 chatGPT-4.1GPT-4.1 miniClaude Haiku 4.5Claude Sonnet 5Claude Opus 5.5Claude Fable 5.1Jev, TypeSafe's figure0.10.20.5125100.020.050.10.20.5125102050Median time per workflow (s, log scale)Cost per 1,000 workflows (EUR, log scale)1234567891011
Cost and speed per model, as a table
#ModelMedian time (s)Cost per 1,000 (EUR)Source
1Dex, GPU compute0.1030.0463our recorded runs, 4 workflows
2Dex, round trip0.1300.0463our recorded runs, 4 workflows
3GPT-5.4 mini0.8591.0327our recorded runs, 4 workflows
4GPT-5.3 chat1.1412.6086our recorded runs, 4 workflows
5GPT-4.11.2342.4764our recorded runs, 4 workflows
6GPT-4.1 mini1.4750.4960our recorded runs, 4 workflows
7Claude Haiku 4.51.5541.8837our recorded runs, 4 workflows
8Claude Sonnet 52.1144.8454our recorded runs, 4 workflows
9Claude Opus 5.52.6709.7278our recorded runs, 4 workflows
10Claude Fable 5.17.05229.3534our recorded runs, 4 workflows
11Jev, TypeSafe's published figure (different workload)0.4000.3435TypeSafe, workflow evals, read 25 Sept 2026

Each point is a contender's mean of its per-workflow medians. Dex is shown twice: round trip over the network, and GPU compute alone. Costs are tokens times list price; Dex at its list price, output free. USD converted at 0.858664 EUR per USD (Azure rate, read 2026-09-25).

How you pay

  • 01Prepaid balance in euros. Top up EUR 10 to EUR 2,500 at a time, with cards, iDEAL, Bancontact, SEPA Direct Debit.
  • 02New accounts can top up at most EUR 500 in their first 30 days.
  • 03Each call is charged when it is accepted, and refunded in full if it then fails on our side.
  • 04Balances do not expire. Unused balance is refunded on request when you close the account.
  • 05VAT: reverse charge for EU businesses with a valid VAT id. Dutch VAT for Dutch customers.

Free test keys

Test keys start with dex_test_. They run on the GPU path, are never billed, and share a free quota of 250,000 tokens per account per day.

Tokens and billing in the docs

Comparison

Dex, the EU alternative to Jev

Jev is a decision model from TypeSafe AI. Like Dex, it answers typed questions about text or JSON with probabilities. This comparison uses only TypeSafe's own public pages. Every row links to its source and says when we read it.

Dex, the EU alternative to Jev
TopicDexJev, as TypeSafe's pages state itSource
Where requests are processedDex differsIn the EU only. Azure West Europe in the Netherlands, Dex's own inference nodes on dedicated hardware operated by thinQit in the Netherlands, and Azure OpenAI in the EU data zone for the fallback path.TypeSafe's subprocessor list names Amazon Web Services, Modal, Nebius and CoreWeave for request processing, each with the location USA.TypeSafe Trust Center, Subprocessorsread 25 Sept 2026Subprocessors table, cloud and AI infrastructure rows
Request content kept by defaultDex differsNone, for every account. Content is stored only if the account owner turns on content logging.TypeSafe's legal page offers zero data retention (ZDR) to enterprise customers.One exception on the Dex side. On the fallback path, until Microsoft approves modified abuse monitoring, Azure OpenAI may keep prompts its classifiers flag for up to 30 days inside the EU data zone. Send fallback set to never to stay on our GPU.TypeSafe docs, Legalread 25 Sept 2026Data retention paragraph
Training on customer dataSame on bothNever. Customer content is not used to train, tune or calibrate any model.TypeSafe's models page says Jev is not trained on customer requests or responses.TypeSafe docs, Modelsread 25 Sept 2026Data paragraph
Same input, same answerNot comparable yetDesigned so that an identical request to the same GPU model version returns byte-identical answers. Fallback answers are excluded and labelled as such.Measured: Published at launchTypeSafe's consistency cookbook reports 90.8% raw label agreement over 15 repeated calls on one post with 8 questions, sampled on 11 Sep 2026, and says its threshold policy does not make the model deterministic.Not like for like. Ours is a design guarantee that we will verify in production; theirs is one measured experiment.TypeSafe docs, self-consistency cookbook for choicesread 25 Sept 2026Results table and the note under the threshold policy
Abstaining when unsureDex differsBuilt in. Set min_confidence on a question and an answer below it comes back with abstained set to true.TypeSafe's confidence page leaves thresholding on confidence to the caller's own code.TypeSafe docs, Confidenceread 25 Sept 2026Using confidence section
LanguagesDex differsEnglish and Dutch quality measured and published separately, as agreement with reference labels on our own test set.Measured: EN 84.9%, NL 79.6%TypeSafe's models page names English as the primary training language, where accuracy is best, and says other languages are handled but not equally well.TypeSafe docs, Modelsread 25 Sept 2026Languages paragraph
List price per million input tokensJev aheadEUR 0.05, flat at every volume.USD 0.042, on TypeSafe's models page.Different currencies. We do not convert. Both prices exclude VAT where it applies.TypeSafe docs, Modelsread 25 Sept 2026Pricing section
Output tokensSame on bothFree.Free, per TypeSafe's models page.TypeSafe docs, Modelsread 25 Sept 2026Pricing section
Largest requestJev ahead32,768 billable tokens per request, of which the state can use up to 16,384.TypeSafe's models page gives 64k tokens per request, of which 32k for the state plus the longest question.Each count uses its own tokenizer, so the numbers are close but not identical in text length.TypeSafe docs, Modelsread 25 Sept 2026Limits section
Published measurements todayJev aheadAgreement and calibration error of our current model version on our own English and Dutch test set, and recorded races of our prototype against general LLMs on the home page. Production latency and determinism measurements are not published yet.TypeSafe publishes accuracy, cost and latency on its workflow evals page, and a repeatability experiment in its docs.Our race numbers come from a prototype on Dex's own inference node. The cost and speed chart on the pricing page shows TypeSafe's published figure beside them, marked as a different workload; it is not a like-for-like comparison.TypeSafe, workflow evalsread 25 Sept 2026Whole page

Where Jev is ahead today

  • 01List price per million input tokens. USD 0.042, on TypeSafe's models page.
  • 02Largest request. TypeSafe's models page gives 64k tokens per request, of which 32k for the state plus the longest question.
  • 03Published measurements today. TypeSafe publishes accuracy, cost and latency on its workflow evals page, and a repeatability experiment in its docs.

How we made this comparison

Nobody working on Dex has used Jev or TypeSafe's service. We read TypeSafe's public pages and cite them with the date we read them, and we read them again before every change to this comparison.

Every row is a fact from a public page, with the page and the date we read it. Where we have not measured something yet, the Dex cell says so. Where the two are not comparable, the row says why.