apify.com
apify.com
43
agent-friendly
Scanned 6/7/2026, 5:02:08 PM
How to access apify.com as an agent
- ○Check for an undocumented developer API
No OpenAPI at the standard paths. Look for /developer, /developers, /docs, /api for hand-authored documentation.
https://apify.com/developers - ○Find the developer signup
No standard OAuth discovery - most sites still have a developer-portal signup. Find the OAuth client registration page on their site.
- ○Publish your own agent identity
Generate an Ed25519 keypair, host a public key directory, sign your HTTP requests (Web Bot Auth), apply to Cloudflare's bots & agents directory if you cross their edge.
https://developers.cloudflare.com/bots/concepts/bot/verified-bots/ - ●Respect robots.txt and Content Signals
Even when you are an approved agent, honor the site's policy preferences. Cache them; refresh weekly.
What we found
| Signal | Status | Evidence | Points |
|---|---|---|---|
| licensed_commercial_access | found Commercial agent-access mechanism detected: https://apify.com/ mentions: rsl. Sites with explicit licensing pathways are the most agent-prepared - they have both access and disintermediation handled. | +30 | |
| llms_txt | found Title: "apify.com" · 11 sections · 64 links | apify.com/llms.txt | +5 |
| agents_md | found 12165 bytes | apify.com/AGENTS.md | +4 |
| robots_allows | found 1 UA rules · sitemap: yes | apify.com/robots.txt | +4 |
Show 11 signals not present
- · llms_full_txt (+3 if found)
- · agents_txt (+6 if found)
- · agents_json (+15 if found)
- · a2a_agent_card (+25 if found)
- · openapi (+18 if found)
- · oauth_discovery (+12 if found)
- · content_signals (+5 if found)
- · ai_plugin_json_legacy (+0 if found)
- · mcp_registry (+25 if found)
- · in_llms_txt_hub (+0 if found)
- · in_agent_friendly_directory (+4 if found)
If you own this site
Concrete moves that would raise apify.com's AgentRank:
- →Publish /agents.txt declaring which agent protocols you support.
- →If you operate an agent, publish /.well-known/agent-card.json so others can discover it.
- →Publish your API as OpenAPI 3.x at a discoverable location.
- →Expose OAuth/OIDC discovery at /.well-known/oauth-authorization-server.