The same model, the same question: alone with manually pasted documents – or with c:node, which passes on only the evidenced citations. All prices, assumptions and sources disclosed.
Every figure can be recalculated.
Every price links to the provider's page.
Opus 5.5, Sonnet 5.5, Haiku 4.5 · list prices per 1M tokens, incl. cache prices
anthropic.comGPT-6 Sol and GPT-6 Luna · list prices per 1M tokens
developers.openai.comGemini 3.1 Pro and 3.8 Flash · up to 200,000 tokens of context
ai.google.devMistral Large 3 and Small 4 · calculated without cache discount
mistral.aiUS$0.658 per hour, on-demand, eu-central-1 · our own invoice 09/2026
aws.amazon.comEstimated throughput on T4: 1,500 tokens/s input, 35 tokens/s output, 4 parallel requests
huggingface.co€1 = US$1.1378 on 28 Sep 2026
ecb.europa.euOur own estimate from the example cases, e.g. 23 contracts of around 7,000 tokens each plus excerpts from the Data Act and GDPR
Our own assumptionList prices retrieved on 29 Sep 2026. All amounts net, converted to euros.
We set up the model with your case numbers and volumes.
Because the model doesn't have to read entire folders. c:node finds the relevant passages beforehand and passes on only those. That saves input tokens – and follow-up rounds.
Calculated – with list prices and disclosed assumptions. The throughput of open models on your own GPU is estimated, not measured.
That is not included. Without c:node, someone has to find and paste in the documents – with c:node, the connectors do that. So in practice the savings are larger.
In our calculation, Mistral grants no cache discount. Alone, the full context is paid in full every round – with c:node, only the evidence, once.