# OpenAPI Directory & API Specs Scraper (APIs.guru) (`ninhothedev/openapi-directory-scraper`) Actor

$0.5/1K 🔥 OpenAPI directory scraper! 2500+ APIs with machine-readable spec URLs, providers & categories. No key. JSON, CSV, Excel or API in seconds. Automate integration research ⚡

- **URL**: https://apify.com/ninhothedev/openapi-directory-scraper.md
- **Developed by:** [ninhothedev](https://apify.com/ninhothedev) (community)
- **Categories:** Developer tools, Integrations, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.50 / 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/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

## OpenAPI Directory & API Specs Scraper (APIs.guru) — 2,500+ APIs, No API Key

Scrape the **APIs.guru OpenAPI directory** — the largest open, machine-readable index of public REST APIs — into a clean dataset. One row per API with the **OpenAPI/Swagger spec URL (JSON + YAML)**, all published versions, the provider, categories, contact, license, terms, logo and — optionally — the actual **path and operation counts** parsed from the spec itself.

No API key. No login. No proxy required.

### Why this actor

APIs.guru is the "Wikipedia for Web APIs": ~2,529 APIs, ~3,992 specs and ~108,000 endpoints, kept in sync with the upstream providers (AWS, Azure, Google, Twilio, Adyen, GitHub, eBay, Stripe-likes, government open data and hundreds more). This actor turns that directory into a flat, spreadsheet-friendly dataset you can filter, join and feed into code generators.

#### How is this different from `public-apis-scraper`?

| | **openapi-directory-scraper** (this actor) | [public-apis-scraper](https://apify.com/ninhothedev/public-apis-scraper) |
|---|---|---|
| Source | APIs.guru `/v2/list.json` — a **machine-readable OpenAPI directory** | The `public-apis` **curated markdown list** on GitHub |
| Per-API data | Actual **OpenAPI/Swagger spec URLs** (JSON + YAML), spec version (2.0 / 3.x), every published version, spec origin URL, license, terms, contact, logo | Name, description, auth type, HTTPS/CORS flag, doc link |
| Machine usable | Yes — spec URLs can be fed straight into codegen / linting / mocking | No — human-curated links only |
| Endpoint counts | Optional: downloads each spec and counts paths + operations | Not available |
| Scale | ~2,500 APIs, ~4,000 specs, 677 providers | ~1,400 curated entries |

They complement each other: use `public-apis-scraper` to discover free APIs a human curated, use **this** actor when you need the actual specs to build against.

### Use cases

- **API discovery** — find every public API in a category (`cloud`, `financial`, `payment`, `ecommerce`, `open_data`, `messaging`, `machine_learning`) with a real, downloadable spec.
- **Integration research** — compare providers, check which spec version (Swagger 2.0 vs OpenAPI 3.x) an API ships, and grab licensing/terms links before you commit.
- **SDK generation pipelines** — feed `spec_url` into openapi-generator, Speakeasy, Fern, Kiota or Prism to auto-build clients, mocks and test suites for hundreds of APIs at once.
- **Competitive API analysis** — measure API surface size (`path_count`, `operation_count`) across competitors, track how many services a provider publishes, and monitor `updated` timestamps for API churn.

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `mode` | select | `apis` | `apis` = the full OpenAPI directory (one item per API). `providers` = the provider list with API counts. |
| `providerFilter` | string | – | Keep one provider only, e.g. `azure.com`, `googleapis.com`, `amazonaws.com`, `twilio.com`. |
| `categoryFilter` | string | – | Keep one APIs.guru category, e.g. `cloud`, `financial`, `developer_tools`. |
| `searchQuery` | string | – | Case-insensitive substring over API id, title and description, e.g. `payment`, `weather`. |
| `countEndpoints` | boolean | `false` | Download each preferred spec and count `paths` + operations. One extra request per API, specs can be multi-MB → much slower. |
| `maxItems` | integer | `500` | Cap on pushed items (max 5,000). |

Filters combine with AND.

#### Example input

```json
{
  "mode": "apis",
  "categoryFilter": "financial",
  "searchQuery": "payment",
  "countEndpoints": false,
  "maxItems": 200
}
```

### Output

```json
{
  "type": "api",
  "api_id": "1forge.com",
  "provider": "1forge.com",
  "service": null,
  "title": "1Forge Finance APIs",
  "description": "Stock and Forex Data and Realtime Quotes",
  "preferred_version": "0.0.1",
  "version_count": 1,
  "all_versions": ["0.0.1"],
  "openapi_version": "2.0",
  "spec_url": "https://api.apis.guru/v2/specs/1forge.com/0.0.1/swagger.json",
  "spec_yaml_url": "https://api.apis.guru/v2/specs/1forge.com/0.0.1/swagger.yaml",
  "origin_url": "http://1forge.com/openapi.json",
  "origin_format": "swagger",
  "categories": ["financial"],
  "logo_url": "https://api.apis.guru/v2/cache/logo/https_1forge.com_assets_images_f-blue.svg",
  "contact_name": "1Forge",
  "contact_email": "contact@1forge.com",
  "contact_url": "http://1forge.com",
  "license_name": null,
  "license_url": null,
  "terms_url": null,
  "external_docs_url": null,
  "homepage": "https://api.apis.guru/v2/specs/1forge.com/0.0.1.json",
  "is_unofficial": false,
  "added": "2017-05-30T08:34:14Z",
  "updated": "2017-06-27T16:49:57Z",
  "path_count": null,
  "operation_count": null,
  "source": "apis.guru",
  "scraped_at": "2026-07-28T18:06:02.869003Z"
}
```

`path_count` and `operation_count` are `null` unless `countEndpoints` is enabled. With it on, e.g. `groundhog-day.com` returns `path_count: 5, operation_count: 5`.

Provider mode items:

```json
{ "type": "provider", "provider": "googleapis.com", "api_count": 281, "source": "apis.guru", "scraped_at": "..." }
```

All fields are nullable — the upstream directory is community-maintained and not every API ships a license, contact or category.

### Pricing

Roughly **$0.5 per 1,000 items** on Apify compute. The directory is a single 8 MB JSON download, so a full 2,500-API run without enrichment finishes in well under a minute. Enabling `countEndpoints` adds one HTTP request per API — keep `maxItems` low when you use it.

### Notes & limits

- Data comes from the public `https://api.apis.guru/v2/` endpoints; APIs.guru is community-run and specs may lag behind the provider.
- Specs larger than 8 MB are skipped during enrichment (counts stay `null`).
- `is_unofficial: true` marks the ~25 specs APIs.guru maintains without the provider's blessing.
- The actor only reads public, non-personal metadata.

### Related actors

- [public-apis-scraper](https://apify.com/ninhothedev/public-apis-scraper) — the curated public-apis markdown list
- [github-repos-scraper](https://apify.com/ninhothedev/github-repos-scraper) — repo metadata, stars and topics
- [software-eol-scraper](https://apify.com/ninhothedev/software-eol-scraper) — end-of-life and support windows
- [deps-dev-scraper](https://apify.com/ninhothedev/deps-dev-scraper) — package dependency and security data

### Local development

```bash
pip install -r requirements.txt
python -m src.main
python tests/test_smoke.py   # offline, stdlib only
```

# Actor input Schema

## `mode` (type: `string`):

What to scrape. 'apis' returns the full APIs.guru OpenAPI directory (one item per API, with spec URLs and metadata). 'providers' returns the provider list with the number of APIs each provider publishes.

## `providerFilter` (type: `string`):

Optional. Keep only APIs of one provider, e.g. 'azure.com', 'googleapis.com', 'amazonaws.com', 'twilio.com'. Matches the x-providerName field or the API id prefix. In 'providers' mode it filters the provider names by substring.

## `categoryFilter` (type: `string`):

Optional. Keep only APIs tagged with this APIs.guru category, e.g. 'cloud', 'financial', 'developer\_tools', 'ecommerce', 'media', 'open\_data', 'messaging'. Case-insensitive substring match. Ignored in 'providers' mode.

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

Optional. Case-insensitive substring search across the API id, title and description, e.g. 'payment', 'weather', 'kubernetes'. In 'providers' mode it searches the provider name.

## `countEndpoints` (type: `boolean`):

Optional. When enabled, the actor downloads each API's preferred OpenAPI spec and counts the paths and HTTP operations inside it, filling path\_count and operation\_count. This is one extra request per API and specs can be multiple MB, so runs are much slower and more expensive. When disabled, both counts stay null.

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

Maximum number of items (APIs or providers) to push to the dataset. Use a small number together with countEndpoints to keep runs fast.

## Actor input object example

```json
{
  "mode": "apis",
  "providerFilter": "azure.com",
  "categoryFilter": "cloud",
  "searchQuery": "payment",
  "countEndpoints": false,
  "maxItems": 500
}
```

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("ninhothedev/openapi-directory-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 = {}

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

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

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

```

## CLI example

```bash
echo '{}' |
apify call ninhothedev/openapi-directory-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=ninhothedev/openapi-directory-scraper",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/dZR1ql3QHCQFamq2B/builds/x99St9QswOzWTXCfb/openapi.json