CATALOG / 269 PUBLISHED WORKBENCHES
269 local tools sit in 12 categories, so category counts always add up to the catalog — never more. Subject collections and network platform surfaces are listed separately because they answer a different question.
01 / REGISTRY FAMILIES
Every published tool belongs to exactly one category. These counts add to 269 of 269 tools, and nothing is counted twice.
Formula, cost, schedule, and ratio workbenches
73 tools · localLocal transformation, parser, and reference workbenches
56 tools · localPrivate counts, line handling, comparison, and transformations
32 tools · localFixed-factor unit, date, timezone, and color conversions
36 tools · localLocal identifiers, passwords, content, and configuration outputs
22 tools · localLocal hashes, encodings, strength checks, and security references
10 tools · localMetadata, structured-data, readability, and page analysis
10 tools · localPure arithmetic, algebra, geometry, and physics workbenches
8 tools · localChemistry and statistics calculations with explicit formulas
6 tools · localAddressing, CIDR, ports, URLs, and protocol references
6 tools · localSQL generation and local data-shape transformations
4 tools · localCSS, SVG, sizing, and layout utilities
6 tools · local02 / COLLECTIONS
Collections are subject lenses, not registry partitions — a workbench can appear in a collection and in its family at the same time, so collection counts are not added to the registry total.
Money, tax, loan, and margin workbenches gathered across the registry.
16 tools · also listed in their categoriesUnit-economics, operations, and document workbenches gathered across several families.
25 tools · also listed in their categories03 / PLATFORM SURFACES
These are network features, not categories of local tools. Each one says what leaves the browser before you run anything.
Provider-backed lookups with named sources, retrieval timestamps, and explicit freshness states.
5 live utilities · Your query is sent to the named provider through UtilityForge's server adapter.A guarded, HTTPS-only request surface with DNS pinning, redirect revalidation, and response redaction.
1 guarded surface · Approved requests are relayed by UtilityForge's server under published limits.Provenance-first directory of external APIs, holding only records with stored evidence.
Beta — no published records yet · Nothing is fetched on your behalf; records are curated source evidence.