lcsc

Files (5)

• SKILL.md
• fetch_datasheet_lcsc.py · scripts/
• search_lcsc.py · scripts/
• sync_datasheets_lcsc.py · scripts/
• test_search_lcsc.py · scripts/

SKILL.md (first lines)

# LCSC Electronics — Component Search, Datasheets & Ordering

## Related Skills

| Skill | Purpose |
|-------|---------|
| `kicad` | Schematic analysis — extracts MPNs for part lookup |
| `bom` | BOM management — orchestrates sourcing across distributors |
| `jlcpcb` | PCB assembly — shares the same parts library |
| `spice` | Uses LCSC parametric data for behavioral SPICE models (no auth needed) |

LCSC is JLCPCB's sister company — they share the same parts library and `Cxxxxx` part numbers. Use LCSC for **production sourcing** (assembled boards from JLCPCB/PCBWay). DigiKey/Mouser are for prototyping. For BOM management and export workflows, see `bom`.

## Key Differences from DigiKey/Mouser

- **No API key needed** — jlcsearch community API is free and open
- **Lower prices** — especially for passives and Chinese-manufactured ICs
- **JLCPCB integration** — same LCSC part numbers used in JLCPCB assembly BOMs
- **Direct PDF downloads** — LCSC's CDN (wmsc.lcsc.com) serves datasheets without bot protection
- **Low MOQ** — many parts available in quantities as low as 1
- **Warehouses** — Shenzhen (JS), Zhuhai (ZH), Hong Kong (HK)
- **Website**: `https://www.lcsc.com`

## LCSC Part Numbers

Format: `Cxxxxx` (e.g., `C14663`). This is the universal identifier across both LCSC and JLCPCB. Use it for:
- Direct ordering on LCSC
- BOM matching in JLCPCB assembly (see `jlcpcb` skill)
- Cross-referencing between platforms

## Component Search

Use `search_lcsc.py` to search LCSC and JLCPCB for electronic components, check live stock, inspect pricing tiers, identify basic vs. extended parts, and fetch parametric attributes. **No API key required.**

```bash
# Search by keyword or description
python3 <skill-path>/scripts/search_lcsc.py "tactile switch"

# Search for basic parts only (no JLCPCB extended loading fees)
python3 <skill-path>/scripts/search_lcsc.py "0805 100R" --basic

# Filter by package/footprint and stock
python3 <skill-path>/scripts/search_lcsc.py "red led" --package 0805 --in-stock

# Inspect full component details (manufacturer, datasheet URL, price breaks, parametric attributes)
python3 <skill-path>/scripts/search_lcsc.py "C318884" --details

# Output machine-readable JSON (for scripts and agent workflows)
python3 <skill-path>/scripts/search_lcsc.py "ME2108" --limit 5 --json

# Sort results by price or stock
python3 <skill-path>/scripts/search_lcsc.py "microcontroller STM32" --sort price

# Parametric category search (rows carry package, stock, price and attributes)
python3 <skill-path>/scripts/search_lcsc.py "STM32" --category microcontrollers
```

The script:
- Queries the free `jlcsearch` community API for the search, then enriches from LCSC's direct product-detail endpoint (manufacturer, datasheet URL, price breaks) for exact `Cxxxxx` queries and for every hit shown with `--details` — one extra request per hit, 0.5s apart. If jlcsearch has no row for a `Cxxxxx` code, the direct lookup is the fallback.
- Formats results into a clean terminal table highlighting `LCSC #`, `MPN`, `Package`, `Basic/Ext` status, `Stock`, `Price`, and `Description`
- Supports `--basic` filtering to optimize PCB assembly BOM costs for JLCPCB manufacturing
- Supports `--json` for automated BOM enrichment and agent workflows

## jlcsearch API Reference

The jlcsearch community API is the recommended way to search LCSC. **No authentication required.**

**Base URL:** `https://jlcsearch.tscircuit.com`

### General Search

```
GET /api/search?q=<query>&limit=20&full=true
```

Parameters:
- `q` — search query (matches MPN, LCSC code, or description keywords)
- `package` — optional footprint filter (e.g., `0402`)
- `limit` — max results (default 100)
- `full` — accepted but no longer adds fields (the former `extra` block is gone, see below)

### Category-Specific Search

```
GET /resistors/list.json?search=10k+0402
GET /capacitors/list.json?search=100nF+0402
GET /microcontrollers/list.json?search=STM32
GET /voltage_regulators/list.json?search=3.3V
```

### Response Format

General search returns `{"components": [...]}`. As of 2026-09 each hit carries only these fields — the `extra` block (manufacturer, datasheet URL, per-warehouse stock, attributes, price breaks) is no longer returned, even with `full=true`:

```json
{
  "lcsc": 318884,
  "mfr": "TS-1187A-B-A-B",
  "package": "SMD-4P,5.1x5.1mm",
  "is_basic": true,
  "is_preferred": false,
  "description": "-30℃~+85℃ 1.5mm 1.6N ... SMD-4P,5.1x5.1mm Tactile Switches ROHS",
  "stock": 1683297,
  "price": 0.0197
}
```

Key fields:
- `lcsc` — numeric LCSC ID (without "C" prefix); prepend `C` for the LCSC code
- `mfr` — manufacturer part number (no manufacturer name)
- `is_basic` — `true` if JLCPCB basic part (no setup fee); `is_preferred` — JLCPCB preferred extended part
- `stock` / `price` — JLCPCB assembly stock and unit price (USD)

Category endpoints return `{"<category>": [...]}` — keyed by the category name, **not** `components`. Rows differ from the general search: `price1` instead of `price`, `in_stock`, an empty `description`, parametric columns (e.g. `resistance`, `cpu_core`), and `attributes` as a JSON **string**:

```json
{"resistors": [{"lcsc": 25804, "mfr": "0603WAF1002T5E", "description": "", "stock": 37165617,
  "price1": 0.000842857, "in_stock": true, "package": "0603", "resistance": 10000,
  "is_basic": true, "is_preferred": false,

From aklofas/kicad-happy, MIT.

More from aklofas/kicad-happy