r/machinelearningnews • u/ai2_official • 14h ago
r/machinelearningnews • u/ai-lover • 19h ago
Research AI is changing how attacks happen, and how fast. More companies will face a security incident. The question is no longer if, but how they respond. [This post covers some insights....]
Attackers now use AI agents to scan, plan and run intrusions at machine speed. That changes what a good response looks like.
1. The trend → CrowdStrike reported 1 AI-agent group targeting more than 200 organizations in 11 days. → Unit 42 found attacks moving about 4 times faster than a year earlier. → Wiz's tracker lists 16 AI platforms that disclosed incidents between October 4 and November 9.
2. The 4-pillar playbook → Detect and contain automatically: kill-switches and automatic token revocation. → Communicate fast, and securely: notify customers and partners in hours, over out-of-band channels. → Eradicate thoroughly: assume backdoors and bring in independent forensics. → Shrink the blast radius: Zero Trust and ephemeral design. Data never stored can't be stolen.
3. What it looks like in practice → Fireworks AI detected its October 24 event the same day and brought in Palo Alto Networks Unit 42. → Klue notified customers the same day it found misuse of OAuth tokens, then revoked access.
4. The shared part → Suppliers, platforms, vendors and customers each control part of the risk. → Deleting a key from a breached platform does not revoke it. Rotate at the source.
My take: no company can promise zero incidents. Every company can promise a fast, honest response.
Full analysis: https://www.marktechpost.com/2026/11/19/ai-security-incident-response-playbook-2026/
Fireworks data retention post: x.com/lqiao/article/2121434466082242896
r/machinelearningnews • u/ai-lover • 1d ago
Cool Stuff Give your AI agent a world to fail in. And get better.
AI agents look great in demos. Until real users break them.
Plurai built a world where your agent can fail, learn, and get fixed before your users ever see it.
→ Digital twin: Your real agent, its tools, and environment recreated from your code
→ Simulated users & tasks: Realistic users, tasks, and workflows that push your agent into the edge cases that matter
→ Auto evals: Check what your agent actually did, not just what it said
→ Verified fixes: Every failure comes with the run that exposed it and a fix you can verify
→ Replays: Turn any production failure into a simulation and replay it against every new version of your agent
All inside the coding agent you already use: Claude Code, Codex, or GitHub Copilot.
See where your agent breaks before production: simulation.plurai.ai/connect
r/machinelearningnews • u/OfficialCerebras • 9h ago
ML/CV/DL News What Would the Ideal LLM Inference Chip Look Like?
r/machinelearningnews • u/evol_daed • 8h ago
Startup News LLM VRAM calculator – memory, speed and context for 61 models on 45 GPUs
https://softperceptron.com/vram-calculator
I built this to answer "will this model run on my card, and how fast?" without downloading 40 GB first.
Pick a model, quantization, context length and GPU. It shows whether it fits, how many cards you need, an estimated tokens/sec, and the longest context that fits. You can also enter any Hugging Face model.
Everything is computed from the model's published architecture (layers, KV heads, head dim) and the card's memory and bandwidth. They are estimates, not benchmarks, and the formulas are written out on the page. The speed estimate is memory-bandwidth-bound decode; I checked it against llama.cpp's published gpt-oss 20B numbers and it lands within about 25%.
No login, no ads. I'd like to hear where the estimates are wrong for your hardware.
r/machinelearningnews • u/ai-lover • 23h ago
Research Google released Gemini 4 Neon today. It is the middle model of the Gemini 4 family, and the numbers are worth a close look.
Google DeepMind released Gemini 4 Neon on November 18, 2026. It sits between Gemini 4 Carbon and Gemini 4 Hydrogen and targets coding agents, knowledge work and science workflows. Pricing is $3/$15 per 1M input/output tokens. Weights are closed and the parameter count is not disclosed.
What it does
- Adapted from Gemini 4 Carbon (per the model card)
- 4 thinking levels: high (default) and xhigh are named, the 2 lower levels are not
- 1M-token unified context, 64K default output, up to 1M via background long decode
- Context compaction and fewer redundant file reads for long agent runs
- Can orchestrate parallel Gemini 4 Hydrogen subagents in Google Antigravity
Key numbers (self-reported by Google)
- AA Intelligence Index: 61 (Claude Opus 5.5: 59, GPT-6.2 Sol: 57)
- AA Coding Agent Index: 58.6, ranked #1
- GraphWalks 256K to 1M: 95.2% (Opus 5.5: 66.8%, GPT-6.2 Sol: 80.1%)
- SWE-sweep, provider harness: 39.0% (Opus 5.5: 10.1%)
- Vals Index v2.2: 70.9% (Opus 5.5: 70.1%)
- Google claims 32% lower cost per task than Carbon at high thinking
Full analysis: https://www.marktechpost.com/2026/11/18/google-gemini-4-neon-release/
Technical details blog.google/innovation-and-ai/models-and-research/gemini-models/introducing-gemini-4-neon/
Model card: storage.googleapis.com/deepmind-media/Model-Cards/Gemini-4-Neon-Model-Card.pdf
Try it: aistudio.google.com
r/machinelearningnews • u/ai-lover • 1d ago
Cool Stuff Hugging Face releases Qwen3.8-27B-pi-adapted, a LoRA adapter that lifts Qwen3.8 coding success in the pi agent (SWE-bench Pro hard-51: 39.2% to 64.7%)
Hugging Face's harness-hub team released a rank-32 LoRA adapter for Qwen3.8-27B, trained with reinforcement learning inside the pi coding agent. It is Apache-2.0 and ships with a GGUF adapter. Numbers below are self-reported on the model card.
What it does
- Adapts Qwen3.8-27B to 1 specific harness (pi) with a small LoRA
- Trained with AsyncGRPO (TRL) on 750 scale800 + 300 TermGrade tasks, 8 rollouts per task
- Reward is verifier correctness plus a 0.1 tool-efficiency bonus
- A rule-based proxy (safeagents) screens every tool call during training
Key numbers (pi harness, thinking off, 1 attempt per task)
- SWE-bench Pro (hard 51): 39.2% to 64.7% (+25.5 pts, p = 0.0023)
- Terminal-Bench 2.1 (86 tasks): 39.5% to 55.8% (+16.3 pts, p = 0.0013)
- Median turns on tasks both solved: 59 to 23 (SWE-bench Pro), 18 to 8 (Terminal-Bench 2.1)
- About 4.5x fewer tokens than the base model with thinking
Full analysis: https://www.marktechpost.com/2026/11/18/hugging-face-qwen3-8-27b-pi-adapted-lora/
Model: huggingface.co/harness-hub/Qwen3.8-27B-pi-adapted
Blog: huggingface.co/blog/harness-hub/harness-adapters
Repo: github.com/huggingface/trl/tree/main/examples/async_grpo_harbor
r/machinelearningnews • u/ai-lover • 1d ago
Cool Stuff Nutrient Data Extraction API returns schema-mapped JSON with per-field citations (86.2 on Nutrient's own WholeDoc Bench)
Nutrient AI has a Data Extraction API that parses PDFs, scans, images and Office files into spatial JSON or Markdown, and maps fields onto your JSON schema. Each extracted value carries a page, bounding box and match label, plus a composite confidence score when the engine provides one. It ships with Studio (a browser workspace for testing), a hosted MCP server, a coding-agent skill and an SDK.
What it does
- 4 parse modes (text, structure, understand, agentic) plus auto routing
- Extract, classify, split and form-filling endpoints
- Match labels: id_match, id_match_multiblock, id_match_partial, fuzzy_match, not_found
- Studio presets are saved as versioned processors and called from the API by ID
Key numbers
- WholeDoc Bench (Nutrient-built, 480 docs, 30+ languages): Agentic 86.2 at 1.8¢/page, Understand 80.8 at 0.9¢
- Same board: Claude Fable 5.1 (high) 67.1 at 17.8¢, Azure Document Intelligence 65.9, Reducto R-1 59.9, LlamaParse Agentic Plus 56.7
- Split F1 96.2% vs 63.7% for Typesafe AI's Jev (Nutrient's own evaluation)
- Pricing: parse $0.001 to $0.018/page; extract adds $0.006; classify $0.001; split $0.003; $5 free usage/month
Full analysis: https://www.marktechpost.com/2026/11/18/nutrient-data-extraction-api-citations-confidence/
API: nutrient.io/api/data-extraction-api
Studio: dashboard.nutrient.io/data-extraction-api/studio
Benchmark: nutrient.io/benchmarks/parse
r/machinelearningnews • u/mehdiweb • 9h ago
AI Tools Claude max for $29 instead of $200 ... seriously how are they doing this?
i got a Claude max account from a reseller for essentially nothing compared to what I used to pay . It works flawless. since 3 months No issues yet i paid only for 1 month . Now I can't stop thinking about their business model. If resellers can sell it this cheap and still profit, how are they acquiring these accounts at scale?
r/machinelearningnews • u/FishermanResident349 • 1d ago
Research Looking for self-learners to join BlueprintML
r/machinelearningnews • u/ai2_official • 1d ago
Startup News 🌍 Ai2 and Taylor Geospatial partner to advance open geospatial AI
r/machinelearningnews • u/ScarKey6332 • 1d ago
AI Tools A long-context result with four denominators: 7/7 allergies, 8/10 disorders, 2/7 dental codes, 2/5 meds
This recorded evaluation gives AntLing's Ling-3.0-flash-Sante a complete synthetic patient history: 334 visits over 71 years, totaling 130,993 input tokens in one request. The task is to list current medications, allergies and active disorders with dates, scored against an answer key built from the same generated data.
The reported result is 7/7 allergies, 8/10 disorders, 2/7 dental codes and 2/5 medications. The returned active lists keep stopped items out. One recovered medication began in 1954 and was never stopped, with its evidence at line 108 of 2,728. A different medication was restarted in 1966; the key also contains three medications restarted on the final visit date.
The run uses official FP8 across two DGX Spark machines with MTP enabled. Reading the input takes 61 seconds, followed by about 30,865 thinking tokens over roughly eleven minutes.
For a similar evaluation, keep the category denominators and date rules beside the latency readings. This case makes both the retrieved facts and the remaining target entries inspectable.
r/machinelearningnews • u/ai-lover • 2d ago
Research Zero data retention explained: the 2 standard API designs behind AI data retention (batch vs ephemeral)
A lot of teams treat "zero data retention" (ZDR) as a vendor-wide label. It isn't. It belongs to specific endpoints, and it depends on which of 2 standard API designs you use. This explainer walks through the framework Fireworks AI CEO Lin Qiao laid out, with examples from public API docs.
What it does
- Customer-managed retention (upload, use, delete): you upload a dataset, run jobs on it, then delete it. Batch APIs at OpenAI, Amazon Bedrock, Gemini and Fireworks AI work this way.
- Ephemeral processing (send, compute, return): the platform processes a request and returns the result without keeping the content. OpenAI Chat Completions, Bedrock Converse, Gemini text generation (with store set to false), Fireworks Chat Completions and the Fireworks Training SDK are examples.
- In both designs, the customer controls the data. The difference is where the lifecycle is managed.
Key numbers (from vendor docs)
- OpenAI batch files expire after 30 days by default. Other uploaded files persist until deleted.
- Anthropic keeps Message Batches data for 29 days.
- Google's Interactions API stores interactions by default (store=true).
Full analysis: https://www.marktechpost.com/2026/11/17/zero-data-retention-ai-apis-explained/
r/machinelearningnews • u/ALexiosK11 • 2d ago
AI Tools Spent months fighting to get a full RAG pipeline (BGE-M3 + reranker + TTS) running on a 4GB laptop GPU. Here's what broke.
started this as a personal project to read massive textbooks and web novels, and it turned into a war with hardware limits.
my setup is a windows laptop with 16GB RAM and a 4GB RTX 3050. no cloud, no "just throw more vram at it." the stack is tauri (rust) shell, nodejs orchestrator, and a python sidecar for pytorch models (bge-m3, bge reranker, kokoro tts).

