Work on your code. Diffs, routes and tests.
Unlimited Qwen3.8 27B: in your agent, app or chat.
+ const { amount, reason } = req.body;
+ const [order] = await query(
+ `SELECT id, total, refunded FROM orders WHERE id = ${req.params.orderId}`
+ );
+ if (!order) return res.sendStatus(404);
refunds.diffReview this diff before merging. List the bugs and security issues by severity.
Qwen3.8 27B
1. SQL Injection via req.params.orderId […] The URL parameter is interpolated directly into the SQL string. […] A negative amount passes the amount > order.total - order.refunded check […] then decreases refunded, effectively creating a "negative refund" / credit. […] Items 1–4 should block the merge […]
Three tasks in every sprint
Fix tests with an agent
Fix slugify.ts so the tests pass. Return the fixed file and explain the cause in one line.
vitest-output.txtslugify.tsslugify.test.tsFAIL slugify.test.ts > slugify > strips accents without dropping letters AssertionError: expected 'crme-brle-recipe' to be 'creme-brulee-recipe' FAIL slugify.test.ts > slugify > leaves no repeated hyphens AssertionError: expected 'prices----2026' to be 'prices-2026'
.normalize("NFD") .replace(/[\u0300-\u036f]/g, "") […] .replace(/-{2,}/g, "-"); […] Cause: The old code deleted accented letters outright (no NFD decomposition) and never collapsed the resulting runs of hyphens (e.g. " -- " → "----").
Find unauthenticated routes
Which routes in this API work without a valid session? Cite the file and say which one is the riskiest.
orders-api/app.use("/health", health); app.use("/export", csvExport); app.use(requireSession); app.use("/orders", orders); app.use("/customers", customers); app.use("/invoices", requireRole("finance"), invoices);
Three routes are reachable unauthenticated: […] GET /health […] GET /export/invoices.csv […] GET /orders/status/:id […] The riskiest one: GET /export/invoices.csv […] Anyone who can reach the server can pull every invoice number, customer ID, monetary total, and date in the system in a single unauthenticated request.
Classify tickets as JSON
Classify each ticket as "billing", "technical" or "account". Return only JSON: [{"id": 0, "category": ""}].
tickets.csvid,text 4812,"You charged me twice for the November fee, statement attached." 4813,"The app goes blank when I open the cart on my phone." 4814,"I want to change my login email, I no longer use the old one." 4815,"Can you issue the invoice in the company's name instead of mine?"
[{"id": 4812, "category": "billing"},{"id": 4813, "category": "technical"},{"id": 4814, "category": "account"},{"id": 4815, "category": "billing"},{"id": 4816, "category": "technical"},{"id": 4817, "category": "account"}]
Where your code goes
-
GPUs in the EU
The model runs in the EU. We never train on your code.
-
No content logs
On the API, prompts, responses and tool calls pass through memory, never to disk.
-
Isolated cache per account
The prefix cache lives only in GPU memory. No two accounts ever share it.
The model: Qwen3.8 27B
- 90.3
- Competitive programming
- 79.0
- Software engineering
- 73.0
- Terminal work
Qwen data: LiveCodeBench v6, QwenSWEBench, Terminal Bench 2.1.
- Base URL
https://api.voracompute.com/v1- Model
qwen3.8-27b
Individual plan
Fair use: 2 requests at once. Add your company's tax ID at checkout.
Common questions
Which agents and SDKs does it work with?
Anything OpenAI-compatible (Chat Completions): the Python or Node SDKs, OpenCode, Cline, Continue or Aider.
Can it make mistakes reviewing code?
Yes: it can misquote a line or miss a security flaw. Always run your tests and check the diff before merging.
Is the 1,000,000-token context real?
Yes: 262,144 native, extended with YaRN, and up to 32,768 output tokens per request. Go over and the API returns an explicit error: it never truncates your code silently.
What happens to the price on 1 December 2026?
Subscribe by then for 12 months at €19/month or €192/year. After that, the rate is €29/month or €288/year, excluding VAT, and you can cancel any time.