PyPI Package Search Scraper

PyPI Package Search Scraper is a BrowserAct Bot template for collecting structured package records from public PyPI search pages. Configure a keyword and result count, then run the Bot to return Python package search data for dependency discovery, ecosystem research, package monitoring, or automation workflows.

What Does BrowserAct PyPI Package Search Scraper Do?

This template opens PyPI search results for your keyword, reads public package snippets, follows pagination when needed, and returns one structured record per package.

Key Features

Extract public PyPI package search results without requiring a PyPI login.
Capture rank, package name, package URL, description, release date, visible status fields, and search keyword.
Configure base URL, keyword, and count.
Continue through paginated results until the requested count is reached.
Preserve empty values when PyPI search snippets do not display optional metadata.

What Data Can I Extract from PyPI?

Field	Description
`rank`	Package result position.
`package_name`	PyPI package name.
`package_url`	Public PyPI package URL.
`version`	Version when visible in the search result snippet.
`description`	Package description from the search result.
`release_date`	Visible release or updated timestamp.
`status`	Visible status or badge text when shown.
`keyword`	Search keyword used for the run.

How to Use PyPI Package Search Scraper

Click Run task.
Enter a search keyword.
Set how many package records to collect.
Run the Bot and review the structured package results.
Reuse the Bot with another keyword or connect the output to your workflow.

Input Parameters

Parameter	Required	Default	Description
`base_url`	Yes	`https://pypi.org`	Base PyPI website URL without a trailing slash.
`keyword`	Yes	`browser automation`	Search keyword or phrase.
`count`	Yes	`20`	Maximum number of package records to return.

Example Output

{
  "packages": [
    {
      "rank": 1,
      "package_name": "browser-automation-launcher",
      "package_url": "https://pypi.org/project/browser-automation-launcher/",
      "version": null,
      "description": "Browser Automation launcher",
      "release_date": "2025-10-24 04:02:44 (-04:00)",
      "status": null,
      "keyword": "browser automation"
    }
  ]
}

How Does it Work?

How PyPI Package Search Scraper runs

BrowserAct constructs a public PyPI search URL from base_url and keyword, then opens the search results page in a live browser. The Bot reads each package snippet, maps package name, URL, description, release date, optional visible metadata, and the search keyword, then returns records in rank order.

When count is higher than the first page of results, BrowserAct follows PyPI pagination and continues collecting records until the requested count is reached or no more public results are available. Version and status fields remain empty when the PyPI search result snippet does not display them.

How to Build a New Scraper Bot with Agent Built

Step 1: Describe the Data You Need

Open BrowserAct and start Agent Built from the Home prompt box or from Create -> Build with Agent. Paste a clear request that includes the website, the records to collect, the filters or search conditions, the fields to return, the result limit, and the inputs you want to reuse later.

Agent Built prompt templates

Step 2: Let BrowserAct Build and Test the Bot

BrowserAct explores the live website, works out the navigation and extraction path, and validates the result. If BrowserAct asks for clarification, reply in the same build conversation with the missing URL, condition, field, example, or expected output.

Agent Built exploration

Step 3: Run the Bot and Review the Result

When the build is complete, run the Bot with the default inputs first. Review the structured records, source URLs, missing fields, and row count before reusing the Bot with new inputs or connecting it to another workflow.

Agent Built run inputs

Agent Built run results

Why Scrape PyPI Package Search Results?

PyPI search data helps teams discover Python packages, compare dependency options, monitor package ecosystems, collect package metadata for research, and route search results into dashboards or agents.

Who Can Use This Template?

Python teams researching dependencies.
Developer tool teams monitoring package ecosystems.
Open-source analysts collecting package metadata.
Security or platform teams reviewing public package signals.
Automation builders routing package records into reports, alerts, databases, or agents.

How Many Results Can You Scrape?

Use count to control the number of package records returned. Higher counts require pagination and may take longer than collecting only the first page.

Automation and Export

Automation and export flow

BrowserAct returns structured PyPI package records first. You can then use the output through API JSON responses, n8n workflows, Make scenarios, Zapier automations, MCP-based agent workflows configured from the Bot's Integrations tab, or manual CSV review.

Need Help?

Discord: Discord Community

E-mail: service@browseract.com

Brief