APIs.guru Directory Scraper
Pricing
from $7.69 / 1,000 results
APIs.guru Directory Scraper
Scrapes the APIs.guru public API directory and returns each API as a flat row with its title, description, provider, category, and OpenAPI spec URL. Filter by provider, category, or free-text search term.
Pricing
from $7.69 / 1,000 results
Rating
0.0
(0)
Developer
ParseForge
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
4 days ago
Last modified
Categories
Share
APIs.guru Directory Scraper
Scrape the APIs.guru directory to discover and list every public API, filtered by provider, category, or search term. Each row returns the API title, description, version, provider, and the link to its machine-readable OpenAPI spec. Export to JSON, CSV, Excel, or XML.
Finding which public APIs exist for a domain, provider, or keyword means manually browsing the APIs.guru directory or stitching together API calls. This Actor reads the full directory listing directly, lets you filter by provider name, category tag, or a free-text search term, and returns every matching API in one flat dataset. No API key or registration required.
| Who uses it | What they scrape APIs.guru for |
|---|---|
| Integration engineers | Build a shortlist of every API a specific provider offers before starting a PoC. |
| API platform teams | Audit which OpenAPI specs are available across a category like machine_learning or cloud. |
| Developer-tool founders | Compile a market map of public APIs in a niche to spot gaps or partnership targets. |
| Data journalists | Track how the number and type of public APIs from a sector changes over time. |
What it does
This Actor collects public API directory entries from APIs.guru and returns each one as a flat row with its title, description, provider, category, and OpenAPI spec URL.
- 🔍 Free-text search: filter the directory by API title, provider name, or description with a case-insensitive search term.
- 🏷️ Category filter: restrict results to a single APIs.guru category, such as cloud, financial, developer_tools, or machine_learning.
- 🏢 Provider filter: list every API published by one provider, for example googleapis.com, amazonaws.com, or azure.com.
- 📦 Bulk export: collect up to a million API entries in one run and download as JSON, CSV, Excel, or XML.
Results export to CSV, JSON, Excel, or XML, or straight from the API.
What you can do with APIs.guru data
📋 Audit a provider's public API surface.
An integration engineer sets the provider filter to 'stripe.com' and exports every listed API to plan a unified client library.
🧠 Build a machine-learning API landscape.
A platform team filters by the 'machine_learning' category and collects all entries to evaluate which specs are complete enough for automated SDK generation.
📊 Monitor the public API ecosystem.
A data journalist runs the Actor weekly with no filters, diffs the dataset, and reports on which sectors are growing fastest.
🔗 Enrich an internal API catalog.
A developer-tool founder scrapes the full directory, matches entries against their own registry, and pulls in missing OpenAPI spec URLs for import.
Why choose this scraper
| What you get | |
|---|---|
| One flat row per API | Title, description, version, provider, category, and the direct OpenAPI spec URL. |
| No API key needed | Reads the public directory listing directly, no registration or OAuth. |
| Full-directory scans | Leave all filters empty to collect every API in the directory in one run. |
| Structured output | Export to JSON, CSV, Excel, or XML for direct use in spreadsheets, databases, or notebooks. |
How it compares
Three other Apify actors also scrape the APIs.guru directory. This one focuses on returning the directory listing itself as clean, filterable metadata rows without downloading or parsing the full spec files.
| Feature | ParseForge | OpenAPI Spec Scraper - APIs to LLM Agent Tools (MCP-Ready) | OpenAPI Directory & API Specs Scraper (APIs.guru) | APIs.guru Scraper - Public API Directory Data |
|---|---|---|---|---|
| Directory metadata (title, description, provider, category) | Yes | Not listed | Yes | Yes |
| OpenAPI spec URL per API | Yes | Not listed | Yes | Yes |
| Filter by provider name | Yes | Not listed | Not listed | Not listed |
| Filter by category tag | Yes | Not listed | Not listed | Not listed |
| Free-text search across title, provider, description | Yes | Not listed | Not listed | Not listed |
| Downloads and parses full OpenAPI spec content | Not listed | Yes | Not listed | Not listed |
Configure the run
Drive the Actor with an optional search term, category, and provider name, alone or together, and filters run as each entry is read so only matches reach your dataset. The Input tab lists every parameter.
A first run with the defaults:
A larger pull:
Pricing
Pay-per-result: $0.0085 per result collected. You pay only for the results written to your dataset.
| Results collected | Approximate cost |
|---|---|
| 100 results | $0.85 |
| 1,000 results | $8.50 |
| 10,000 results | $85.00 |
New Apify accounts start with $5 in free credit.
Free users
Free-plan runs return up to 10 results as a preview. Upgrade your Apify plan to collect up to 1,000,000 results per run.
Run it
- Create a free Apify account with $5 in credit.
- Open the APIs.guru Directory Scraper.
- Set your inputs and any filters, then click Start.
- Export the results as CSV, Excel, JSON, or XML from the Dataset tab.
Run it programmatically through the Apify API (run-sync-get-dataset-items) or the ApifyClient for JavaScript and Python.
Use with AI agents (MCP)
Give an AI agent live access to APIs.guru through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:
Then prompt it in plain language to run the scraper and read back the results.
Troubleshooting
Why am I getting zero results?
Check that your search term, category, or provider filter is not too restrictive. Try running with all filters empty first to confirm the directory is reachable, then add filters one at a time.
The run finished but the dataset has fewer rows than I expected.
The directory size is finite. If you set a high maximum but applied filters, only the matching subset is returned. Remove filters to see the full count.
My category filter is not returning any APIs.
Category tags must match the APIs.guru taxonomy exactly. Check the spelling and case, and try a known tag like 'cloud' or 'machine_learning' to verify the filter works.
The run times out or takes too long.
Lower the maximum APIs value. The full directory is a few thousand entries, so a value of 5000 is usually enough and keeps the run fast.
I need the actual OpenAPI spec content, not the URL.
This Actor provides directory metadata only. Use the spec URL from the output as input to an OpenAPI spec scraper that downloads and parses the full specification.
FAQ
| Question | Answer |
|---|---|
| Do I need an APIs.guru account or API key? | No. The Actor reads the public directory listing that APIs.guru provides openly. No registration, authentication, or key is required. |
| What exactly is in each row of the output? | Every row represents one API entry and includes its title, description, version, provider name, category tags, and the URL to its machine-readable OpenAPI specification. |
| Can I get the full OpenAPI spec file, not the URL? | This Actor returns the directory metadata, including the spec URL. To download and parse the actual spec files, use a dedicated OpenAPI spec scraper that fetches and normalizes the content behind those URLs. |
| How do I list every API in the directory? | Leave the search term, category, and provider fields empty and set the maximum APIs high enough to cover the full directory. The Actor will return every entry it finds. |
| What categories can I filter by? | You can use any category tag from the APIs.guru taxonomy, such as cloud, financial, developer_tools, machine_learning, or messaging. The input field accepts the exact tag string. |
| Can I combine filters, like a provider and a search term? | Yes. All provided filters are applied together. If you set a provider and a search term, only APIs from that provider whose metadata matches the term will appear. |
| How many APIs can I collect in one run? | You can set the maximum up to 1,000,000 entries. The directory contains a few thousand APIs, so a single run can easily capture the entire listing. |
| What output formats are supported? | The dataset can be exported as JSON, CSV, Excel, or XML from the Apify platform after the run completes. |
| Does the Actor follow pagination automatically? | Yes. It handles directory pagination internally and stops when it reaches the maximum number of APIs you set or when no more entries are available. |
| Can I schedule this to run daily? | Yes. You can set up a recurring schedule in Apify to run the Actor automatically and track changes in the directory over time. |
Related actors
Browse the full ParseForge collection for more scrapers.
🆘 Need help? Email parseforge@protonmail.com with your run ID, your input, and what you expected.
⚠️ Disclaimer. This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by APIs.guru. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.
