Amazon ASIN Lookup Skill

Amazon ASIN Lookup Skill

📖 Introduction

This skill utilizes BrowserAct's Amazon ASIN Lookup API template to provide a seamless way to retrieve comprehensive product information from Amazon. By simply providing an ASIN, you can extract structured data including title, price, ratings, brand, and detailed descriptions directly into your application without manual scraping.

✨ Features

1. No Hallucinations: Pre-set workflows avoid AI generative hallucinations, ensuring stable and precise data extraction.
2. No Captcha Issues: No need to handle reCAPTCHA or other verification challenges.
3. No IP Restrictions: No need to handle regional IP restrictions or geofencing.
4. Faster Execution: Tasks execute faster compared to pure AI-driven browser automation solutions.
5. Cost-Effective: Significantly lowers data acquisition costs compared to high-token-consuming AI solutions.

🔑 API Key Setup

Before running, check the BROWSERACT_API_KEY environment variable. If not set, do not take other measures; ask and wait for the user to provide it. Agent must inform the user:

"Since you haven't configured the BrowserAct API Key, please visit the BrowserAct Console to get your Key."

🛠️ Input Parameters

The agent should configure the following parameters based on user requirements:

1. ASIN (Amazon Standard Identification Number)
   • Type: string
   • Description: The unique identifier for the Amazon product.
   • Required: Yes
   • Example: B07TS6R1SF

🚀 Usage

The agent should execute the following script to get results in one command:

# Example Usage
python -u ./scripts/amazon_asin_lookup_api.py "ASIN_VALUE"

⏳ Execution Monitoring

Since this task involves automated browser operations, it may take some time (several minutes). The script will continuously output status logs with timestamps (e.g., [14:30:05] Task Status: running). Agent Instructions:

• While waiting for the script result, keep monitoring the terminal output.
• As long as the terminal is outputting new status logs, the task is running normally; do not mistake it for a deadlock or unresponsiveness.
• Only if the status remains unchanged for a long time or the script stops outputting without returning a result should you consider triggering the retry mechanism.