Investigate USB-A Bolt for a verified compatible input device
Choose the physical connection after confirming Bolt support and the current device-specific pairing instructions. Keep direct Bluetooth if it already meets the requirement.
Skip it if: The device is Unifying-only, already has a suitable receiver in its actual package, or the host/pairing route is unresolved.
Keep the working connection before adding an accessory
A receiver is worth investigating for a specific connection need, not simply because a keyboard or mouse can support one. If direct Bluetooth already works with the intended computer and is permitted for that use, record what a new receiver would actually change before buying it.
This guide concerns adding the correct accessory to compatible equipment. It is separate from replacing a keyboard or deciding how to switch an entire two-computer setup. We have not measured latency, range, reliability or performance before sign-in, so those are not reasons to pay more based on this article.
Check three different parts
1 · PERIPHERALCorrect protocol
Verify the exact device’s Bolt support. A connector adapter does not turn Unifying into Bolt.
2 · HOST PATHCorrect connector
Match USB-A or USB-C to the supported computer and any intended hub path.
3 · INITIAL SETUPPermitted pairing
Read the exact receiver instructions before assuming a browser or software route is available.
Original decision diagram. Keep direct Bluetooth when it already meets the requirement.
Check the protocol before the shape of the plug
Logitech’s documentation distinguishes Logi Bolt from Unifying: their devices and receivers are not cross-compatible. The Bolt logo on the intended peripheral and receiver is a documented compatibility check. Verify the exact model instead of assuming that a shared brand name means any receiver will work.
A USB-A-to-USB-C adapter changes the physical connector; it does not convert Unifying into Bolt. Likewise, the older K380 and Pebble Keys 2 K380s are different model names. Use the exact device label and its own connection documentation when filling out the plan.
Check whether the actual package already supplies a receiver
Use the exact standalone or bundle listing. Regular consumer, business, Combo and Mac-oriented packages can differ. The examples below are bounded to the specific primary sources, rather than a promise about every package sold under a similar name.
Receiver-inclusion checks for the named standalone examples
Existing device
What the cited source establishes
What to verify on the listing
Pebble Keys 2 K380s
Optional Bolt; named Combo inclusion differs
Standalone versus exact Pebble 2 Combo
MX Keys Mini US 920-010475
Regular package lists keyboard, charging cable and documents
Exact market and bundle; do not assume a receiver
Pebble Mouse 2 M350s
Standalone specification says receiver not included
Exact model and any combined package
MX Anywhere 3S, regular US consumer
Product page says receiver not included
Consumer versus business/Mac/package variants
Choose the connector and the initial-pairing route together
The current US receiver page lists USB-A part 956-000007 and USB-C part 956-000156. Those are US variant identifiers, not a statement that every market or retailer bundle uses the same part. Match the exact variant to a verified host connection and the package you intend to buy.
For a separately purchased USB-C receiver, Logitech requires initial pairing using Options+ on Windows/macOS. Basic use after pairing on other supported systems is a different question. Confirm that setup before purchase; do not transfer older USB-A Web Connect instructions to this variant.
For USB-A, follow the current device-specific instructions. The K380s setup guide describes Options+ or Logi Web Connect for that USB-A route. Check the supported host/browser and any work-computer software restrictions before choosing the receiver. A blocked initial-pairing step is a reason to resolve the plan first.
Count active devices separately from stored pairings
The USB-C documentation lists six paired devices and three simultaneous active connections. Record the active inputs you need, rather than treating stored pairings as active capacity.
Also record which computer will hold the receiver. A receiver in a USB hub or sharing-switch plan still needs that complete path to be supported. Native keyboard device switching, receiver pairing and switching a shared USB connection are different actions; one does not automatically coordinate the others.
Do not buy a charging cable as a substitute for the data plan
The MX Keys Mini specification describes a wireless keyboard and identifies the supplied cable as charging. That cable label does not establish a wired typing route. Keep the supported Bluetooth or receiver connection in the inventory while planning how the keyboard is powered.
Apply the same discipline to the rest of the desk: identify the documented data connection for each device and the power connection separately. A socket or cable that powers equipment is not, by itself, evidence that it carries the input connection you need.
Make a four-line receiver inventory
Before ordering, record four things: the exact compatible peripheral, the actual package contents, the available host connector, and the permitted initial-pairing method. Add the active-device count if several inputs will use the receiver. Resolve any blank entry before treating the receiver as the missing part.
Keep Bluetooth when it already handles the job. Investigate USB-A Bolt when the device and its documented USB-A setup route pass. Investigate the separately sold USB-C variant when its initial-pairing requirement and host path pass. Check the current retailer listing and manufacturer instructions; no receiver choice here is an independent reliability or security certification.
Evidence and limits
This is a specification-based buying guide. Product descriptions come from the sources below; the fit examples and decision rules are our editorial analysis. We have not measured durability, performance, or comfort in a product test.
Logitech US Logi Bolt receiver specifications ↗Current rendered US drawer lists USB-A 956-000007 and USB-C 956-000156 variants. Part numbers differ by market; do not copy a UK SKU into the US recommendation.
Logitech USB-C receiver whitepaper ↗USB-C pairing requirements, Bolt logo check, and six-paired versus three-active connection distinction (printed pp. 5, 10–11).
K380s getting-started and receiver instructions ↗Documents Bluetooth/optional Bolt, a separately purchased receiver except for the named Combo, and USB-A pairing instructions using Options+ or Logi Web Connect. An apparent M380s typo is not repeated here.
Bolt and Unifying compatibility FAQ ↗Logi Bolt and Unifying devices/receivers are not cross-compatible. A connector adapter does not change the receiver protocol.
MX Keys Mini regular US package ↗The rendered US In the Box panel lists keyboard, charging cable and documentation without a receiver; do not extend this to business or other bundles.
As an Amazon Associate I earn from qualifying purchases. Amazon links open a model listing or product search. Confirm the variant, seller, price and availability there. Disclosure.
Logi Bolt USB-A Receiver (US 956-000007)
A Logi Bolt receiver variant for a compatible input device and a verified USB-A host route.
Check the fit: Verify the peripheral’s Bolt support, exact package and current pairing instructions. Unifying is a different protocol; keep Bluetooth if it already meets the need.
A USB-C Logi Bolt receiver variant whose standalone initial-pairing requirement needs to fit the intended setup.
Check the fit: The separately purchased USB-C receiver requires initial Options+ pairing on Windows/macOS. Six paired devices does not mean six active; the whitepaper lists three simultaneous active connections.