earlyink
151 updated first flagged17 Oct 2026

Bulk Pass: batch extraction over CSVs on the new fast, cheap models

A CLI that tests a sample, picks the cheapest model that passes, then runs your whole file. Data-heavy small teams pay.

Early · Mercury 3 speed plus MiniMax price cut

Written for: Solo builder

Next step

This week, run one 10k-row extraction job across Mercury 3, MiniMax M3.1 Flash, DeepSeek V4.1 Flash and Haiku 5.5. Publish cost, time and accuracy with the CLI on r/LocalLLaMA and r/dataengineering.

Why now

This idea was on the watchlist because it needed a local GPU running diffusion models. Fast diffusion and flash-tier models are now available as hosted APIs, so the GPU requirement is gone. What's missing is a tool that picks the right model per job against your own labels and handles retries and resume across 100k rows.

What became possible

Inception's Mercury 3 diffusion LLM claims to beat GPT-6 Luna, Claude Haiku 5.5 and GLM-5.3 Flash on agentic benchmarks while running 4x to 8x faster. MiniMax M3.1 Flash gained 13 points on the Artificial Analysis Intelligence Index at half the cost of its predecessor. It matches DeepSeek V4.1 Flash at under $0.30 per coding task.

Two ways in

  1. bulkpass CLI

    Run `bulkpass run rows.csv --task 'extract vendor, amount, date'`. It tests 100 rows across four models against your hand labels, picks the cheapest one that passes, then runs the rest with resume and a cost report.

    Customer
    Analysts and small data teams cleaning invoices, leads or support tickets
    Model
    Free OSS. A hosted queue charges a margin on tokens or $19 per month
  2. Sheets add-on

    The same flow inside Google Sheets, for people who never open a terminal.

    Customer
    Small-business operators and ops staff
    Model
    $9 per month self-serve

Competition

Early

No one ships the specific product: a CLI that takes a CSV and a JSON schema, batches rows through a diffusion LLM on one local GPU, validates the outputs and sends failed rows to an autoregressive fallback. The pieces are all there, though.

Full competition notes (12 competitors)

No one ships the specific product: a CLI that takes a CSV and a JSON schema, batches rows through a diffusion LLM on one local GPU, validates the outputs and sends failed rows to an autoregressive fallback. The pieces are all there, though. SGLang, dInfer, Fast-dLLM and llama.cpp give you diffusion inference. Bespoke Curator, Instructor and Sculpt give you bulk, schema-validated runs with retries, mostly on autoregressive models. Inception's Mercury API gives you fast, cheap diffusion inference with structured outputs and no GPU. So the moat is thin: Curator could add a dLLM backend easily, and many indie teams will prefer Mercury's hosted API to running a GPU. A new entrant could still win with an opinionated, local-first tool that turns a CSV into validated output with no setup. It would pick the dLLM model and decoding settings for the user, handle schema validation and the fallback, and report the cost and speed gain over running a model like Qwen through vLLM. That only pays off if diffusion models really are faster and accurate enough on short, schema-shaped outputs. That is unproven. The fastest local figure I found was d3LLM's self-reported 289 tokens per second on an H100, and "thousands of tokens per second" is Mercury's hosted figure, not a local one. I also found no public trace of "dlmrt", the runtime the pitch names. The benchmark idea is the clearer opening. Only scattered academic papers exist, such as the multi-label classification study and ParallelBench, plus vendor blog posts. There is no maintained public leaderboard comparing diffusion and small autoregressive models on extraction and classification. Building one would also bring in users for the CLI and test whether it is worth building. The risk is that the main runtime projects or Inception publish their own.

  • SGLang diffusion LLM support (LMSYS)

    Production-style serving for diffusion LLMs like LLaDA 2.0 inside SGLang. It is a general engine with no CSV, schema or fallback workflow, but it is the most likely backend a user would reach for instead.

  • dInfer (inclusionAI / Ant Group)

    Open-source dLLM inference framework with batched inference for throughput. Infrastructure only.

  • Fast-dLLM (NVlabs)

    Training-free acceleration for Dream and LLaDA using block-wise KV cache. Research-oriented, not a data tool.

  • llama.cpp diffusion CLI

    llama-diffusion-cli runs Dream, LLaDA, RND1 and (via Unsloth guides) DiffusionGemma locally. It generates text but has no batch-over-CSV, schema validation or retry logic.

  • DiffusionGemma local guide (Unsloth)

    Shows a big-lab diffusion model that people can already run locally, which lowers the barrier for DIY bulk pipelines.

  • Bespoke Curator

    Python library for bulk inference and dataset annotation with a vLLM local backend, caching and retries. Closest workflow competitor; it is autoregressive-focused but could add a dLLM backend.

  • Inception Labs Mercury API

    Hosted commercial diffusion LLM with structured outputs, an OpenAI-compatible API, around 1,100 tokens per second and roughly $0.25/$0.75 per million tokens. A cheap hosted substitute for running dLLMs locally.

  • Sculpt

    Schema-based structured extraction library with parallel batch mode. Not local-GPU or diffusion specific.

  • Instructor batch processing

    Popular structured-extraction library with batch support across providers. Adjacent: covers the validate-and-retry layer.

  • Discrete Diffusion LMs Are Training-Free Multi-Label Classifiers (arXiv)

    Academic comparison of LLaDA-8B against Qwen2.5-7B on classification with mixed results. The closest thing to the proposed quality benchmark, but a one-off paper, not a maintained leaderboard.

  • ParallelBench (ICLR 2026)

    Studies quality trade-offs of parallel decoding in dLLMs versus autoregressive models. Relevant to the benchmark idea but not focused on extraction or classification.

  • dLLM-Serve (arXiv)

    Research serving system for diffusion LLMs built on Nano-vLLM. Shows active systems work on dLLM throughput.

