PyPI Scraper - Python Package Metadata & Versions avatar

PyPI Scraper - Python Package Metadata & Versions

Pricing

from $1.10 / 1,000 package scrapeds

Go to Apify Store
PyPI Scraper - Python Package Metadata & Versions

PyPI Scraper - Python Package Metadata & Versions

Scrape Python package metadata from PyPI: name, version, summary, author, license, keywords, dependencies, project URLs, release history and Python version. By name or newest packages. No key. Independent tool, not affiliated with PyPI.

Pricing

from $1.10 / 1,000 package scrapeds

Rating

0.0

(0)

Developer

Scrape Sage

Scrape Sage

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

6 days ago

Last modified

Share

Disclaimer: This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by the Python Software Foundation or any of its subsidiaries. All trademarks mentioned are the property of their respective owners. "PyPI" is referenced only to describe the publicly available website this Actor collects data from.

Pull clean metadata for Python packages from PyPI: version, summary, author, license, keywords, dependencies, project URLs (repo, docs, homepage), required Python version, release count and latest upload. Scrape a named list of packages, or the newest / recently updated packages from PyPI's feeds. Built on the official PyPI JSON API - no key, no browser.

What you get per package

FieldMeaning
name / version / summaryPackage name, latest version, one-line summary
author / authorEmail / licenseAuthor/maintainer, contact email, license
requiresPython / dependencies / dependencyCountPython constraint and the requires_dist list
homePage / repositoryUrl / documentationUrl / projectUrlsThe package's links
keywords / classifiersTrove classifiers and keywords
releaseCount / latestUpload / yanked / packageUrlRelease history and status

Input

{ "packages": ["requests", "numpy", "django"] }
  • Package names - one per line.
  • Or scrape a feed - pull the newest packages or recently updated ones from PyPI's feeds and scrape their metadata automatically.
  • Import from a file - paste a whole list, or link a public .txt/.csv, a Google Sheet/Drive link, or an Apify key-value-store record.
  • Max packages / Concurrency bound the run. Output fields - tick only the columns you want (e.g. just name, version, license, dependencies for a license/dependency audit).

Leave the package list empty (and pick no feed) and the run returns a small free sample.

Reliability

Reads the official PyPI JSON API - public, no key, no proxy, no anti-bot. A package name that does not exist is reported (not an error) and charges nothing; an empty run bills $0.

Honest limits

  • Metadata is what the maintainer published. author, keywords, documentationUrl and repositoryUrl are present only when the package sets them - many packages fill some fields and leave others blank. That is the package's own metadata, not a scraping gap.
  • No PyPI keyword search (PyPI removed it). Use the newest/updated feeds, or provide package names (e.g. from a requirements.txt).

Pricing

$0.002 per package on the FREE tier (tiered pricing lowers it with volume). Only packages actually saved are billed; a not-found name or empty run costs nothing.

Output views

  • Packages - name, version, summary, author, license, Python constraint, releases and the PyPI link.

Use with AI assistants (MCP)

Available through the Apify MCP server - an agent can pull metadata, licenses and dependencies for a list of packages to audit a project's supply chain.

Agent-ready: autonomous payments (x402 & Skyfire)

This actor is agent-ready - AI agents can discover it, run it, and pay for it autonomously, with no Apify account and no human in the loop. It uses pay-per-event pricing and limited permissions, so it qualifies for Apify's agentic-payment standards:

  • x402 - an open, HTTP-native payment protocol. Agents pay per run in USDC on the Base network directly through the Apify MCP server - no account, no API key.
  • Skyfire - agent-to-service payments for fully autonomous AI-agent workflows.

Building an AI agent, MCP tool, or autonomous data pipeline? This scraper is ready to plug in and pay as it goes.

Automate & schedule

Run this Actor on autopilot and pull results into your own stack:

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'MY_APIFY_TOKEN' });
const run = await client.actor('scrapesage/pypi-scraper').call({
"packages": [
"requests",
"numpy"
]
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(`Got ${items.length} records`);

Integrate with any app

Connect the dataset to thousands of apps - no code required:

  • Make - multi-step automation scenarios.
  • Zapier - push new records straight into your CRM or spreadsheet.
  • Slack - get notified when a scheduled run finds something new.
  • Google Drive / Sheets - auto-export every run to a spreadsheet.
  • Airbyte - pipe results into your data warehouse.
  • GitHub - trigger runs from commits or releases.

FAQ

How is this Actor billed? Pay-per-event: you pay only for the results it delivers, with no monthly rental and no start fee. The per-event price is shown on the Pricing tab.

Can I schedule it and get results automatically? Yes - create a Schedule and add a webhook or an integration (Google Sheets, Slack, Make, Zapier) to push each run's dataset wherever you need it.

Which export formats are available? Every run's dataset can be downloaded as JSON, CSV, Excel (XLSX), XML, HTML or RSS from the Apify Console or the API.

Can I run it from code or an AI agent? Yes - through the Apify API and client libraries, or from Claude, ChatGPT and other assistants via the Apify MCP server.

Is it legal to scrape PyPI? This Actor collects publicly available data only. You are responsible for using the output in compliance with applicable laws (including data-protection law where personal data is involved) and the source's terms. See the Disclaimer below.

Is this an official PyPI tool? No. It is an independent, third-party Actor with no affiliation to, endorsement by or sponsorship from the Python Software Foundation. See the Disclaimer below.

Disclaimer

This Actor is an independent tool and is not affiliated with, endorsed by, or sponsored by the Python Software Foundation or any of its subsidiaries. All trademarks mentioned are the property of their respective owners.

"PyPI" and any related marks are the property of their respective owners and are used here only in a descriptive, nominative sense - to identify the publicly accessible website from which this Actor collects data. This Actor is not an official PyPI product, is not authorised or certified by the Python Software Foundation, and does not distribute PyPI software. It collects only publicly available information; you are responsible for ensuring your use of that data complies with applicable laws, regulations and the terms of the source website.

Need help?

Open an issue on the Actor's Issues tab, or visit the Apify help center. Feature requests are welcome - this Actor is actively maintained.