aklofas/kicad-happy

mouser

Search Mouser Electronics for electronic components — secondary source for prototype orders.

Voir la source
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

Mouser Electronics Parts Search & Analysis

Related Skills

SkillPurpose
kicadSchematic analysis — extracts MPNs for part lookup
bomBOM management — orchestrates sourcing across distributors
digikeyPrimary prototype source (prefer for datasheets — direct PDF links)
spiceUses Mouser parametric data for behavioral SPICE models

Mouser is the secondary source for prototype orders — use when DigiKey is out of stock or has worse pricing. For production orders, see lcsc/jlcpcb. For BOM management and export workflows, see bom. For datasheets, prefer DigiKey's API (direct PDF links) — Mouser blocks automated PDF downloads.

API Credential Setup

Mouser uses simple API key authentication — no OAuth, no tokens, no callback URLs. The Search API key is a UUID passed as a query parameter.

Getting Your API Key

  1. Go to mouser.com → My Mouser → My Account
  2. Under "APIs" section, click "Manage"
  3. Register for Search API key — this is the one needed for part lookups and datasheet downloads
  4. Search API keys may require approval (status shows "pending authorization" initially)

Setting Credentials

Set the environment variable before running the scripts:

bash
export MOUSER_SEARCH_API_KEY=your-search-api-key-uuid

If credentials are stored in a central secrets file (e.g., ~/.config/secrets.env), load them first:

bash
export $(grep -v '^#' ~/.config/secrets.env | grep -v '^$' | xargs)

Mouser Search API Reference

All search endpoints use the Search API key as a query parameter: ?apiKey=<key>. Content-Type is application/json for all POST requests.

V1 Endpoints

Keyword Search

POST /api/v1/search/keyword?apiKey=<key>
json
{
  "SearchByKeywordRequest": {
    "keyword": "100nF 0402 ceramic capacitor",
    "records": 50,
    "startingRecord": 0,
    "searchOptions": "InStock"
  }
}
  • searchOptions: "None" | "Rohs" | "InStock" | "RohsAndInStock"
  • records: max 50 per request
  • startingRecord: offset for pagination

Part Number Search

POST /api/v1/search/partnumber?apiKey=<key>
json
{
  "SearchByPartRequest": {
    "mouserPartNumber": "GRM155R71C104KA88D|RC0402FR-0710KL",
    "partSearchOptions": "Exact"
  }
}
  • Up to 10 part numbers, pipe-separated (|)
  • Works with both Mouser part numbers AND manufacturer part numbers (MPNs)
  • partSearchOptions: "Exact" | "BeginsWith" | "Contains"

V2 Endpoints

V2 adds manufacturer filtering and pagination by page number.

Keyword + Manufacturer Search

POST /api/v2/search/keywordandmanufacturer?apiKey=<key>
json
{
  "SearchByKeywordMfrNameRequest": {
    "keyword": "LMR51450",
    "manufacturerName": "Texas Instruments",
    "records": 25,
    "pageNumber": 1,
    "searchOptions": "InStock"
  }
}

Note: the wrapper object name is SearchByKeywordMfrNameRequest (not SearchByKeywordMfrRequest — the V1 name is deprecated).

Part Number + Manufacturer Search

POST /api/v2/search/partnumberandmanufacturer?apiKey=<key>

Manufacturer List

GET /api/v2/search/manufacturerlist?apiKey=<key>

Returns the full list of manufacturer names for use in filtered searches.

V1 Deprecated Endpoints

These still work but V2 equivalents are preferred:

  • POST /api/v1/search/keywordandmanufacturer → use V2
  • POST /api/v1/search/partnumberandmanufacturer → use V2
  • GET /api/v1/search/manufacturerlist → use V2

Search Response Structure

All search endpoints return the same response format:

json
{
  "Errors": [],
  "SearchResults": {
    "NumberOfResult": 142,
    "Parts": [...]
  }
}

Key Part Fields

FieldTypeDescription
MouserPartNumberstringMouser's internal part number (prefixed, e.g., 81-GRM155R71C104KA88)
ManufacturerPartNumberstringManufacturer's part number (MPN) — use for cross-distributor matching
ManufacturerstringManufacturer name
DescriptionstringProduct description
CategorystringProduct category
DataSheetUrlstringURL to datasheet PDF (Mouser-hosted — see Datasheet section)
ProductDetailUrlstringURL to Mouser product page
ImagePathstringProduct image URL
AvailabilitystringHuman-readable stock text (e.g., "2648712 In Stock")
AvailabilityInStockstringNumeric stock quantity (as string)
AvailabilityOnOrderarrayIncoming stock: [{Quantity, Date}]
LeadTimestringFactory lead time (e.g., "84 Days")
LifecycleStatusstring\null"New Product", "End of Life", etc.
IsDiscontinuedstring"true" or "false" (string, not boolean)
SuggestedReplacementstringReplacement MPN if discontinued
MinstringMinimum order quantity (as string)
MultstringOrder multiple (as string)
ReelingboolTape-and-reel packaging available
ROHSStatusstringRoHS compliance status
PriceBreaksarrayTiered pricing: [{Quantity, Price, Currency}]
ProductAttributesarrayParametric specs: [{AttributeName, AttributeValue}]
AlternatePackagingsarray\nullAlternate packaging MPNs: [{APMfrPN}]
SurchargeMessagesarrayTariff/surcharge info: [{code, message}]
ProductCompliancearrayHTS codes, ECCN: [{ComplianceName, ComplianceValue}]
UnitWeightKgobject{UnitWeight: <float>} in kg

