chip-fetcher — tool map
What runs in your container vs. what we call over the network. Generated 2026-06-24 · updated for native Altium + EAGLE.
orchestrator
local CLI — runs in your container
local library (Rust crate, not a separate app)
remote service container — we call it over HTTPS
your laptop — reached via adom-desktop bridge
⬢ adom-chip-fetcher
The orchestrator. Pulls every CAD format off the internet, converts + renders each, and shows them side-by-side so you can pick what to export.
▼ shells out to (all local CLIs) ▼
Convert & renderturn each downloaded format into geometry + thumbnails
adom-sfconvert NEW
EAGLE/Fusion .lbr → KiCad AND Altium → KiCad — fully native, pure Rust.
native libs: altium-schlib + altium-pcblib + eagle — no service
adom-symbol
Renders the schematic symbol (with 3D chip embossed).
→ service-kicad
adom-footprint
Renders the PCB footprint SVG.
→ service-kicad
adom-ds2sf
Extracts sym+footprint from the datasheet PDF.
local (uses claude + pdf tools)
adom-concur
Scores whether all libs + datasheet AGREE (now incl. Altium symbol).
uses libs altium-pcblib + altium-schlib
adom-step
Handles the 3D STEP model.
→ step2glb
adom-lbr
Side-by-side sym/fp/3D embeddable.
→ wiki
adom-chip-thumbnailer
Bakes the card thumbnails (sym/fp/3D icons).
local (OCCT + xvfb)
adom-chipsmith
Validates the 3D chip against its footprint.
→ service-kicad, step2glb
Local librariesRust crates compiled in — not separate apps
altium-pcblib lib
The Altium reader you built. Parses .PcbLib/.IntLib binary → KiCad pad JSON + SVG. 100% local, no network.
altium-schlib NEW lib
Native Altium SYMBOL reader — parses .SchLib binary → KiCad pin JSON + SVG. 100% local, validated 28/28 vs KiCad.
eagle parser lib
Inside adom-sfconvert. Parses EAGLE/Fusion .lbr XML → KiCad. 100% local.
Sourcingfind the part & its data — each has a baked-in API key in its own service
adom-parts-search
The umbrella search.
→ mouser, digikey, jlcpcb
adom-mouser
→ mouser service
adom-digikey
→ digikey service
adom-jlcpcb
→ jlcpcb service
Bridge & infrareach your laptop / the platform
adom-desktop
Bridge to your real laptop.
→ your laptop
adom-cli
Adom platform (containers, wiki, carbon).
adom-vscode
Reveal files in the editor.
▼ the heavy lifting lives OFF your container ▼
Remote service containersshared, always-on, big installs you never put on your own container
🌐 service-kicad remote
KiCad 10 (~2 GB) headless. DRC/ERC, SVG/Gerber/STEP/GLB export. (Altium import is now native — see altium-schlib.)
kicad-rk5ue5pcfemi.adom.cloud
🌐 step2glb remote
STEP → GLB 3D conversion (OCCT).
step2glb-…adom.cloud
🌐 mouser / digikey / jlcpcb remote ×3
One service each, with the vendor API key baked in — so you never need a key.
mouser-… · digikey-… · jlcpcb-…
🌐 wiki remote
Publish & install pages/skills.
wiki.adom.inc
Your laptopvia the adom-desktop bridge — not a cloud service
🖥 real Chrome laptop
Native-browser / pup automation for vendor downloads (your real logins).
🖥 KiCad / Fusion laptop
Open the finished library in your actual EDA app.
🟢 What's a “local CLI”?
A small command that's installed in your cloud container (in ~/.local/bin) and runs right there. Fast, no network, nothing big to install. Example: adom-sfconvert, adom-symbol.
These are tiny Rust binaries (a few MB). They do the orchestration, parsing, and file-shuffling.
🟠 What's a “remote service container”?
A shared, always-on container we call over HTTPS. It holds the heavy software (KiCad is ~2 GB) so it lives in one place instead of on every user's container.
When a local CLI needs KiCad, it POSTs a file to service-kicad and gets the result back. Nothing ever installs KiCad on your container.
15 apps chip-fetcher depends on
adom-sfconvert NEW · adom-symbol · adom-footprint · adom-ds2sf · adom-concur · adom-step · adom-lbr · adom-chip-thumbnailer · adom-chipsmith · adom-parts-search · adom-mouser · adom-digikey · adom-jlcpcb · adom-desktop · adom-cli (+ adom-vscode for editor reveal).
All 15 are local CLIs. Between them they reach only 6 remote services (service-kicad, step2glb, mouser, digikey, jlcpcb, wiki) and your laptop. The 2 GB KiCad never touches your container.
On Altium specifically: altium-pcblib reads Altium footprints and altium-schlib reads Altium symbols (both native/local). adom-altium is an empty stub. The other Altium pages on the wiki — adom-altium-library-importer, altium-part-importer, adom-desktop-altium-bridge (all barrett-land) — go the opposite direction: they write parts into Altium Designer on the desktop. Reading Altium symbols (.SchLib) is now native too via altium-schlib — so as of this thread nothing foreign touches service-kicad; Altium + EAGLE convert entirely in your container.