# PyPI Scraper - Python Package Metadata & Versions (`scrapesage/pypi-scraper`) Actor

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.

- **URL**: https://apify.com/scrapesage/pypi-scraper.md
- **Developed by:** [Scrape Sage](https://apify.com/scrapesage) (community)
- **Categories:** Agents, Integrations
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.10 / 1,000 package scrapeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## 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

```json
{ "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](https://docs.pypi.org/api/json/) - 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](https://docs.apify.com/platform/integrations/mcp) - 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](https://docs.apify.com/platform/actors/publishing/monetize/pay-per-event) pricing and [limited permissions](https://docs.apify.com/platform/actors/development/permissions), so it qualifies for Apify's agentic-payment standards:

- **[x402](https://docs.apify.com/platform/integrations/x402)** - an open, HTTP-native payment protocol. Agents pay per run in USDC on the Base network directly through the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp) - no account, no API key.
- **[Skyfire](https://docs.apify.com/platform/integrations/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.

# Actor input Schema

## `packages` (type: `array`):

PyPI package names to scrape, one per line - e.g. <code>requests</code>, <code>numpy</code>, <code>django</code>. <b>Leave empty (and pick no feed) and the run returns a small free sample.</b>

## `feed` (type: `string`):

Instead of naming packages, pull the latest package names from PyPI's feeds and scrape their metadata.

## `packagesFromFile` (type: `string`):

Bulk-load package names. Either <b>paste the whole list</b> (one per line or comma-separated), or give <b>a single link</b> to a public <code>.txt</code>/<code>.csv</code>, a Google Sheet/Drive link, or an Apify key-value-store record. A file that cannot be read says so and charges nothing.

## `maxItems` (type: `integer`):

Maximum packages to scrape in one run. You are only charged for packages actually saved.

## `concurrency` (type: `integer`):

How many packages to fetch in parallel.

## `outputFields` (type: `array`):

Pick the fields you want and every record is trimmed to exactly those - handy for lean CSV/Sheets exports.

## Actor input object example

```json
{
  "packages": [
    "requests",
    "numpy"
  ],
  "feed": "",
  "maxItems": 500,
  "concurrency": 10
}
```

# Actor output Schema

## `results` (type: `string`):

Each scraped record - Python packages - as a JSON item in the default dataset.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "packages": [
        "requests",
        "numpy"
    ],
    "packagesFromFile": ""
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapesage/pypi-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "packages": [
        "requests",
        "numpy",
    ],
    "packagesFromFile": "",
}

# Run the Actor and wait for it to finish
run = client.actor("scrapesage/pypi-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "packages": [
    "requests",
    "numpy"
  ],
  "packagesFromFile": ""
}' |
apify call scrapesage/pypi-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapesage/pypi-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/4eOZalCLYP8pBdhgD/builds/VIIF9UqJaGdBSUB4y/openapi.json