The whole RobbJack catalog, machine-readable.
7,108 standard tools with ISO 13399-coded specifications in inches and millimeters — JSON for systems, CSV for spreadsheets, and a SHA-256 manifest so you can trust every byte. This is the feed tool-data managers consume.
The files
Schema v1.0 · generated 2026-07-17 · regenerated whenever the catalog changes — re-download rather than caching long-term.
- JSON5.5 MBrobbjack-master-catalog.jsonFull structure: parameter legend, link templates, per-tool specs, saw parametrics
- CSV3.8 MBrobbjack-master-catalog.csvThe same tools flattened one row per tool (inch + mm columns), Excel-friendly
- Manifestrobbjack-master-catalog.manifest.jsonSchema version, generated date, tool counts, file sizes, SHA-256 checksums
What's in the JSON
- A self-describing header: publisher, license, unit conventions, and the full parameter legend (below), so your importer never guesses what a column means.
- Link templates for every per-tool resource — product page, ISO JSON/CSV, 2D DXF, 3D STEP, speeds & feeds — keyed by part number.
- All 7,108 tools with ISO 13399-coded specs. Every length carries both
inandmmat full precision; angles are degrees. - Series, product line, tool types, available coatings, and country of origin per tool.
- A
sawParametricsection describing all 88 slitting-saw families by range, step, and part-number rule — see below.
The CSV is the same catalog flattened to one row per tool with paired _in/_mm columns — open it straight in Excel, or feed it to a converter or tool-manager import.
The saw rule: any thickness is a standard part
RobbJack slitting saws are parametric: within each of the 88 saw families, every 0.0001″ thickness step between the family's thinnest and thickest standard size is a standard, orderable part number — not a special. Enumerating them would bloat your import by hundreds of thousands of rows, so the JSON instead carries each family's diameter, thickness range, step, tooth count, and part-number encoding rule.
Need the data for one specific in-between thickness? Ask the API — it synthesizes the full ISO record for any valid saw part number on demand, derived from the next thicker standard saw:
GET /api/iso?tool=<saw part number>&format=jsonExact-thickness ordering lives on each saw family's tool page — browse slitting saws.
Shared parameter legend
ISO 13399 parameter codes as used in the JSON, the CSV column headers, and the per-tool API. The JSON embeds this same legend.
| Code | Meaning | Unit |
|---|---|---|
| DC | Cutting diameter (saw outside diameter for saws) | in / mm |
| DCX | Maximum cutting diameter | in / mm |
| DMM | Shank diameter | in / mm |
| APMX | Maximum depth of cut / length of cut | in / mm |
| OAL | Overall length | in / mm |
| RE | Corner radius | in / mm |
| CHW | Corner chamfer width | in / mm |
| KCH | Chamfer angle | deg |
| NOF | Number of flutes (teeth for saws) | — |
| FHA | Helix angle | deg |
| FHH | Helix hand | — |
| CW | Cutting width (saw thickness) | in / mm |
| arbor_bore | Arbor hole (bore) diameter | in / mm |
| max_depth_of_cut | Maximum depth of cut (saws) | in / mm |
| recommended_arbor | Recommended arbor | — |
| SDL | Reach / length below shank | in / mm |
| ND | Neck diameter | in / mm |
| LN | Neck length | in / mm |
| SIG | Point angle | deg |
| DC_TOL | Diameter tolerance | — |
| CCMS | Country of origin | — |
CATIA, TDM, Zoller, WinTool, MachiningCloud
Tool-data managers and CAD/CAM tool libraries standardize on ISO 13399 — the same parameter model this catalog is coded in. There's no separate “CATIA file” to wait for: this feed is the ISO 13399 layer those systems consume.
- Bulk load: map the JSON (or CSV columns) once using the legend above — codes match the ISO parameter names your system already uses (DC, DMM, APMX, OAL, RE, CW…).
- Single-tool load: pull one record at a time from the per-tool API below, in JSON or CSV, inch or metric.
- Keep it fresh: check the manifest's
generateddate and re-pull when it changes.
Building an integration and want a hand? Talk to us →
Verify your download
The manifest carries a SHA-256 checksum for every file, so you can prove the bytes you feed your production tool library are exactly the bytes we published:
Windows (PowerShell)
Get-FileHash robbjack-master-catalog.json -Algorithm SHA256macOS / Linux
shasum -a 256 robbjack-master-catalog.jsonCurrent checksums (from the manifest):
- JSON
0bf3590d9869acf5ddc71e5d0fb127ae52a96b6d1a8c545e4135f1dec270cd85 - CSV
691d731d054f3c71271ef95b70c7824334c114308ca3eaec529e3b34838d5774
Per-tool API
When you don't want the whole catalog: one HTTP GET returns a single tool's ISO 13399 record — including on-demand synthesis of any in-between slitting-saw thickness. JSON responses also carry links to the tool's product page, CAD, and speeds & feeds.
GET https://robbjack.com/api/iso?tool=A1-201-04&format=json&units=both| Parameter | Values | Notes |
|---|---|---|
| tool | part number | Any catalog tool — or any in-between saw-thickness part number (synthesized on demand) |
| format | csv (default) · json | CSV downloads as a file; JSON returns specs plus product/CAD/speeds-feeds links |
| units | both (default) · in · mm | JSON only — CSV always carries both unit systems |
Run Fusion 360? Skip the mapping entirely.
The native .tools library imports in one step — geometry plus 12,307 RobbJack tested cutting presets.