# Apify — API Agent Score

> Score: 86/100 (Grade: A) | Domain: apify.com | Rubric: 1.0.0 | Checked: July 24, 2026

Apify scored 86/100 (A), classified "ai-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/apify)
[All organizations](https://www.postman.com/ai/ai-ready-apis/llms.txt)

## Summary

- Overall: 86/100 (A)
- Classification: ai-ready

## Category Scores

- API Design: 96/100 (A+)
- Developer Experience: 83/100 (A)
- Agent Discovery: 91/100 (A+)
- Agent Understanding: 73/100 (B)
- Agent Usability: 86/100 (A)

## Check Results

### API Design

- [warn] Schema coverage & depth — 8 of 268 public signatures use loose types (anyTypeRatio=0.030). Investigated: sdk 91%.
- [pass] Security & governance hygiene — security.txt valid at https://apify.com/.well-known/security.txt (Contact + unexpired Expires). Investigated: wellknown 100%.
- [pass] Example coverage — Code samples in 3 language(s) across docs (top: javascript, shell, python); 3/20 pages have ≥ 2 languages on the same page. Investigated: docs 100%, sdk 100%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Auth declared & discoverable — No surface produced evidence for this capability in this run.

### Developer Experience

- [pass] Self-service developer portal — Signup page at https://console.apify.com/sign-up; no free-tier language detected in docs/pricing. Investigated: docs 100%.
- [pass] Code samples in docs — Code samples in 3 language(s) across docs (top: javascript, shell, python); 3/20 pages have ≥ 2 languages on the same page. Investigated: docs 100%.
- [pass] Changelog published — Newest official SDK activity 0 day(s) ago. Investigated: sdk 100%.
- [warn] Quickstart present — Quickstart page reachable (1 variants scanned starting at https://docs.apify.com/get-started) but no runnable code sample detected in HTML or .md variant. Investigated: docs 50%.
- [warn] Description completeness — 67/146 operations lack a description. Investigated: sdk 54%.

### Agent Discovery

- [pass] Docs reachable, not hard auth-gated — All 50 sampled pages are publicly accessible. Investigated: docs 100%.
- [pass] Registry & SDK presence — Indexed on Context7 (apify/apify-docs, 4920 snippets). Investigated: docs 100%, cli 100%, mcp 100%, sdk 67%, wellknown 0%.
- [warn] llms.txt present, valid & comprehensive — llms.txt covers 406/3883 sitemap doc pages (10%); 3477 missing; 8 llms.txt links not in sitemap (may indicate stale links or incomplete sitemap). Investigated: docs 75%, sdk 0%.
- [warn] Crawlable / AEO — Sitemap present (6 entries) but carries no lastmod values. Investigated: wellknown 75%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — 6 of 50 pages have substantive content differences between markdown and HTML (avg 6% missing). Investigated: docs 78%.
- [pass] Agent instructions file (AGENTS.md) — Agent instructions file found at https://apify.com/AGENTS.md. Investigated: wellknown 100%.
- [fail] Docs structured data — Neither JSON-LD nor OpenGraph/meta tags detected across 2 assessed pages (2 JS-rendered). Investigated: docs 0%.
- [skip] Machine-readable errors (RFC 9457) — No surface produced evidence for this capability in this run.
- [skip] Operation purpose clarity — No surface produced evidence for this capability in this run.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [pass] Idempotency documented — Built-in retry machinery is present (grep-derived). Investigated: sdk 100%.
- [pass] Sandbox separation — Sandbox environments are exposed (sandbox). Investigated: sdk 100%.
- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Rate-limit signaling — No surface produced evidence for this capability in this run.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.

## Executive Summary

Apify's API program shows strong fundamentals across design, onboarding, and discoverability — partners can find and evaluate the APIs with relative ease. The two areas that need immediate attention are agent-readiness of documentation and the absence of runnable, test-backed collections: without structured, machine-parseable docs and executable examples, AI agents building on Apify's platform are forced to guess at request shapes and workflow patterns, slowing integrations and increasing support burden. Closing these two gaps will make the program genuinely self-serve for both human partners and the AI agents they deploy.