PyPI Scraper - Python Package Metadata & Versions

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

Field	Meaning
name / version / summary	Package name, latest version, one-line summary
author / authorEmail / license	Author/maintainer, contact email, license
requiresPython / dependencies / dependencyCount	Python constraint and the requires_dist list
homePage / repositoryUrl / documentationUrl / projectUrls	The package's links
keywords / classifiers	Trove classifiers and keywords
releaseCount / latestUpload / yanked / packageUrl	Release 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.