A support-ticket extraction exercise for DeepSeek V4.1 Flash
DeepSeek V4.1 Flash is now available on RouterBase. Here is a small exercise for evaluating it in a support workflow. This is a proposed test, not a report of measured model results.
Use a fictional ticket
Start with this input:
My CSV export failed twice today. I am using the web app. I have not tried another browser, and I do not know the error code.
Ask the model:
Extract a short summary, the reported failure, known environment details, and missing information. Return JSON with the keys summary, failure, environment, and missing_information. Use null for unknown facts. Do not diagnose a cause that the ticket does not establish.
The input is fictional and contains no customer information. Keep the prompt identical while comparing candidate models.
Check the answer in two stages
First, parse the output as JSON and check the required keys. Second, check meaning: the result should preserve the two failed attempts, mention the web app, and treat the browser and error code as unknown. Valid JSON alone is not evidence of factual accuracy.
Include another ticket with a known error code and a third with contradictory details. Record which cases pass, token usage, latency, and any retries. An application should have a fallback when parsing or factual checks fail.
Configure RouterBase
Base URL: https://routerbase.com/v1
Model: deepseek/deepseek-v4.1-flash
Keep your RouterBase API key on the server. The listed rates are $0.30 per million input tokens and $1.20 per million output tokens.
Sources: RouterBase API documentation and the public model catalog. Pricing checked September 14, 2026.
评论
发表评论