Chrome Web Store Extension Scraper

Export public Chrome extension metadata to CSV or JSON for inventories, vendor review and market research. Supply extension IDs or detail URLs; no browser installation, login or API key is required.

For AI agents and MCP clients

Tool description: Agent tool: given Chrome Web Store extension IDs or URLs, returns one metadata row per extension (name, developer, users, rating, version, last updated, category).

Output fields (dataset rows): extensionId, name, description, users, rating, ratingCount, version, updated, category, developer, icon, url

Use cases:

• Monitor a shortlist of browser extensions for an AI agent: re-run weekly and flag version, rating or user-count changes (about $0.002 per extension).
• Feed vendor-risk review to an MCP client: pull developer, privacy policy URL and last-updated date for every extension an employee installs.
• Competitor tracking: snapshot users and ratings of 50 rival extensions for about $0.10.

Pay-per-event price table (USD; platform compute billed separately by Apify):

Event	Charged per	FREE plan	DIAMOND plan
extension	Extension scraped	$0.002	$0.001

Set maxTotalChargeUsd on the run to cap spend.

Try one listing

{
  "extensions": ["aapbdbdomjkkjkaonfhkkikfgjllcleb"]
}

This example uses Google Translate. It replaces the previous uBlock Origin example, which returned a generic Store page rather than usable listing metadata during verification. The one-listing example has a maximum Actor event charge of US$0.002 at the FREE-tier list price. Apify platform charges are separate; paid-tier event prices may be lower.

Real output preview

Selected fields from the public Google Translate listing captured on September 9, 2026:

{
  "extensionId": "aapbdbdomjkkjkaonfhkkikfgjllcleb",
  "name": "Google Translate",
  "users": 35000000,
  "rating": 4.2,
  "version": "2.0.17",
  "updated": "July 2, 2026",
  "category": "productivity"
}

These are observations, not fixed expected values: listings and ratings can change. Source fields that are unavailable in recognized markup remain null.

Inputs

Field	Required	Accepted format	Behavior
extensions	Yes	Non-empty array of 32-letter IDs (a–p) or Chrome Web Store detail URLs containing an ID	Console prefill is the Google Translate ID above. IDs are processed sequentially. There is no schema list-length cap; keep your first run small. Duplicate IDs are not automatically removed.

Missing or empty input is rejected. Invalid IDs and unavailable listings produce no result rows. If no usable extension metadata is found, the run fails clearly rather than returning a successful empty or generic Store-page result. A generic Chrome Web Store page is not a billable extension.

Output fields

Field	Meaning
extensionId, url	Extension identifier and canonical Store URL
name, description, icon	Public listing identity, summary and image
users, rating, ratingCount	Public adoption and rating figures where recognized
version, updated	Version and listing update date
category, developer	Category and developer/author where exposed in recognized markup

Fields can be null. A null developer, rating count or date is not itself evidence of an unsafe extension. The Actor does not inspect permissions, extension code or runtime behavior and does not provide a security verdict.

Pricing

One extension event per returned extension row. FREE-tier list price: US$0.002 per result / US$2 per 1,000 results. Current paid-plan event discounts are displayed on the Actor pricing page. Infrastructure charges are separate. Use a short ID list and an explicit maximum-charge setting for initial trials; do not repeat IDs unless repeated observations are intended.

Maximum charge is respected. Each result is written and billed in one step. Before requesting the next listing, the Actor checks that your maximum total charge still covers one more extension event; if it does not, it stops without requesting, writing or billing anything further (a budget below one event makes no request at all). Unavailable listings are never billed. If the platform restarts a run, it resumes after the last delivered extension without duplicating paid rows. A billing error stops the run with a failure.

Recurring use

Reuse a saved task with the same ID list to collect later snapshots of versions, update dates, public user counts and ratings. Export each dataset and compare by extensionId in your own workflow. The Actor returns current observations; it does not store a cross-run historical index or generate change alerts by itself.

Source and limitations

The Actor makes plain HTTP requests to public Chrome Web Store detail pages. It does not log in, access private browser data, download extension packages or call developer-console APIs. Removed, unlisted, region-blocked or unavailable listings may return no usable result; Store markup changes can affect extraction. Use the data in line with Store terms and applicable law, and treat publisher and adoption details as public listing claims rather than independently verified facts.

Troubleshooting

• No results: confirm the listing still opens publicly. Removed listings may return HTTP200 with a generic Store page; that is rejected.
• Missing version/date: the source may omit the field or change its markup. Missing fields remain null.
• Input rejected: provide a non-empty extensions array using IDs or detail URLs.
• Need a security review: use a dedicated scanner or human review. This Actor exports public metadata only.