Support
Route tickets to the right queue
Map a request to the team that can handle it.
Invoice address change → billing | technical | account
EU tier · GDPR data handling · EU
A decision API for teams with personal or confidential data: route, classify and score. Jev-compatible, with a probability for every option.
Sign in with Google or a one-time email link. Top up from EUR 1; taxes are shown before you pay. Operated by a German company in Passau: imprint.
state: Mia owns a red bicycle.
question: Which color is the bicycle?
state: a business customer asks to update an invoice address.
question: Which support queue fits?
state: a viewer deletes a workspace.
question: Is this action allowed?
EU tier
EU requests always stay in the EU and have priority. Details
More throughput per GPU
s1-pro-3 (vLLM-SR d3, 12 Oct 2026): ~2.6x the throughput of its reference server. Details
Jev-compatible API
s1-fast from half of Jev’s price. Details
Measured by us on 11–12 Oct 2026; method and raw data on /evidence.
1 mammoth-1 (s1-pro in the EU tier) scores 10.2 points above Jev 1.14.0 on the same items. JevBench v1.8.7 (4 Nov 2026) capability score = mean of Intelligence and Calibration; each pair was measured on the same items. JevBench measures the open models, not our API. JevBench is run by Benchmark Heaven, also by the founder of Decision Models; method and raw results are public. Evidence
ISO/IEC 27001: Hetzner for the API gateway, database and backups (certificate covers the Helsinki data centre). GPU providers: see Security.
EU tier
Same models, same API. One header or an EU key is all it takes.
EU requests run only on contracted operators inside the EU; inference data never leaves the EU.
EU requests take priority over Peer-to-Peer traffic, even when a key allows worldwide processing.
The EU tier runs only on GPU servers we operate in EU data centres, never on the peer-to-peer network or on worldwide capacity. Locations
DPA under Art. 28 GDPR accepted at signup; a public sub-processor list with purpose and location.
Quickstart
Jev-compatible request shape: moving from Jev means changing the base URL and credentials, then reviewing the documented differences.
Sign in with a one-time email link or with Google and create an API key in the dashboard. Free allowance by invitation; top up from EUR 1.
A named state and up to three questions for s1-pro, one for s1-fast or s1-vision: choice, score or noul (a yes/no question answered with a probability).
Read the chosen answer with probabilities, a usage receipt and the effective tier. With S1-Region: eu the request stays in the EU.
# Key from your dashboard
export DECISIONMODELS_API_KEY="paste-your-key-here"
# Ask one question on the EU tier (S1-Region: eu)
curl https://api.decisionmodels.io/v1/systemone \
-H "Authorization: Bearer $DECISIONMODELS_API_KEY" \
-H "Content-Type: application/json" \
-H "S1-Region: eu" \
-d '{
"model": "s1-fast",
"state": "Mia owns a red bicycle.",
"questions": {
"color": {
"type": "choice",
"instructions": "Which color is the bicycle?",
"criteria": {"red": null, "blue": null}
}
}
}'Practical decisions
Send context and a named question; use the typed answer in your workflow.
Support
Map a request to the team that can handle it.
Invoice address change → billing | technical | account
Product / Safety
Check a proposed action. Keep deterministic access controls in your application.
Viewer deletes workspace → allowed?
Quality
Grade replies or summaries and escalate uncertain cases.
Draft + rubric → score
Ops / Docs
Classify document text before handing it off.
Document → invoice | contract | other
Illustrative workflows. Validate representative cases on your own data before automating decisions.
Data flow
Every EU request stays in the EU from the first byte to the last.
Answer returns over the same encrypted path
Contracts
Data Processing Agreement under Art. 28 GDPR, accepted at signup.
Read the DPA →Every provider with purpose and location.
See the list →Which account data we process and why.
Read privacy policy →German company, reachable contacts.
Open imprint →Encryption, access and operations at a glance.
Read security overview →EU pricing
Per 1 million input tokens. Output tokens are free. Free allowance by invitation. Top up from EUR 1.
| Model | USD | EUR |
|---|---|---|
s1-fastbased on Blink v0.3 26B-A4B · text | $0.021 | €0.018 |
s1-promammoth-1 27B (MIT, EU tier) · text | $0.084 Existing customers until 12 November 2026: $0.040 | €0.074 Existing customers until 12 November 2026: €0.035 |
s1-visionBlink v0.3 26B-A4B · text without an image | $0.032 | €0.028 |
reax-1REAX 1 by Decision Models · text | $0.084 | €0.074 |
Excluding applicable taxes. Private individuals and businesses worldwide can sign up and top up. Taxes are shown in checkout before you pay. All prices and calculator →
Two approaches
EU-tier requests always stay in the EU and have priority. Allowing worldwide Peer-to-Peer processing for a key does not change that.
Peer-to-Peer starts on spare EU capacity. When it is busy, Peer-to-Peer can draw on rented worldwide GPU capacity from independent hardware providers in various countries, including outside the EU/EEA. This happens only for keys with “Allow worldwide processing” enabled. Without either opt-in (worldwide processing or network processing), Peer-to-Peer stays in the EU and may be queued or rejected when busy. Existing customers keep EU-only processing unless they opt in for the individual key. Our gateway does not log payloads; on keys with the separate network-processing opt-in, independent providers of the peer-to-peer network may store content. Requests to models served by the network (currently: s1-fast-1) go to REAX miners with a track record as the primary route, with our GPUs as fallback; answers are checked on a sampled basis. All other models in this tier run on our GPUs (EU, and with worldwide processing enabled also non-EU partner GPUs). If the network has no capacity for an exact network version, the request is answered on our own GPUs with the same exact model version, never with another model. A retryable 503 is returned only if neither the network nor our own GPUs have capacity. This applies to keys with network processing turned on, which is preselected when you create a Peer-to-Peer key in the dashboard ("Our GPUs only" is selectable) and separate from worldwide processing; existing keys are not changed. The EU tier never uses the network.
EU AI Act
Decision Models serves open-weight models for narrow decision tasks, including our own fine-tunes. We publish model cards and benchmark results, label our models clearly, and document intended use. Using the API for high-risk purposes under the AI Act requires your own assessment.
reax-1.3 · REAX 1.3 by Decision Models · text · EU only
REAX is an open inference network on Bittensor subnet 92; JevBench is a sister project. Its open training competition improves the decision models served by the network. REAX 1.3 has two parts that run in parallel on one GPU; each part builds on a fine-tune trained by a REAX miner (uid 18 and uid 83). Jev-compatible interface, with a probability for every option. Text only, 1 question per request, up to 28,672 billed input tokens including the state; longer inputs are refused, not truncated. Hosted in the EU tier only. €0.400 per 1M input tokens, output free.
Open weights on Hugging Face (Apache-2.0) · REAX Engine (MIT) · Model page →
mammoth-1 27B by baselabs · MIT · FP8 · text · EU tier
Since 5 November 2026, mammoth-1 (revision 61cec44c) answers s1-pro in the EU tier. Up to three text questions per call, 8,192 input tokens per question. In the EU tier, s1-pro is answered by mammoth-1 (s1-pro-5), or by s1-pro-3 (vLLM-SR d3) if mammoth-1 cannot answer. In the Peer-to-Peer tier, it is answered by s1-pro-3, with or without network processing enabled. The pinned id s1-pro-5 is EU tier only. model_version shows which version answered. mammoth-1 is post-trained from Qwen3.5-27B by the Qwen team (Apache-2.0). Not affiliated with or endorsed by baselabs, Baseten or the Qwen team.
vLLM-SR d3 · 26B · FP8 · Apache-2.0
The pinned id for vLLM-SR d3 26B (Apache-2.0), served in FP8. It has answered s1-pro since 12 October 2026; since 5 November 2026 it is the Peer-to-Peer model and the EU fallback. Up to three questions per call, 16,384 input tokens per question. Available through at least 27 January 2027. The authors do not disclose its training data.
mammoth-1 27B · MIT · FP8 · pinned id · EU tier only
The pinned id for mammoth-1 (revision 61cec44c), EU tier only. Served in FP8 by Decision Models, up to three questions per call, 8,192 input tokens per question. Billed at the s1-pro EU list rate: $0.084 per 1M input tokens, output tokens free. mammoth-1 is an open model under MIT, post-trained from Qwen3.5-27B by the Qwen team (Apache-2.0). Not affiliated with or endorsed by baselabs, Baseten or the Qwen team.
Perplexity Decider v1.1 27B · NVFP4 · previous s1-pro, pinned id, retires 1 December 2026
The pinned id for the model that answered s1-pro until 12 October 2026: calibrated text decisions on our engine, at about 4.4x the throughput of the author's reference code (not Perplexity's hosted service) on the same GPU model (measured by us on 11 October 2026; method on /evidence). Available in both tiers, billed at the s1-pro list rate: $0.080 Peer-to-Peer / $0.084 EU per 1M input tokens, output tokens free. Perplexity Decider v1.1 is an open model under Apache-2.0, derived from Qwen3.8-27B by Alibaba Cloud (Apache-2.0). Retires on 1 December 2026; successor: s1-pro.
Based on Blink v0.3 26B-A4B · NVFP4 · text
Short text decisions at low latency: one question with up to 16 options. Runs on a batched engine, so probabilities for identical requests can differ slightly.
Based on Blink v0.3 26B-A4B · NVFP4 · one image
One question with one image attached, up to 26 options.
REAX 1 by Decision Models · 27B · text
Our own open decision model: REAX 1 by Decision Models, a fine-tune of Perplexity Decider v1.2 by Perplexity (Apache-2.0), derived from Qwen3.8-27B by the Qwen team (Apache-2.0). Not affiliated with or endorsed by Perplexity AI or the Qwen team. Up to three questions per call, billed at the s1-pro list rate. reax-1 always points to the current REAX 1 release. We may replace the model behind this id with a newer REAX version at any time, with the same API and price; we switch only to a version that measures at least as well on our evaluations. For reproducibility, pin a dated id such as reax-1-20261021; pinned ids stay available for at least 30 days after they stop being current.
5 November 2026: s1-pro now runs mammoth-1 (s1-pro-5) in the EU tier. In the EU tier, s1-pro is answered by mammoth-1 (s1-pro-5), or by s1-pro-3 (vLLM-SR d3) if mammoth-1 cannot answer. In the Peer-to-Peer tier, it is answered by s1-pro-3, with or without network processing enabled. The pinned id s1-pro-5 is EU tier only. model_version shows which version answered. Prices unchanged.
Every response names the model version that answered in model_version and in the S1-Model-Version header. The retired ids s1-pro-1, s1-fast-1 and s1-vision-1 are answered by the current models. In the EU tier, s1-pro is answered by mammoth-1 (s1-pro-5), or by s1-pro-3 (vLLM-SR d3) if mammoth-1 cannot answer. In the Peer-to-Peer tier, it is answered by s1-pro-3, with or without network processing enabled. The pinned id s1-pro-5 is EU tier only. model_version shows which version answered. Perplexity Decider v1.1 stays pinned as s1-pro-2 through 30 November 2026. s1-pro-2 and s1-pro-4 retire on 1 December 2026; s1-pro-3 stays available through at least 27 January 2027. On keys with peer-to-peer network processing enabled, s1-fast-1 may instead be answered by its original model (listed in the model licences). Each question, including its state, is limited to 8,192 to 28,672 input tokens, depending on the model. Full model list: /models · Licence.
Current prices are on /pricing. Dated Decision Index results and our own speed measurements for s1-pro-3, s1-pro-2, s1-fast and s1-vision are on /evidence; reference-model results from published benchmarks and their methods are on /benchmarks.
Where it fits
Use a decision model for narrow tasks where it meets your accuracy needs. Keep an LLM for difficult reasoning and open-ended writing.
TYPICAL TASKS
Route a ticket, approve an action or score a draft: one answer per option, with probabilities.
WHEN AN LLM IS BETTER
Use a frontier LLM for open-ended writing or difficult reasoning. Validate representative cases on your own data first.
Press context
“…LLMs as we know them aren't the right solution for a lot of software because they are comparatively slow and expensive.”
Common questions
No. EU-tier requests run on contracted operators in the EU. Our gateway does not log prompts or answers, and we do not use them for training; see Data retention for the limits. Read the DPA and the sub-processor list.
Worldwide Peer-to-Peer processing must be explicitly enabled per key. EU-tier requests always remain in the EU.
No blanket compliance promise applies to your application. You remain responsible for your application, the data you send and its lawful use.
It depends on the task. Validate representative cases on your own data and keep a frontier LLM or human review for difficult or open-ended tasks.