here are the three walls i hit:
- the node memory cliff
unbounded async ingestion spiked node.js memory to 14.6GB on a 16GB machine. i fixed it by implementing a strict sequential await barrier (f65) that streams chunk-by-chunk. peak ram dropped to ~296MB for a 508,000-word book (5.9 min processing).
- 4gb vram musical chairs
loading bge-m3 in fp32 ate ~3.9GB of vram, leaving zero room for the reranker or tts. switched to fp16 (~1.1GB) and wrote an idle ttl eviction manager (f43) that reclaims ~3.2GB of vram when models sit unused.
- silent speakers
even after bundling the python sidecar into tauri, webview2 blocked tts audio playback. had to share a single user-gesture-unlocked audiocontext between ui sounds and narration to fix it.
also learned that a clickable citation makes a sentence inspectable, but it doesn't magically prove the llm is right. compression ratios vary (3.6:1 to 5:1 in my samples), so the human still has to be the judge.
it's open source (agpl-3.0) with a windows installer. works with ollama, lm studio, or byok endpoints to keep everything local.
code and builds here if anyone wants to dig into the architecture or roast it:
https://github.com/ayumu-ml/Omnitome
happy to answer questions about the retrieval setup or squeezing multiple models onto a 4gb gpu.
r/machinelearningnews • u/OfficialCerebras • 2d ago
ML/CV/DL News Cerebras Launches Disaggregated Inference
r/machinelearningnews • u/ai-lover • 2d ago
Research Liquid AI releases d1.2 and d1.2-ultra, omnimodal decision models (75 on the AA Decision Index)
Liquid AI released d1.2 and d1.2-ultra on November 16, 2026. They are decision models: instead of generating text, they return a probability for every option in 1 call, so only input tokens are billed. The new versions accept text, images and audio and add 5 typed answer formats.
What it does
- Reads a state (text/JSON, up to 8 images, up to 300 s of 16-bit WAV audio) plus up to 128 typed questions
- New answer types: value extraction with source characters, spans with positions, boxes, number with range, multi-label choice
- Audio can be the subject of a question or the question itself
- 65,536 input tokens per question, 4.5 MB request body
Key numbers
- AA Decision Index v2.1: d1.2-ultra 75, Drex Max v1.1 73, SubQ Snap 1.2 73, GLiDE v1.2 73, Perplexity Decider v1.3 70, d1.2 69
- Calibration error, 13 benchmarks / 22,505 questions (self-reported): d1.2-ultra 0.8, d1.2 1.2, Jev 1.14 2.7, Decider v1.3 3.7, GPT-6 Luna (Decisions API) 7.2
- New tasks on internal test sets (self-reported): receipts 98% / 96%, PII precision/recall 94/93 and 92/88, object location 94% for both
- Price: $0.02 (d1.2) and $0.042 (d1.2-ultra) per 1M input tokens, output free
Full analysis: https://marktechpost.com/2026/11/17/liquid-ai-d1-2-omnimodal-decision-models/
Blog: http://liquid.ai/blog/d1-2
Docs: http://docs.liquid.ai/lfm/models/d1
Index: http://artificialanalysis.ai/evaluations/artificial-analysis-decision-index
r/machinelearningnews • u/ai-lover • 2d ago
Research NVIDIA open-sources NVKE and NVKR, a managed Kubernetes stack for GPU bare metal (conformance tested on K8s 1.36)
NVIDIA released 2 Apache 2.0 projects in public preview. NVKE is a management plane that lets a GPU cloud run a managed Kubernetes service on its own hardware. NVKR builds and signs the node images, container images and Helm charts those clusters use. NVKE has no runtime dependency on NVKR.
What it does
- REST API and controllers on a 3-server management cluster create customer clusters
- Each customer cluster has its own control plane, etcd and node pools
- Bare-metal machines come from NVIDIA Infra Controller (NICo) via CAPNICo, a Cluster API provider
- Nodes need a TPM-attested SPIFFE identity before receiving join credentials
- Built on upstream Kubernetes, kubeadm and Cluster API
Key numbers (self-reported by NVIDIA)
- Conformance tested on Kubernetes 1.36; Certified Kubernetes AI Platform and Installer
- amd64 and arm64 builds
- Local quickstart: 6 CPUs, 12 GiB RAM, 100 GiB disk, no GPU
Full analysis: https://www.marktechpost.com/2026/11/17/nvidia-nvke-nvkr-managed-kubernetes-gpu/
NVKE: github.com/dsx-ai-factory/nvke
NVKR: github.com/dsx-ai-factory/nvkr
Docs: docs.nvidia.com/nvke
r/machinelearningnews • u/phenex_agi • 2d ago
Research [R] The Agent Memory Wall: KV-cache hits for AI agents collapse once their working set passes ~1.2-2.2x the cache (pre-registered, H200)
I measured what happens to GPU energy when AI agents' KV caches are evicted during tool calls: one H200 NVL, vLLM and SGLang, Qwen3-32B / 30B-A3B / 8B, synthetic agent sessions, recorded SWE-agent trajectories, a replay of Kimi's production tool-agent trace (Mooncake) and BFCL v4. Every prediction was pre-registered before its run.
Findings:
- Hits don't degrade gradually. Past ~1.2-2.2x working set over cache they collapse, and energy per turn ends up within 0.01-1.6% of running with no cache. Qwen3-32B, ~27k-token sessions: 8 sessions kept 88% of prompt tokens cached, 16 kept ~0%.
- Restoring a prompt's KV from host memory costs ~1/110-1/220 of the above-idle GPU energy of recomputing it.
- On the overloaded production replay, a 160 GB host tier took finished requests from 85-86% to 100%, with 16-18% more prompt tokens for about the same energy. At a lighter load it saved under 1%.
- BFCL: accuracy with and without the cache differed by 3 of 400 tasks; the cache doubled correct answers per kWh.
Limits: one GPU type, GPU board energy only (NVML), single node.
Feedback on the method is very welcome.
r/machinelearningnews • u/ai-lover • 3d ago
Research Alibaba releases Qwen4-Max, a proprietary 2.4T MoE with 71B active parameters (1M context, $1.5/M input)
Alibaba's Qwen team released Qwen4-Max, the first Qwen4 model. It is a closed, API-only sparse MoE with a 2.4T-parameter backbone, 71B active parameters per token, native vision and a 1M-token context. Alibaba also cut API prices versus Qwen3.8-Max. All benchmark numbers below are self-reported by Alibaba or cited by Alibaba from third-party leaderboards.
What it does
- Reads text, images and video, writes text, with up to 393K output tokens
- 3 Gated DeltaNet layers per Qwen Sparse Attention (QSA) layer; QSA uses a lightweight indexer to select context at micro-block granularity
- 4 gated residual branches plus 328B N-gram Embedding parameters at layer 2
- OpenAI-compatible and Anthropic-compatible API, function calling, structured outputs, caching, batch, fine-tuning
Key numbers (self-reported)
- First on 4 of 16 charted benchmarks: HLAB-Vals-1.1 21.3, Agents' Last Exam v1.1 46.7, BioMysteryBench 85.0, DeepSWE v1.1 75.7
- Work360 (Alibaba's in-house benchmark): 52.69 vs 47.74 for Qwen3.8-Max
- Work360 cost per task: $4.43 to $1.67 (62% lower); up to about 50% fewer tokens
- Price: $1.5 input / $4.5 output / $0.075 cached input per 1M tokens (Qwen3.8-Max: $2 / $6 / $0.25)
Full analysis: https://www.marktechpost.com/2026/11/16/alibaba-qwen4-max-release/
Technical details: qwen.ai/blog?id=qwen4-max
API: qwencloud.com/models/qwen4-max
Pricing: qwencloud.com/pricing/token-plan
r/machinelearningnews • u/Pretty-Swordfish9203 • 3d ago
Research How much can we actually trust open base model benchmarks anymore? New study ("Benchleaking") finds ERNIE-5.5-Flash-Base reciting unseen test sets in exact order.
Link to the report & repo:https://github.com/GAIR-NLP/Benchleaking
Saw this making the rounds today and thought it was worth sharing here. Basically, they removed stop tokens during few-shot evals and found that ERNIE-5.5-Flash-Base just keeps going after answering—reciting 96% of HumanEval, 85% of OpenBookQA, and 80% of GSM8K verbatim in exact dataset order (including reference solutions and even original typos like "for examble:" in HumanEval #67).
Across the four open base models they tested, zeroing out leaked items drops the 20-benchmark average by up to 16.6 points on heavily contaminated ones, while cleaner base models stay within 1.5 points of their original scores. Curious how people doing SFT/RL on open weights feel about this—does pre-training contamination ruin downstream evals for everyone else too?

r/machinelearningnews • u/ai-lover • 5d ago
Research Cmpnd releases dspy-wsp, a DSPy optimizer where GPT-6-Astra edits model weights directly (d1-omni-600M +18.3 pts on Typed Decisions)
Cmpnd released dspy-wsp, a prototype DSPy optimizer built on the "Sparks of Weight-Space Programming" work from MIT CSAIL (Takehi, Teoh, Zhang, Khattab). A frontier "writer" LLM reads a small student model's weights in a sandbox, edits them with Python, and checks edits with a capped number of forward passes. No gradients and no training data pipeline. All numbers below are self-reported by Cmpnd.
What it does
WeightSpaceoptimizer works with any DSPy module and metric- Writer:
gpt-6-astraat max reasoning effort, 25 forward passes per run - Writer sees practice examples and holdout scores, never holdout examples; a hidden valset is used once at the end
- Output is a patch (
manifest.json+edit.npz) with sha256 hashes, so anyone with the public base model can rebuild the edited weights - Backends: Liquid AI d1-omni, d1-2B, NanoJev; text LLMs via vLLM, HF or MLX
Key numbers (Typed Decisions, 400 held-out cases)
- d1-omni-600M: 50.9% → 66.9% (WeightSpace) → 69.1% (+ ReAnchor)
- NanoJev (Qwen3-0.6B): 39.2% → 52.4% → 56.4%
- d1-2B: 60.6% → 74.0% → 77.9%
- Clef-Flash 9B: 68.8% → 70.7% → 75.3%
- Cost: $5.42 to $7.63 per run, 78 to 167 minutes, on 1 Mac
Full analysis: https://www.marktechpost.com/2026/11/14/cmpnd-dspy-wsp-weight-space-programming/
Repo: github.com/cmpnd-ai/dspy-wsp
r/machinelearningnews • u/remoteinspace • 5d ago
Research LongMemEval-S: 96.0% with the official judge, and what top-5 vs top-20 retrieval changes
r/machinelearningnews • u/strata2signal • 6d ago
Research Temperature, top-k and top-p explained: the model only sets the odds, a sampler rolls the dice, and temperature 0 does not promise the same answer every time
A language model never picks a word. Its last output is a list of scores, one for every token it knows (262,144 of them on one model we run). Ordinary code outside the network, called a sampler, turns the scores into chances and draws one token. Temperature, top-k, top-p, min-p and the repetition penalty are the settings on that draw.
The guide works one made-up example by hand: five candidate tokens after "The lighthouse keeper poured a cup of", with scores 3, 2, 1, 0 and -1. Divide the scores by the temperature and the favourite, "tea", gets 86.5 % of the draws at 0.5, 63.6 % at 1 and 42.9 % at 2. The order never changes; temperature decides how often the long shots come up. Top-k, top-p and min-p then cut the unlikely tail in three different ways: on the same table, top-p 0.9 keeps 2, 3 or 4 tokens depending on the temperature.
Two things worth knowing before you compare outputs. The defaults differ: as documented on 2026-11-13, llama.cpp's server and Ollama ship temperature 0.8 and vLLM ships 1.0; top-k is 40, 40 and off; top-p is 0.95, 0.9 and off. And the order differs: llama.cpp cuts first and applies temperature last, vLLM applies temperature first. With only temperature 2 and top-p 0.9 switched on, one order keeps four of our five tokens and the other keeps three, so the same two numbers give different text.
Temperature 0 removes the dice and takes the top score. It does not promise the same answer every time: llama.cpp's own server manual warns that "the logits are not guaranteed to be bit-for-bit identical for different batch sizes". And the likeliest token is not a checked fact.
What it cannot tell you: which settings are best. Nothing was tested for this guide; the example's scores are made up and the arithmetic is ours; the defaults are one day's reading of each project's documentation, and a model's maker or a single request can override them.
The practical point: before comparing two answers, ask three things: which settings, in which order, set by whom.
The guide, with every source: https://research.strata2signal.com/temperature-and-sampling-in-plain-words/
A small human team asked for this; AI agents read the sources and drafted it; every figure is linked to its source on the page.
r/machinelearningnews • u/ai-lover • 6d ago
Research Perplexity releases Decider v1.3 and Flash v1.3, open-weight decision models with span extraction (91.6% on 63 query-classification tasks)
Perplexity released pplx-decider-v1.3 (built on Qwen3.8-27B) and pplx-decider-flash-v1.3 (distilled into Qwen3.5-4B) under Apache 2.0. They answer yes/no, multiple-choice and score questions with probabilities instead of generated text. The new Locate feature extracts exact text spans with character offsets.
What it does
- Takes a shared state (text or images) plus multiple labeled questions, answered in 1 forward pass
- v1.3 isolates questions: each sees only the state and itself, unlike v1.2
- Locate returns spans for NER, PII and extractive QA via a span head plus an unmerged LoRA adapter
- Available on Hugging Face, OpenRouter and the Perplexity Decisions API
Key numbers (all self-reported by Perplexity)
- 91.6% mean accuracy on 63 query-classification tasks
- 83.99 nDCG@10 on 72 retrieval tasks (+1.81 vs Qwen3-Reranker-8B, +2.24 vs Jev 1.14)
- Locate average 69.0 (v1.3) and 63.6 (Flash) vs 43.3 for Liquid d1 and 33.6 for GLiNER large v2.5
- 93.98% agreement with frontier LLM judges on 1M real API requests (Jev 1.14: 93.35%)
- $26.47 to run those 1M requests vs $68.10 for Jev 1.14
- API: $0.02 (v1.3) and $0.01 (Flash) per 1M input tokens, output free
Full analysis: https://marktechpost.com/2026/11/13/perplexity-decider-v1-3-open-weight-decision-models-locate/
Model: http://huggingface.co/perplexity-ai/pplx-decider-v1.3
Flash: http://huggingface.co/perplexity-ai/pplx-decider-flash-v1.3