Give dealer website URLs, get the vehicles each dealer currently lists for sale on its own website, one row per vehicle (VIN, year, make, model, trim, price, mileage, specs, dealer location, link) plus one status row per dealer. Covers franchise and independent car dealers on 21 website platforms, RV dealers on Interact RV, Inventrue and Coast Technology, truck dealers on iManPro, the DriveTime, Camping World, Rush, SelecTrucks, Ryder, Velocity and TEC chains, and other sites that publish standard schema.org vehicle data. Data comes from the dealers' own public websites; this app is not an official product of any dealer or website provider
Lowe's Keyword Search
Give a Lowe's search keyword, expected count, and sort to get public product search listings with title, brand, category, rating, and product links.
Original · en-USZur Übersetzung
Übersicht
Retail and brand teams that watch Lowe's usually make assortment and share-of-search calls from the same product card a shopper sees: title, brand, category, rating, review count, and the product page. This app turns one public Lowe's search keyword into a structured table of those listings so category reviews, competitor scans, and catalog matching can start from storefront search instead of a one-off screenshot.
Each row keeps the Search keyword beside the SKU ID, SPU ID, Model ID, and Product URL, so later comparisons stay attached to the query that produced them. Rating and Review count stay in the source text, and Product status is kept as the original listing label. It is a search-listing workbook, not a substitute for a full product detail page, inventory position, or variant matrix.
Data notes
Each row is one public Lowe's keyword search listing for the submitted Search keyword and Sort order. The same SKU ID is kept once in the returned set. Listings are returned in collection order. Product status is the source label as shown on the card, including values such as 在售. Rating and Review count remain source text rather than normalized numbers. Collected at is returned without a timezone; Source created time is a Unix millisecond timestamp when present. Alternate image, Item number, and Source collect time may be empty on a listing card. Search keyword, Business ID, and Task keyword repeat the search context across rows from the same query. A No-data flag distinguishes a search that produced no listings from ordinary product rows.
The collection does not cover private seller tools, warehouse inventory, fulfillment data, or product-detail fields that are not visible on public Lowe's search.
What a result looks like
Each row is one Lowe's search listing.
| Product title | SKU ID | Brand | Rating | Product URL | Search keyword |
|---|---|---|---|---|---|
| HP3600Plus+500X 3600 -Watts Portable Power Station (1 Solar Panel Included) | 5017225957 | Jackery | 0 | https://www.lowes.com/pd/Jackery-Jackery-Solar-Generator-3600-Plus-with-1-Solar-Panel-500W/5017225957 | Jackery |
| SolarSaga 200W 91.3-in x 21.2-in x 1-in 200-Watt Portable Solar Panel | 5015759393 | Jackery | 4.7 | https://www.lowes.com/pd/Jackery-Solar-Panels-200W/5015759393 | Jackery |
Category, Review count, and Product image are also available when the card shows them.
Use cases
- For assortment scans, group rows by Search keyword and Brand, then read Product title and Category to see which products occupy the first results for that query.
- For reputation checks, compare Rating and Review count to separate well-reviewed SKUs from unrated or thinly reviewed cards.
- For catalog matching, join SKU ID, SPU ID, Model ID, and Product URL to an internal product list and keep the Product image for visual QA.
Anwendungsbereich & Grenzen
One keyword search per task with an expected result count from 1 to 240; results are returned in complete batches of 24 and may be rounded up; coverage is limited to public Lowe's keyword search listings.
- Geeignet für
- When you need public Lowe's product search listings for one keyword and sort order.
- When you need to compare product titles, brands, categories, ratings, review counts, and product links from search cards.
- Nicht verwenden für
- When you need a full product detail page, inventory, fulfillment, or variant matrix beyond the search card.
- When you need an immediate single-record lookup rather than a background keyword collection task.
Fehlerbehandlung
Vom Entwickler deklariertes Fehler- und Wiederholungsverhalten. Wir empfehlen, es bei der Integration in Ihren System-Prompt aufzunehmen.
- 1If no products are returned, confirm the keyword can be searched on public Lowe's, then retry with a broader brand or product phrase.
- 2Keep completed records after a partial success; resubmit the same input after a failed or expired task.
- 3Retry later after rate limiting, temporary unavailability, or a timeout.
- 4If authentication fails, verify the API Key configured for the execution environment.
Eingabe
Parameter, die zum Aufruf dieser App erforderlich sind, generiert aus dem input.schema in der manifest.json.
- Search keyword
keywordErforderlichstringProduct, brand, or phrase to search on Lowe's. Each task accepts one keyword from 1 to 512 characters.BeispielJackery - Expected result count
expected_countErforderlichintegerExpected number of product listings from 1 to 240; results come back in complete batches of 24, so the actual count may be rounded up and a partial batch is still billed as 24 listings.Bereich1–240Beispiel1 - Sort order
sort_orderOptionalstring(enum)How Lowe's should rank the search listings. Default is Default; choose Best selling, a price order, Most popular, or Highest rated when you need a different ranking.Zulässige WerteDefault0Best selling2Price: low to high51Price: high to low52Most popular6Highest rated11Standard0
Ausgabe
Feldstruktur eines einzelnen Datensatzes, generiert aus dem output.schema in der manifest.json.
- Alternate image
alternate_image_urlstringBackup product image URL from the search card; empty when the source does not return one.Beispielhttps://mobileimages.lowes.com/productimages/3c276865-0b5a-4a89-b625-8f995c1382bd/73741189.jpeg - Business ID
biz_idstringBusiness identifier attached to the search record; in the current shape this repeats the search keyword.BeispielJackery - Brand
brand_namestringProduct brand name shown on the Lowe's search card; empty when the source does not return one.BeispielJackery - Category ID
category_idstringLowe's category identifier for the listing; empty when the source does not return one.Beispiel107784
Beispieldaten
Aus output.schema erzeugt. Felder ohne Beispielwert verwenden strukturelle Platzhalter.
{
"alternate_image_url": "https://mobileimages.lowes.com/productimages/3c276865-0b5a-4a89-b625-8f995c1382bd/73741189.jpeg",
"biz_id": "Jackery",
"brand_name": "Jackery",
"category_id": "107784",
"category_name": "SOLAR_GENERATORS",
"crawl_time": "2026-09-11T19:08:13",
"image_url": "https://mobileimages.lowes.com/productimages/26fcd8db-042f-4987-91c3-07b4477fafb7/73741094.jpeg",
"item_number": "<item_number>",
"keyword": "Jackery",
"model_id": "60-360050-US00073",
"product_title": "HP3600Plus+500X 3600 -Watts Portable Power Station (1 Solar Panel Included)",
"product_url": "https://www.lowes.com/pd/Jackery-Jackery-Solar-Generator-3600-Plus-with-1-Solar-Panel-500W/5017225957",
"rating_score": "0",
"review_count": "0",
"sku_id": "5017225957",
"source_collect_time_ms": 0,
"source_created_at_ms": 1789124892867,
"spu_id": "5017225957",
"status_code": "在售",
"task_item": "Jackery",
"no_data": false,
"vendor_number": "110974"
}Integration
Diese App kann über MCP, API, SDK oder Dateiexport integriert werden — alle Kanäle teilen sich dieselben Fähigkeiten und Preise. Jede Anfrage authentifiziert sich über den Authorization: Bearer-Header mit einem API Key (langlebig, in der Data Hub Konsole erstellt); MCP-Clients können sich zusätzlich per OAuth ohne Key anmelden. Weitere Optionen wie CLI und Skill sind in Vorbereitung. Diese App läuft asynchron und kann zwischendurch abgebrochen werden: Nach dem Abbruch stoppt der Lauf. Bereits gelieferte Datensätze bleiben erhalten und werden abgerechnet.
Über das MCP (Model Context Protocol) können Sie diese App direkt aus KI-Clients wie Claude und Cursor aufrufen. Wählen Sie Ihren Client und den Authentifizierungsmodus und kopieren Sie dann die Konfiguration unten.
Client-Konfiguration
Ersetzen Sie den Wert nach Bearer durch Ihren langlebigen API Key. Funktioniert in jedem Client, in CI und in Headless-Umgebungen.
{
"mcpServers": {
"octoparse_datahub": {
"type": "http",
"url": "https://mcp-v2.octoparse.com?pin=hello_moto/lowes-keyword-search",
"headers": { "Authorization": "Bearer <YOUR_API_KEY>" }
}
}
}Lassen Sie die KI die Einrichtung übernehmen
Sie möchten Konfigurationen nicht von Hand bearbeiten? Kopieren Sie den Installations-Prompt und fügen Sie ihn in einen beliebigen KI-Client ein — er schließt die Einrichtung auf seine eigene Weise ab. (Standardmäßig führt er Sie durch die Anmeldung und fordert Sie nie auf, Ihren API Key im Chat zu senden.)
detail.access.mcp.composeHint
Preise
Berechnet nach der Anzahl der erfolgreich zurückgegebenen Datensätze. Fehlgeschlagene Läufe werden nicht berechnet. Abgerechnet in Einheiten von 24 Datensätze; jede angefangene Einheit wird auf 24 Datensätze aufgerundet.
Wird pro übermitteltem Lauf einmal berechnet, unabhängig davon, wie viele Datensätze zurückgegeben werden.
Mehrere Abrechnungsereignisse werden unabhängig voneinander kumuliert. Details siehe jeweilige Position. Fehlgeschlagene Läufe werden nicht berechnet.
Credits ansehenJetzt ausprobieren
Füllen Sie die Parameter aus und starten Sie — die Ergebnisse stammen aus einem echten Aufruf.