adom-digikey

DigiKey Electronics component search for the Adom ecosystem, one Rust binary, three modes:

• CLI verbs: adom-digikey search|part|health for quick JSON-returning shell use.
• Hydrogen webview app: adom-digikey app opens a searchable UI as a first-class Hydrogen tab.
• Backend HTTP service: adom-digikey serve runs the shared proxy (port 8777) used by the service-digikey container.

Replaces the earlier Node service and MCP server. No MCP server, no Adom Viewer dependency.

Identity and access

You never need a DigiKey API key. Any vendor credential is company-owned and lives only inside Adom's service container. The CLI reaches Adom's hosted DigiKey backend automatically, with nothing to configure, and never calls the vendor directly.

What a search needs is your Adom identity, so it is attributed to a real Adom user: in an Adom container it is read automatically from /var/run/adom/api-key; elsewhere set ADOM_API_KEY to your Adom session token. An error reading "this needs your ADOM identity, not a vendor API key" means exactly that.

Quick start

# One-shot search (auto-detects backend, or falls back to direct DigiKey call)
adom-digikey search "STM32F103RBT6"

# Interactive UI
adom-digikey app

# Run the backend on the service container
DIGIKEY_CLIENT_ID=<key> adom-digikey serve

See SKILL.md for the full command reference and typical workflows.

Architecture

┌─────────────────────────────────┐          ┌─────────────────────────┐
│  any container                  │          │  service-digikey         │
│                                 │          │                         │
│  $ adom-digikey search "ESP32"   │───POST──▶│  adom-digikey serve      │
│  $ adom-digikey app              │          │    port 8777            │
│    (Hydrogen webview tab)       │          │    DIGIKEY_CLIENT_ID set   │
│                                 │          │    10-min LRU cache     │
└─────────────────────────────────┘          └─────────────────────────┘
                                                         │
                                                         ▼
                                              api.digikey.com (v2)

Consumer containers point DIGIKEY_API at the service container's public URL; locally, the CLI will also autodetect http://127.0.0.1:8777 if a backend is running on the same box.

Build

./build.sh    # cargo build --release → copy to /usr/local/bin → adom-digikey install

License

MIT.