iPhone Charger Fast Charging [Apple MFi Certified] 3 Pack 20W PD Type C Wall Charger Block with 6FT USB C to Lightning Cable Cord for 14/14 Plus/14 Pro/14 Pro Max/13/12/11/X/XR/XS/8, iPad, AirPods Pro
【iPhone 14 13 12 11 Super Fast Charger】20W PD USB Type C power delivery wall plug with USB C to Lightning Cable to charge virtually any device with a Lightning port including iPhone, AirPods, iPad and Apple Watch. PD 3.0 20W USB-C charger with 6ft type c to lightning cord, charge iPhone 14 and previous iPhone models up to 3× faster than with an original 5W Charger, charging your iPhone 14 / 13 / 12 / 11 up to 50% in just 30 minutes 【Apple MFi Certified Lightning Cable】With the Apple MFi Chip, the USB-C to lightning cord equips automatic chip recognition function, full support with iOS versions and all future updates. They are of high quality, pull-resistance, ensures your devices syncs and charge simultaneously with up to 480 mb/s, also delivers up to 3A current to maximize the charging efficiency performance. The Apple MFi Certification ensures 100% flawless compatibility with Apple devices. No more trigger warning messages. 【Applicable Apple Equipment】20W USB C iPhone charger to access fast-charging for iPhone 14/ 14 plus/ 14 Pro / 14 Pro Max/ 13/ 13 Mini/ 13 Pro/ 13 Pro Max/ 12/ 12 mini/ 12 Pro/ 12 Pro Max/ SE 2020/ SE 2022/ 11/ 11 Pro/ 11 Pro Max/ XS/ XS Max/ XR/ X/ 8 Plus/ 8, iPad mini 5, iPad Air 3/ 4,iPad 8,AirPods Pro 2 /1, Power Delivery 3.0 FAST charger also charges for iPhone 7, 7 Plus, 6, 6 Plus, 6S, 6S Plus, 5, 5s, 5c, SE, iPad Pro / Mini / Air, AirPods 1/2/3 at an original charging speed.
- ASIN
- B0BY26GT6D
- Embedding
- CLIP ViT-L/14 · 768d
- Distance metric
- cosine
- Doc fetch
- 2mscache hitGET /v2/namespaces/amazon-products/documents/B0BY26GT6D
- Similar query
- 27msnearest_to_id → /query
Doc fetch goes through Layer's Aerospike pull-through cache; cache hit served the row without touching turbopuffer. The similar query asks Layer for nearest neighbors of the stored product vector — queries don't go through the doc cache, so no cache header is set.