Quirks and Gotchas

  • Price is a string with currency symbol: "$0.10", not a float. Parse it before comparing.
  • Stock is a string: AvailabilityInStock returns "2648712" not 2648712.
  • IsDiscontinued is a string: "true" or "false", not boolean.
  • Mouser part numbers have prefixes: 81-GRM155R71C104KA88 — the prefix is Mouser-specific. Use ManufacturerPartNumber for cross-referencing.
  • V2 wrapper names differ from V1: V2 uses SearchByKeywordMfrNameRequest, not SearchByKeywordMfrRequest.
  • Tariff info: SurchargeMessages may contain US tariff percentages — useful for cost estimation.
  • On-order data: AvailabilityOnOrder shows incoming stock quantities and expected dates.

Datasheet Download & Sync

Mouser's DataSheetUrl field points to Mouser-hosted URLs (mouser.com/datasheet/...). These URLs block automated downloads — they return an HTML "Access denied" page when fetched with Python/curl/wget, even with browser User-Agent headers. The download scripts handle this with a multi-strategy approach:

  1. Try the Mouser datasheet URL directly (works for some parts)
  2. Scrape the Mouser product page HTML for alternative datasheet links
  3. Try manufacturer-specific alternative URL patterns

Note: Mouser's product pages return 403 for most automated requests, so strategy 2 has limited success. DigiKey and LCSC are more reliable datasheet sources.

Datasheet Directory Sync

Use sync_datasheets_mouser.py to maintain a datasheets/ directory alongside a KiCad project. Same workflow and manifest.json format as the DigiKey skill.

bash
# Sync datasheets for a KiCad project
python3 <skill-path>/scripts/sync_datasheets_mouser.py <file.kicad_sch>

# Preview what would be downloaded
python3 <skill-path>/scripts/sync_datasheets_mouser.py <file.kicad_sch> --dry-run

# Retry previously failed downloads
python3 <skill-path>/scripts/sync_datasheets_mouser.py <file.kicad_sch> --force

# Custom output directory
python3 <skill-path>/scripts/sync_datasheets_mouser.py <file.kicad_sch> -o ./my-datasheets

# Parallel downloads (3 workers)
python3 <skill-path>/scripts/sync_datasheets_mouser.py <file.kicad_sch> --parallel 3

# Batch mode — sync from a plain MPN list (no KiCad project required)
python3 <skill-path>/scripts/sync_datasheets_mouser.py --mpn-list mpns.txt --output ./datasheets

MPN-list batch mode (KH-312) — when you have a list of MPNs but no KiCad project to point at (harness datasheet seeding, bulk part-library seeding). One MPN per line; blank lines and # comments (full-line and inline) are skipped; generic values (100nF, DNP) are filtered via is_real_mpn() and de-duplicated. Output defaults to ./datasheets/ in the current working directory when --output is omitted.

