mouser

Files (3)

• SKILL.md
• fetch_datasheet_mouser.py · scripts/
• sync_datasheets_mouser.py · scripts/

SKILL.md (first lines)

# Mouser Electronics Parts Search & Analysis

## Related Skills

| Skill | Purpose |
|-------|---------|
| `kicad` | Schematic analysis — extracts MPNs for part lookup |
| `bom` | BOM management — orchestrates sourcing across distributors |
| `digikey` | Primary prototype source (prefer for datasheets — direct PDF links) |
| `spice` | Uses 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](https://www.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:

From aklofas/kicad-happy, MIT.

More from aklofas/kicad-happy