Rubygems

Use RubyGems data APIs through OpenAny to retrieve packages or modules that depend on the selected resource. For dependents, provide resource name (name); refine the result with search expression or keywords (q). Other available operations include gem, versions. Reverse-dependency results identify the packages or projects that use the selected resource, rather than its own requirements, and retain the source's version relationships or usage ordering when those are provided. Identify projects or packages that depend on a resource, compare usage relationships and estimate the reach of a proposed package change. Each API page provides supported parameters, request and response examples, and usage pricing.

Endpoints
3In this collection
Providers
1Unique providers
Requests
—Loading...
Success rate
—Loading...
Response P50
—Loading...
Loading statistics... API browsing remains available.

Available APIs

RubyGems versions API

Use the RubyGems versions API to retrieve published package or extension versions and release metadata. Provide resource name (name); refine the result with prerelease inclusion flag (prerelease), source platform (platform). Version entries retain the release number and any date, platform or prerelease details supplied by that ecosystem, so a historical release can be selected before its own package metadata is retrieved. Compare published release numbers and dates, identify prereleases where provided and choose a version for a compatibility review. The detail page provides the supported parameters, request examples, available response examples and usage pricing for this operation.

1 provider · 1 implementation$0.002 / billing credit

RubyGems gem API

Use the RubyGems gem API to retrieve package metadata and the source's published package details. Provide resource name (name); refine the result with release version (version), source platform (platform). Package details identify the chosen release and its published licence or project references, providing the metadata needed to distinguish the library, application or module before inspecting its ecosystem-specific details. Identify a package release, inspect its licence and distribution metadata and select the version to examine for integration. The detail page provides the supported parameters, request examples, available response examples and usage pricing for this operation.

1 provider · 1 implementation$0.002 / billing credit

RubyGems dependents API

Use the RubyGems dependents API to retrieve packages or modules that depend on the selected resource. Provide resource name (name); refine the result with search expression or keywords (q). Reverse-dependency results identify the packages or projects that use the selected resource, rather than its own requirements, and retain the source's version relationships or usage ordering when those are provided. Identify projects or packages that depend on a resource, compare usage relationships and estimate the reach of a proposed package change. The detail page provides the supported parameters, request examples, available response examples and usage pricing for this operation.

1 provider · 1 implementation$0.002 / billing credit

Common questions

How are Rubygems APIs priced?

Each endpoint publishes its own rate and billing unit. Compare the selected implementation and request-specific conditions; a collection starting price is not a quote for every request.

How do I authenticate Rubygems requests?

Use your OpenAny API key from a secure environment variable for supported account-based calls. Never paste secrets into prompts, documentation examples or public logs.

Are all implementations interchangeable?

No. Read each endpoint request schema, response examples and limitations before execution. Different suppliers may expose different fields and behavior; approve the budget before a paid call.

Use Rubygems with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.