Apify serves an AI Catalog
manifest at /.well-known/ai-catalog.json on apify.com, declaring
15 agentic resources
that a discovery service can index without asking anyone’s permission.
Run against this exact body with the project’s own
conformance CLI.
Discovery path
predecessor
Answered only at /.well-known/ai-catalog.json. ARD v0.91 renamed the path to /.well-known/ard.json and made the old one an optional courtesy, so a consumer implementing only the current spec will not find this manifest.
Declared spec version
1.0
The specVersion in the manifest. 1.0 is current for the AI Catalog data model; anything lower is an earlier draft. ARD reads this field as transport-defined and ignores it.
Optional affordances missing. None of these break a client, but each one costs the publisher search relevance or verifiability.
entry-no-representativeQueries
host-identifier-not-did-web
15 entries
7 media types
18 representative queries
15 trust manifests
Host identifier: apify.com
What this manifest advertises
Apify MCP server
urn:air:apify.com:mcp:apify
The hosted MCP server for Apify, the largest marketplace of trusted tools for AI. Search thousands of ready-to-run tools called Actors, read what one takes as input, run it, and read the structured web data it returns.
Search endpoint over the 68,000+ Actors published on Apify Store. Query by the platform or product a tool works with rather than the end goal, filter by category or pricing model, and get back the tools that do the job.
“find a ready-made tool that collects product data from an online store”
“which Apify tool extracts data from Google Maps”
Apify agent quickstart (agents.md)
urn:air:apify.com:doc:agent-quickstart
Quickstart for an agent integrating Apify: how to connect to the MCP server, the tool sequence from search to data, and the REST routes with the cost caps each one takes.
Index of apify.com in the llmstxt.org format: every main page, use case, support program and agent-facing document, each with one line on what it answers. The homepage serves this document to a client that asks for text/markdown.
How an agent with a wallet buys a prepaid, spend-capped Apify API token through an agentic payment protocol and runs Actors without a human signing up.
“pay for a web scraping API without a human signing up”
“buy a spend-capped token for an API”
apify-actor-development
urn:air:apify.com:skill:apify-actor-development
Develop, debug, and deploy Apify Actors - serverless cloud programs for web scraping, automation, and data processing. Use when creating new Actors, modifying existing ones, or troubleshooting Actor code.
Convert existing projects into Apify Actors - serverless cloud programs. Actorize JavaScript/TypeScript (SDK with Actor.init/exit), Python (async context manager), or any language (CLI wrapper). Use when migrating code to Apify, wrapping CLI tools as Actors, or adding Actor SDK to existing projects.
Generate output schemas (dataset_schema.json, output_schema.json, key_value_store_schema.json) for an Apify Actor by analyzing its source code. Use when creating or updating Actor output schemas.
Design and build an official Apify integration for a company's product - workflow-automation apps (Zapier/n8n-style), AI agent plugins (coding-agent skills+MCP bundles or OpenClaw/Hermes-style harnesses), AI framework packages (LangChain/LlamaIndex-style), or direct application clients via apify-client. Use when planning, creating, or reviewing an integration that exposes Apify Actors, runs, datasets, or key-value stores inside another product.
Universal AI-powered web scraper for any platform. Scrape data from Instagram, Facebook, TikTok, YouTube, LinkedIn, X/Twitter, Google Maps, Google Search, Google Trends, Reddit, Airbnb, Yelp, and 15+ more platforms. Use for lead generation, brand monitoring, competitor analysis, influencer discovery, trend research, content analytics, audience analysis, review analysis, SEO intelligence, recruitment, or any data extraction task.
The publishing guide asks for three things at the transport layer, because a crawler is the
consumer that matters and a crawler is a browser-shaped client.
HTTPS only — yes (HTTP 200)
Content-Type: application/json —
no — serves application/ai-catalog+json
Access-Control-Allow-Origin: * —
yes
Evidence. Fetched https://apify.com/.well-known/ai-catalog.json on 2026-09-13, HTTP
200. The verbatim body is stored alongside its manifest in the
Apify repository
as ai-catalog/apify-ai-catalog.json. Nothing on this page is derived
or generated: an AI Catalog manifest is served from the publisher’s own domain or it does not
exist, which makes it — like an
A2A Agent Card — one of the few agent artifacts that cannot be
produced on a provider’s behalf. Grades are recomputed on every build; the specification is a
v0.9 draft and
these verdicts will move when it does.
Every descriptor here is available over the APIs.io API and to AI agents over MCP. Agent Discovery is not yet its own endpoint on the v1 API. Reach it through catalog search and the tag graph, or the MCP server.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for agent discovery
3 MCP tools reach this
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.