# RubyGems Package Lookup (`m_ctim/rubygems-package-lookup`) Actor

Look up current version, total downloads, license, runtime dependencies, and yanked status for any RubyGems package via the official rubygems.org API.

- **URL**: https://apify.com/m\_ctim/rubygems-package-lookup.md
- **Developed by:** [Timothy Kelvin](https://apify.com/m_ctim) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

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

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

## RubyGems Package Lookup

Look up current version, total downloads, license, homepage, and
runtime dependencies for any RubyGems package, via the official
[rubygems.org API](https://guides.rubygems.org/rubygems-org-api/).

Built for DevOps and tooling teams tracking Ruby dependency health —
checking a gem's latest version, whether it's been yanked, or how
widely adopted it is — without checking rubygems.org by hand.

### Input

```json
{
  "gemNames": ["rails", "rspec", "nokogiri"]
}
```

| Field | Type | Description |
|---|---|---|
| `gemNames` | array of strings | One or more RubyGems package names to look up. Default `["rails"]`. |

### Output

One record per requested gem:

```json
{
  "gemName": "rails",
  "found": true,
  "latestVersion": "8.1.3.1",
  "latestVersionReleasedAt": "2026-07-29T15:02:41.060Z",
  "yanked": false,
  "totalDownloads": 778125297,
  "latestVersionDownloads": 3144551,
  "licenses": ["MIT"],
  "authors": "David Heinemeier Hansson",
  "homepageUrl": "https://rubyonrails.org",
  "sourceCodeUrl": "https://github.com/rails/rails/tree/v8.1.3.1",
  "documentationUrl": null,
  "runtimeDependencies": [
    { "name": "actionpack", "requirements": "= 8.1.3.1" }
  ]
}
```

An unrecognized gem name returns `{ "gemName": "...", "found": false }`
rather than failing the whole run.

Note: `totalDownloads` is a cumulative all-time count — rubygems.org's
public API doesn't expose a daily/period download-history endpoint
the way npm and PyPI's stats APIs do, so this actor is a snapshot
lookup rather than a trend tracker.

### How it works

Direct calls to the official `rubygems.org/api/v1/gems` endpoint — no
proxy, no key, no scraping.

### Pricing note

Billed per **lookup** (one run) at a flat rate, regardless of how many
gem names are requested.

### Related products

- [NPM Download Stats Tracker](https://github.com/timmKal01/npm-download-stats-tracker)
- [PyPI Download Stats Tracker](https://github.com/timmKal01/pypi-download-stats-tracker)
- [Homebrew Package Lookup](https://github.com/timmKal01/homebrew-package-lookup) — same snapshot-lookup shape, different ecosystem

# Actor input Schema

## `gemNames` (type: `array`):

One or more RubyGems package names to look up, e.g. "rails", "rspec", "nokogiri".

## Actor input object example

```json
{
  "gemNames": [
    "rails"
  ]
}
```

# Actor output Schema

## `results` (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 = {
    "gemNames": [
        "rails"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("m_ctim/rubygems-package-lookup").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 = { "gemNames": ["rails"] }

# Run the Actor and wait for it to finish
run = client.actor("m_ctim/rubygems-package-lookup").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 '{
  "gemNames": [
    "rails"
  ]
}' |
apify call m_ctim/rubygems-package-lookup --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,m_ctim/rubygems-package-lookup"
        }
    }
}

```

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/iQ29gK78OmEsWQRfx/builds/fK0RBKxeCwzIBrrAp/openapi.json