Checked 2026-10-17

Risks

  • Mercury 3 and MiniMax figures are vendor-reported
  • OpenAI and Anthropic batch discounts already make bulk jobs cheap
  • After the DHS DeepSeek ban, some customers will refuse Chinese-origin models
  • Thin moat

Strong team fit and buildability; open space is the weak point (4).

tech 7 · pull 5 · space 4 · fit 9 · build 9

Momentum of its main topic

53 developments this week +10 vs last week
21 Sep: 0 developments22 Sep: 0 developments23 Sep: 0 developments24 Sep: 0 developments25 Sep: 0 developments26 Sep: 0 developments27 Sep: 0 developments28 Sep: 0 developments29 Sep: 0 developments30 Sep: 0 developments1 Oct: 0 developments2 Oct: 0 developments3 Oct: 0 developments4 Oct: 0 developments5 Oct: 0 developments6 Oct: 0 developments7 Oct: 0 developments8 Oct: 7 developments9 Oct: 9 developments10 Oct: 9 developments11 Oct: 4 developments12 Oct: 7 developments13 Oct: 7 developments14 Oct: 4 developments15 Oct: 9 developments16 Oct: 7 developments17 Oct: 10 developments18 Oct: 6 developments19 Oct: 7 developments20 Oct: 10 developments
Stage: Coverage

Sources

  1. Inception debuts Mercury 3, a diffusion LLM that it says tops GPT-6 Luna, Claude Haiku 5.5, and GLM-5.3 Flash on agentic benchmarks while being 4x to 8x faster (Jason Hiner/The Deep View)Techmeme
  2. Mercury 3: Diffusion at scaleHacker News
  3. MiniMax M3.1 Flash shows China's AI price race has no floor in sightThe Decoder
  4. MiniMax M3.1 FlashHacker News
  5. DeepSeek V4.1 Flash 1017 (Max)Hacker News
  6. DeepSeek banned from U.S. federal civilian agencies under new DHS orderHacker News

Status history

  • 2026-10-17 Added to the watchlist
  • 2026-10-20 Promoted from the watchlist: Today's evidence made it buildable
  • 2026-10-20 Flagged as buildable