sluicer 0.3.0

Turn a web page into structured data. No model, no API key, no bill.

Sluicer reads the structured data a web page already declares -- JSON-LD, microdata, RDFa, OpenGraph, the Twitter card, HTML's own meta names -- and merges it into one record per thing, every value naming the vocabulary and key it came from. No model reads the page, so the same page always gives the same answer and a run costs CPU. Learn an extractor from a few pages of a template and every replay checks the page still keeps to it: a site that changed its layout fails loudly, and heal says what moved where.

uv tool install 'sluicer[fetch,markdown,mcp]'
sluicer extract product.html --url https://example.com/product

It prints, abridged:

{
  "summary": {
    "title":    { "value": "Brake pad set", "source": "jsonld", "key": "Product.name" },
    "price":    { "value": "41.90", "source": "jsonld", "key": "Product.offers" },
    "currency": { "value": "EUR", "source": "jsonld", "key": "Product.offers" },
    "image":    { "value": "https://example.com/i/pads.jpg", "source": "opengraph", "key": "og:image" }
  },
  "records": [
    {
      "type": "Product",
      "fields": {
        "name":   { "value": "Brake pad set", "source": "jsonld" },
        "offers": { "value": { "@type": "Offer", "price": "41.90", "priceCurrency": "EUR" }, "source": "jsonld" },
        "mpn":    { "value": "BP-2210", "source": "microdata" },
        "image":  { "value": "https://example.com/i/pads.jpg", "source": "opengraph" }
      }
    }
  ],
  "sources": ["jsonld", "microdata", "opengraph"]
}

That page described one product three times, in three vocabularies. You get one record, a summary of the questions you came with, and the provenance of every value. sluicer inspect prints the same reading laid out for a person.

How it differs

• From extruct, which returns each vocabulary as the page wrote it: Sluicer merges them into one record per thing, keeps where each field came from, answers a summary with its reader and key, and resolves JSON-LD references.
• From trafilatura and newspaper4k, which read authors and dates from the visible text: Sluicer reads only what the page declares. It answers less often, and is wrong less often -- see the numbers.
• From a scraper of CSS selectors: an extractor checks every page it reads against what it learnt, and a page that drifted fails with exit code 3 instead of returning nulls for weeks.
• From an LLM scraper: no model, no key, no bill, and the same answer every time.

Why Sluicer has the full comparison, and when another tool is the better choice.

Use it

sluicer extract page.html                           # a file, a URL, or - for stdin
sluicer inspect https://example.com/product         # the same, for a person to read
sluicer extract listing.html --induce               # rows of a page that declares nothing
sluicer markdown https://example.com/article        # the readable content

sluicer compile page1.html page2.html -o shop.json  # learn an extractor
sluicer run shop.json https://shop.example/c?p=7    # replay it, checked
sluicer heal shop.json https://shop.example/c -o shop.json  # after a redesign

Exit codes follow grep: 0 found, 1 nothing declared, 2 could not read, and 3 for a page that broke its extractor or a heal that lost a field. A drifted page never exits 0.

import sluicer

result = sluicer.extract(html, url="https://example.com/p")
print(result.summary["title"].value, "via", result.summary["title"].key)

For an agent: claude mcp add sluicer -- sluicer-mcp, or install the repository as a Claude Code plugin with /plugin install. Six tools -- extract_declared, page_markdown, fetch_page, compile_extractor, run_extractor, heal_extractor -- each answering with ok, which is true exactly when the answer can be used as it is, and an output schema. The server fetches nothing on localhost, a private network or a cloud's metadata endpoint -- redirects and a browser's requests included -- unless started with SLUICER_ALLOW_PRIVATE=1.

Install

uv pip install sluicer                          # the library and the command: lxml and click
uv pip install 'sluicer[fetch,markdown,mcp]'    # fetching, markdown, the MCP server
uv pip install 'sluicer[microformats]'          # microformats2, off by default
uvx --from 'sluicer[fetch]' scrapling install   # the browser, once, for the browser rung

Without a browser, plain HTTP still works, and a page that wanted one comes back from the HTTP rung with the failed climb recorded.

Measured, losses included

The summary beside the tools people use for the same job, on the 511 annotated test pages of the public WCXB corpus. Hit rate is right answers over the pages that carry a label; an invention is an answer on a page whose label is empty.

WCXB strips every <script>, so JSON-LD, the vocabulary Sluicer reads first, is not measured there. The same labels on the 360 of those pages that a web archive holds as their servers sent them, scripts intact:

With the scripts back, JSON-LD appears on 236 of the 360 pages, and Sluicer's author and date hit rates rise from 0.434 and 0.553 on WCXB's copies of the same pages to 0.674 and 0.748. It still finds fewer authors and dates than trafilatura, which also reads them from the visible text, and it is still the most often right when it answers a date. 31 of its 34 invented dates are dates the page declares in its own JSON-LD and does not show a reader, which is what the labels describe. The method, every outcome and the commands that regenerate both tables are in the scoreboard and the scoreboard on pages as served.

Extractors are measured too: learnt on Wayback Machine captures of 25 sites and replayed on later ones, 44 pairs, none failed silently and none raised a false alarm. See drift.

Principles

• No LLM call, anywhere in the path. A test fails the build if a model client is ever imported.
• No paid API. A feature that needs somebody's key does not ship.
• Deterministic. The same page always gives the same answer, which is what makes the scoreboard reproducible.
• Honest about failure. A page that cannot be read says so, and nothing returns a plausible answer where the truth was unavailable.

Documentation

At https://gi0tto.github.io/sluicer/, or in the repository: Why Sluicer · Extractors · Scoreboard · Scoreboard, as served · Drift · Known limits · Design notes · Examples · Roadmap · Changelog · Security · Contributing

Licence

MIT, with no vendored code. The base install needs lxml and click, both BSD-3-Clause. The extras pull a wider tree that is not all permissive: tld is tri-licensed MPL-1.1, GPL-2.0-only or LGPL-2.1-or-later, orjson is MPL-2.0 alongside Apache-2.0 or MIT, and certifi is MPL-2.0. CI lists every licence in that tree and fails on one nobody has read; see the licence notes.