Rate limiting — the script paces API calls with a 1.0s delay between requests by default (Mouser's Search API allows 30 calls/min on the free tier; 1.0s stays comfortably under). Override with --delay <seconds> if you have a higher-tier key or want to slow things down further.

Single Datasheet Download

Use fetch_datasheet_mouser.py for one-off downloads.

bash
# Search by MPN (uses Mouser API)
python3 <skill-path>/scripts/fetch_datasheet_mouser.py --search "TPS61023DRLR" -o datasheet.pdf

# Direct URL download
python3 <skill-path>/scripts/fetch_datasheet_mouser.py "https://example.com/datasheet.pdf" -o datasheet.pdf

# JSON output
python3 <skill-path>/scripts/fetch_datasheet_mouser.py --search "ADP1706" --json

Download Strategy

The scripts try multiple sources in order:

  1. Schematic URL — uses the datasheet URL embedded in the KiCad symbol (sync only)
  2. Mouser API search — gets the DataSheetUrl from the API response
  3. Alternative manufacturer sources — tries known URL patterns for major manufacturers (TI, Microchip, etc.) when the Mouser URL is blocked
  4. Headless browser fallback — if playwright is installed, uses headless Chromium as a last resort

When all methods fail, provide the ProductDetailUrl to the user so they can download from the Mouser product page in their browser.

Web Search Fallback

If no API key is available, search Mouser by fetching product pages directly:

  • Search URL: https://www.mouser.com/c/?q=<query>
  • Product pages contain full specs, pricing tiers, stock, datasheets
  • Results from Mouser can be noisy (JS-heavy pages)

Include key parameters in the query:

  • Passives: value, package (0402/0603/0805), tolerance, voltage/power rating, dielectric (C0G/X7R)
  • ICs: part number or function, package (QFN/SOIC/TSSOP), key specs (voltage, current, interface)
  • Connectors: type (USB-C, JST-PH), pin count, pitch, mounting (SMD/THT), orientation

Tips

  • Pipe-separate up to 10 part numbers in a single PartNumber search for batch lookups
  • Min and Mult fields matter — some parts have minimum order qty or must be ordered in multiples
  • SurchargeMessages may include US tariff percentages — factor into cost estimates
  • AvailabilityOnOrder shows incoming stock with expected dates
  • Check IsDiscontinued and LifecycleStatus before selecting parts
du même dépôt

Autres Skills

Tous les Skills
aklofas
Communauté

datasheets

Extract structured specifications from electronic component datasheet PDFs — pinouts, electrical characteristics, peripherals, topology, and features. Cache extractions per project for consumption by schematic and PCB analyzers. Primary consumer infrastructure for kicad, emc, spice, and thermal analyzers. Use this skill whenever the user asks to extract, verify, or read specs from a component datasheet; when analyzers need verified IC knowledge (EN pin thresholds, PG presence, USB peripheral speed); or when a review mentions datasheet coverage, extraction quality, or per-MPN specifications. Also triggers on "extract this datasheet", "what are the specs for MPN X", "verify datasheet extraction", or "check pin functions for part Y".

installations
2
GitHub Stars
1,3 k
Mis à jour
13 sept.
aklofas
Communauté

emc

- EMC pre-compliance risk analysis for KiCad PCB designs — 18 check categories, 44 rule IDs covering ground planes, decoupling, I/O filtering, switching harmonics, clock routing, differential pair skew, board edge radiation, PDN impedance, return paths, crosstalk, ESD protection, shielding, and magnetic leakage from switching inductors. Produces severity-ranked risk report with pre-compliance test plan. Supports FCC Part 15, CISPR 32, CISPR 25 (automotive), MIL-STD-461G. SPICE-enhanced when available. Use when the user asks about EMC, EMI, radiated/conducted emissions, FCC compliance, CE marking, CISPR, ground plane issues, decoupling strategy, clock routing EMC, switching noise, differential pair skew, or whether their board will pass EMC testing. Also for "will this pass FCC?", "check my EMC", "is my ground plane okay?", "check my decoupling", or "generate an EMC test plan".

installations
2
GitHub Stars
1,3 k
Mis à jour
13 sept.
aklofas
Communauté

bom

BOM (Bill of Materials) management for electronics projects — the workflow skill that coordinates DigiKey, Mouser, LCSC, element14, JLCPCB, PCBWay, and KiCad skills around a unified BOM lifecycle. Create, update, and maintain BOMs with part numbers, costs, quantities stored as KiCad symbol properties. ALWAYS trigger this skill for any task involving component sourcing, pricing, ordering, distributor searches, BOM export, or fabrication preparation — even if the user names a specific distributor or fab house (e.g. "search DigiKey for...", "generate JLCPCB BOM", "order from Mouser"). This skill analyzes the schematic for sourcing gaps, recommends which distributor/fab skills to call for each gap, and writes results back as symbol properties — the agent (or user) performs the actual searches via the called skills. Also trigger on phrases like "what parts do I need", "order components", "how much will this cost", "export for JLCPCB", "find parts for this board", "compare pricing", or "check stock".

installations
2
GitHub Stars
1,2 k
Mis à jour
13 sept.
aklofas
Communauté

element14

Search Newark, Farnell, and element14 for electronic components — find parts by MPN or distributor part number, check pricing/stock, download datasheets, analyze specifications. One unified API covers all three storefronts (Newark for US, Farnell for UK/EU, element14 for APAC). Free API key, simple query-parameter auth, no OAuth. Datasheets download directly from farnell.com CDN with no bot protection. Sync and maintain a local datasheets directory for a KiCad project, or use batch MPN-list seeding (--mpn-list) for bulk workflows without a project. Use this skill when the user mentions Newark, Farnell, element14, needs parts from a non-US distributor, wants to compare pricing across regions, or needs datasheets from a source that doesn't require complex API auth. For package cross-reference tables and BOM workflow, see the bom skill.

installations
2
GitHub Stars
1,2 k
Mis à jour
13 sept.