# AI use cases for Coreclaw API Directory (cporter202/coreclaw-api-directory) Repo: [cporter202/coreclaw-api-directory](https://github.com/cporter202/coreclaw-api-directory) | Use cases: 4 | Page: https://dedupedai.com/use-cases/cporter202-coreclaw-api-directory/ A community-maintained directory of 118 public CoreClaw Workers, which are runnable web-data workflows for scraping and collecting structured data from public websites. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Build a local business lead list from Google Maps: https://dedupedai.com/use-cases/cporter202-coreclaw-api-directory/build-local-business-leads-from-google-maps/ - Track Amazon product data for a list of ASINs: https://dedupedai.com/use-cases/cporter202-coreclaw-api-directory/track-amazon-product-data-by-asin/ - Pull Google organic results and People Also Ask for SEO: https://dedupedai.com/use-cases/cporter202-coreclaw-api-directory/pull-google-serp-results-for-seo-tracking/ - Enrich company records from LinkedIn company URLs: https://dedupedai.com/use-cases/cporter202-coreclaw-api-directory/enrich-company-records-from-linkedin-urls/ ## How to build a local business lead list from Google Maps with Coreclaw API Directory Repo: [cporter202/coreclaw-api-directory](https://github.com/cporter202/coreclaw-api-directory) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Run the Google Maps Worker to collect local businesses with reviews, contacts and hours. **Who it is for:** A sales rep or local marketer who needs a prospect list for a city or niche and has no time to copy listings by hand. **The problem:** Finding and copying business details from maps one listing at a time is slow and error-prone. **The outcome:** A structured set of local businesses with reviews, contact details and opening hours, ready for a CRM or spreadsheet. ### Steps 1. Get a CoreClaw API key and keep it private. 2. Read the input schema for coreclaw/google-maps-scraper, since the README says required fields differ between Workers. 3. Replace the empty input object with your search fields and run a small test: `curl -X POST "https://openapi.coreclaw.com/api/v2/workers/coreclaw~google-maps-scraper/runs" -H "Authorization: Bearer YOUR_API_KEY" -H "Content-Type: application/json" -d '{"input": {}, "is_async": true}'` (inferred, check the README) 4. Check that the output includes the contact details and opening hours you need. 5. Scale the input to your full target area once the test output looks right. ### Prompt to paste into your agent ```text Using the repo cporter202/coreclaw-api-directory, run the coreclaw~google-maps-scraper Worker for and return the businesses with names, reviews, contact details and opening hours as structured output. Verify the run returned at least one structured result before you report completion. ``` ### Caveat The directory describes the Worker output but the README does not list field names, so confirm the exact fields in a test run before building on them. Risk, credentials: Keep the Bearer API key out of shared scripts, screenshots and public repositories because anyone with it can run Workers on your account. Risk, reverse engineering: Business contact details collected from maps should be used in line with the laws and platform rules that apply to your outreach. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/cporter202-coreclaw-api-directory/build-local-business-leads-from-google-maps/ ## How to track Amazon product data for a list of ASINs with Coreclaw API Directory Repo: [cporter202/coreclaw-api-directory](https://github.com/cporter202/coreclaw-api-directory) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Run the ASIN-based Amazon Worker to pull prices, reviews, rankings and seller data. **Who it is for:** An e-commerce seller or analyst who monitors a fixed set of competitor or own products by ASIN. **The problem:** Checking prices, reviews and rankings for many ASINs by hand takes hours and gets out of date fast. **The outcome:** Structured product records for each ASIN with title, brand, price, reviews, seller information and ranking. ### Steps 1. Get a CoreClaw API key and keep it private. 2. Open the Worker page for coreclaw/amazon-product-data-scraper-api and read its input schema for the ASIN field. 3. Run a test with one ASIN: `curl -X POST "https://openapi.coreclaw.com/api/v2/workers/coreclaw~amazon-product-data-scraper-api/runs" -H "Authorization: Bearer YOUR_API_KEY" -H "Content-Type: application/json" -d '{"input": {}, "is_async": true}'` (inferred, check the README) 4. Add your ASIN list to the input as the schema requires and run the batch. 5. Export the results or send them to your own tool, as the Worker description states is possible. ### Prompt to paste into your agent ```text Using the repo cporter202/coreclaw-api-directory, run the coreclaw~amazon-product-data-scraper-api Worker for the ASINs and return title, brand, price, reviews, seller information and ranking for each one. Verify that every ASIN you sent has a matching record in the output before you report completion. ``` ### Caveat The README does not say how often data refreshes or how scheduled runs work, so set your own schedule and check the output timing yourself. Risk, credentials: Store the CoreClaw API key in an environment variable or secret manager rather than hard-coding it into a price tracker. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/cporter202-coreclaw-api-directory/track-amazon-product-data-by-asin/ ## How to pull Google organic results and People Also Ask for SEO with Coreclaw API Directory Repo: [cporter202/coreclaw-api-directory](https://github.com/cporter202/coreclaw-api-directory) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Run the Google Search Worker to collect organic results, related searches and PAA questions. **Who it is for:** An SEO analyst or content lead who tracks how search results and related questions change for target keywords. **The problem:** Recording search result pages by hand for many keywords is slow and hard to repeat. **The outcome:** Structured organic results, related searches and People Also Ask entries for each keyword. ### Steps 1. Get a CoreClaw API key and keep it private. 2. Read the input schema for coreclaw/google-search-scraper to find the keyword and location fields. 3. Run a test with one keyword: `curl -X POST "https://openapi.coreclaw.com/api/v2/workers/coreclaw~google-search-scraper/runs" -H "Authorization: Bearer YOUR_API_KEY" -H "Content-Type: application/json" -d '{"input": {}, "is_async": true}'` (inferred, check the README) 4. Confirm the output includes organic results, related searches and People Also Ask entries. 5. Repeat the run for your keyword list and store the results by date. ### Prompt to paste into your agent ```text Using the repo cporter202/coreclaw-api-directory, run the coreclaw~google-search-scraper Worker for the keyword and return the organic results, related searches and People Also Ask entries as structured output. Verify that the output contains organic results before you report completion. ``` ### Caveat The README lists the Worker outputs but does not state result limits or how many keywords you can run, so check the input schema before running large batches. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/cporter202-coreclaw-api-directory/pull-google-serp-results-for-seo-tracking/ ## How to enrich company records from LinkedIn company URLs with Coreclaw API Directory Repo: [cporter202/coreclaw-api-directory](https://github.com/cporter202/coreclaw-api-directory) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Run the LinkedIn company Worker to add industry, description and size to a company list. **Who it is for:** A sales or research analyst with a list of target company URLs who needs basic firmographic fields filled in. **The problem:** Looking up each company profile to copy its industry, description and size is manual and slow. **The outcome:** Company records with profile details, industries, descriptions and organization size. ### Steps 1. Get a CoreClaw API key and keep it private. 2. Read the input schema for coreclaw/linkedin-company-scraper to confirm it takes company profile URLs. 3. Run a test with one company URL: `curl -X POST "https://openapi.coreclaw.com/api/v2/workers/coreclaw~linkedin-company-scraper/runs" -H "Authorization: Bearer YOUR_API_KEY" -H "Content-Type: application/json" -d '{"input": {}, "is_async": true}'` (inferred, check the README) 4. Add your company URLs to the input as the schema requires and run the batch. 5. Merge the returned industry, description and size fields into your CRM or spreadsheet. ### Prompt to paste into your agent ```text Using the repo cporter202/coreclaw-api-directory, run the coreclaw~linkedin-company-scraper Worker on the company URLs and return the profile, industry, description and organization size for each one. Verify that each URL returned a record before you report completion. ``` ### Caveat The README gives the company fields but does not say how complete each record will be, so check for blank fields in your first test batch. Risk, credentials: Keep the CoreClaw API key out of shared spreadsheets and scripts that other team members can open. Dual-use notice: only use this on software, sites and systems you own or are authorized to test. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/cporter202-coreclaw-api-directory/enrich-company-records-from-linkedin-urls/