# crates.io Scraper: Rust Crates, Downloads, Versions | $1/1K (`one_dollar_store/crates-io-packages-scraper`) Actor

$1 per 1,000 results, platform usage included. Rust crates from the official crates.io API: downloads, recent downloads, versions, license, Rust version, keywords, categories, links. Search, filter by category or keyword, or look up crates by name. No key.

- **URL**: https://apify.com/one_dollar_store/crates-io-packages-scraper.md
- **Developed by:** [One Dollar Store](https://apify.com/one_dollar_store) (community)
- **Categories:** Developer tools, Open source
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

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

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## crates.io Scraper: Rust Crates, Downloads and Versions

**$1 per 1,000 results. Platform usage included. No rental, no minimum.**

[Open it in Apify Console](https://console.apify.com/actors/IpdCaDTlWrCmke5uC/input)

### What it costs

| Results | Price |
|---|---|
| 1,000 | $1.00 |
| 10,000 | $10.00 |
| 100,000 | $100.00 |

Plus $0.001 per run. One flat price, platform usage included, so there is no separate compute or proxy bill. A daily run that reads the 100 most downloaded crates costs $0.101 (100 results plus the run fee), about $3.03 for 30 days. A result is one crate or, in version mode, one version.

### Why use it

- **Crates and versions.** Get one row per crate, or one row per released version of the crates you choose, with downloads, license, minimum Rust version, edition, package size and who published it.
- **Search, filter or look up.** Search by words, narrow by category or keyword, sort by all time downloads, recent downloads, recent updates or newest, or give exact crate names.
- **Built for a one request per second site.** crates.io asks API users for at most one request per second and a User-Agent that names the application. The actor does both, so you do not have to think about it.
- **Official API, no key.** Data comes from the crates.io API. No login, no token.
- **Direct links.** Every row has the crates.io page and the docs.rs page.

### Quick start

1. Open the actor, type a search word, press **Start**.
2. Or paste this input:

```json
{ "searchQuery": "csv", "sort": "relevance", "includeDetails": true, "maxItems": 20 }
```

3. Download the results as JSON, CSV or Excel, or read them through the API.

### Use it from code

```bash
curl -X POST "https://api.apify.com/v2/acts/one_dollar_store~crates-io-packages-scraper/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"crateNames": ["serde", "tokio"], "maxItems": 10}'
```

```python
from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("one_dollar_store/crates-io-packages-scraper").call(
    run_input={"crateNames": ["serde", "tokio"], "maxItems": 10}
)
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["name"], item["newestVersion"], item["downloads"], item.get("license"))
```

### Use it from an AI assistant

Claude, ChatGPT, Cursor and other assistants can call this actor through Apify's MCP server. Add it with this server address:

```
https://mcp.apify.com?tools=one_dollar_store/crates-io-packages-scraper
```

Then ask, for example: "Look up serde, tokio and clap and tell me each one's license, newest version and minimum Rust version."

### Switching from another crates.io actor

Most crates.io actors take a search term, a crate name list and a result limit. Here they are `searchQuery`, `crateNames` and `maxItems`. The core output fields are `name`, `newestVersion`, `downloads`, `recentDownloads`, `license`, `repository` and `cratesUrl`.

### Input

| Field | Type | Default | What it does |
|---|---|---|---|
| `searchQuery` | text | none | Words to look for in crate names, descriptions and keywords. Empty lists crates by the sort order. |
| `crateNames` | list of text | none | Exact crate names, one per line. Each one is looked up directly and returns the full record. Names that do not exist are skipped. |
| `category` | text | none | A crates.io category slug, for example `web-programming`. |
| `keyword` | text | none | A keyword the crate authors chose, for example `parser`. |
| `sort` | text | `downloads` | `downloads`, `recent-downloads`, `recent-updates`, `new`, `relevance` or `alpha`. |
| `resultType` | text | `crates` | `crates` for one row per crate, `versions` for one row per version of each crate found. |
| `includeDetails` | true or false | false | Adds license, minimum Rust version, edition, size, keywords and categories to search results. One extra request per crate. |
| `maxItems` | number | 100 | Total results for the run. Minimum 10, maximum 10,000. |

### Output fields

Crate rows (`rowType` is `crate`):

| Field | Meaning |
|---|---|
| `name`, `description` | The crate name and the description its authors wrote. |
| `newestVersion`, `maxStableVersion`, `versionCount` | Newest version, highest version that is not a pre-release, and how many versions exist. |
| `downloads`, `recentDownloads` | All time downloads and downloads in the last 90 days, as crates.io counts them. |
| `createdAt`, `updatedAt` | When the crate was first published and last changed (UTC). |
| `keywords`, `categories` | Set when you look a crate up by name or turn details on. The search list leaves them out. |
| `license`, `rustVersion`, `edition`, `crateSizeBytes`, `latestPublishedAt`, `latestPublishedBy` | From the newest version. Same condition as keywords. `rustVersion` is empty when the authors did not declare one. |
| `homepage`, `documentation`, `repository` | Links the authors set. |
| `cratesUrl`, `docsUrl` | The crates.io page and the docs.rs page. |

Version rows (`rowType` is `version`): `name`, `version`, `yanked`, `yankMessage`, `license`, `rustVersion`, `edition`, `downloads` (for that version), `crateSizeBytes`, `featureCount`, `hasLib`, `binNames`, `createdAt`, `updatedAt`, `publishedBy`, `cratesUrl`, `docsUrl`. Every row also has `scrapedAt`. Fields a crate does not have are left out.

### Sample results

Real rows from test runs on 20 October 2026: two crates from a search sorted by downloads, one crate looked up by name, and one version row. Some fields are left out.

```json
[
  {"rowType": "crate", "name": "once_cell", "description": "Single assignment cells and lazy values.", "newestVersion": "1.21.4", "downloads": 1393741088, "recentDownloads": 323860204, "versionCount": 67, "updatedAt": "2026-03-12T10:59:52.512992Z", "repository": "https://github.com/matklad/once_cell", "cratesUrl": "https://crates.io/crates/once_cell"},
  {"rowType": "crate", "name": "tokio", "description": "An event-driven, non-blocking I/O platform for writing asynchronous I/O backed applications.", "newestVersion": "1.54.0", "downloads": 1082931722, "recentDownloads": 262899274, "versionCount": 200, "updatedAt": "2026-10-19T16:33:48.987430Z", "repository": "https://github.com/tokio-rs/tokio", "cratesUrl": "https://crates.io/crates/tokio"},
  {"rowType": "crate", "name": "serde", "newestVersion": "1.0.229", "downloads": 1555648707, "license": "MIT OR Apache-2.0", "rustVersion": "1.56", "edition": "2021", "keywords": ["serialization", "no_std", "serde"], "categories": ["no-std", "encoding", "no-std::no-alloc"], "latestPublishedBy": "dtolnay", "cratesUrl": "https://crates.io/crates/serde"},
  {"rowType": "version", "name": "itoa", "version": "1.0.18", "yanked": false, "license": "MIT OR Apache-2.0", "rustVersion": "1.68", "edition": "2021", "downloads": 397075046, "crateSizeBytes": 15935, "publishedBy": "dtolnay", "createdAt": "2026-03-20T00:12:37.043881Z", "cratesUrl": "https://crates.io/crates/itoa/1.0.18"}
]
```

### Limits

- **One request per second.** crates.io asks API users for at most one request per second, so the actor waits between requests. A search page holds up to 100 crates, so 1,000 crates take about 10 requests. A test run of 50 crates finished in about 4 seconds.
- **Details and versions cost time.** Each crate you look up by name, each crate with `includeDetails` on and each crate in version mode needs its own request. In a test, 10 crates with details took 13 seconds. The default time limit is one hour, about 2,700 crates with details. For more, raise Timeout under Run options. If a run reaches the limit, it stops cleanly and keeps what it has.
- **The search list is shorter than a full record.** It has downloads, versions, dates and links, but no license, minimum Rust version, size, keywords or categories. Turn on `includeDetails` or use `crateNames` for those.
- **Up to 10,000 results per run.** For the whole registry in one go, crates.io publishes a daily database dump. This actor is for searches, lists and lookups.
- **Download counts are crates.io's own figures.** `downloads` counts downloads of the package file, so it is not the number of projects that use a crate. `recentDownloads` covers the last 90 days.
- **Search is crates.io's.** Which crates match a word, and in what order for `relevance`, is decided by crates.io, not by this actor.
- **Version order.** Version rows come in the order crates.io returns them, which was newest first in the tests.
- **Public data only.** Version rows carry a `yanked` flag. Private registries are not covered.

### FAQ

**How much does it cost to scrape 10,000 crates?**
$10, plus $0.001 for each run.

**Do I pay for compute or proxy on top?**
No. Platform usage is included in the $1 per 1,000 price. The crates.io API is read directly, so no proxy is used.

**Where does the data come from?**
From the public crates.io API, run by the Rust project. No key and no login are needed.

**How do I find the license of a crate?**
Look it up by name in `crateNames`, or turn on `includeDetails` for a search. The `license` field holds the license expression of the newest version, for example `MIT OR Apache-2.0`.

**How do I list every version of a crate?**
Put the crate in `crateNames` and set `resultType` to `versions`. Each version has its own row with downloads, license and publisher.

**How do I watch for new crates?**
Set `sort` to `new` and run on a schedule. Use `name` to drop crates you already have.

**Is it legal?**
The actor reads public data only, with no login. It follows the one request per second rule that crates.io publishes for its API. How you use the data is up to you: follow the source's terms and the law where you live.

**Is this an official crates.io product?**
No. It is an independent tool and is not affiliated with or endorsed by crates.io or the Rust project.

**Do I need an Apify account?**
Yes. Actors run from an Apify account, and a free account is enough to start: it includes $5 of platform usage every month. You can [sign up here](https://www.apify.com?fpr=ymnoit). This is a referral link and it costs you nothing.

**Is there a limit on the free plan?**
Yes. A run started from a free plan account delivers the first 10 results, then ends with a message and a link to the plans. Any paid plan returns everything you ask for, up to your own limit. The price per result is the same on every plan.

### More from The One Dollar Store

Every actor here costs $1 per 1,000 results, platform usage included. See the whole store: https://apify.com/one_dollar_store

**Domains and apps**

- [Apple App Store Scraper](https://apify.com/one_dollar_store/app-store-apps-scraper): App details, ratings and search results.
- [DNS Records Lookup](https://apify.com/one_dollar_store/dns-records-lookup): DNS records for any list of domains.
- [Domain WHOIS Lookup](https://apify.com/one_dollar_store/domain-whois-rdap-lookup): Registrar, dates and name servers for any domain.
- [Subdomain Finder](https://apify.com/one_dollar_store/subdomain-finder-crtsh): Subdomains found in certificate logs.
- [Shopify App Store Scraper](https://apify.com/one_dollar_store/shopify-app-store-scraper): Shopify apps with ratings and pricing.
- [Hugging Face Scraper](https://apify.com/one_dollar_store/hugging-face-models-scraper): Models and datasets with downloads and tags.
- [WordPress Plugin Scraper](https://apify.com/one_dollar_store/wordpress-plugin-directory-scraper): Plugins with installs, ratings and versions.

### Changelog

- October 2026: first release.

# Actor input Schema

## `searchQuery` (type: `string`):

Optional. Words to look for in crate names, descriptions and keywords, for example async or http client. Leave empty to list crates by the sort order below.

## `crateNames` (type: `array`):

Optional. One crate name per line, for example serde or tokio. Each name is looked up directly and returns the full record, including license and Rust version. Costs one request per name, at one request per second.

## `category` (type: `string`):

Optional. A crates.io category slug, for example web-programming or command-line-utilities. The slug is the last part of the category page address.

## `keyword` (type: `string`):

Optional. A crates.io keyword that the crate authors chose, for example parser or cli.

## `sort` (type: `string`):

Order of the results when you search. Downloads means all time downloads.

## `resultType` (type: `string`):

Crates gives one result per crate. Versions gives one result per released version of each crate found, and costs one extra request per crate.

## `includeDetails` (type: `boolean`):

Search results do not carry the license, the minimum Rust version or the crate size. Turn this on to look up each crate for them. It costs one extra request per crate, at one request per second, so 100 crates take about two minutes.

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

The run stops after this many results. Minimum 10, maximum 10,000. The site allows one request per second, and each search page holds up to 100 crates.

## Actor input object example

```json
{
  "searchQuery": "async",
  "sort": "downloads",
  "resultType": "crates",
  "includeDetails": false,
  "maxItems": 50
}
```

# Actor output Schema

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

No description

## `summary` (type: `string`):

No description

# 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 = {
    "searchQuery": "async",
    "sort": "downloads",
    "resultType": "crates",
    "maxItems": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("one_dollar_store/crates-io-packages-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 = {
    "searchQuery": "async",
    "sort": "downloads",
    "resultType": "crates",
    "maxItems": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("one_dollar_store/crates-io-packages-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 '{
  "searchQuery": "async",
  "sort": "downloads",
  "resultType": "crates",
  "maxItems": 50
}' |
apify call one_dollar_store/crates-io-packages-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,one_dollar_store/crates-io-packages-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/IpdCaDTlWrCmke5uC/builds/djytykzXQcW6EW00Y/openapi.json
