1# Apify Actors Development Guide
2
3Important: Before you begin, fill in the `generatedBy` property in the meta section of `.actor/actor.json`. Replace it with the tool and model you're currently using, such as "Claude Code with Claude Sonnet 4.5". This helps Apify monitor and improve AGENTS.md for specific AI tools and models.
4
5## What are Apify Actors?
6
7- Actors are serverless programs that run in the cloud. They're inspired by the UNIX philosophy - programs that do one thing well and can be easily combined to build complex systems.
8- Actors are programs packaged as Docker images that run in isolated containers
9
10## Core Concepts
11
12- Accept well-defined JSON input
13- Perform isolated tasks (web scraping, automation, data processing)
14- Produce structured JSON output to datasets and/or store data in key-value stores
15- Can run from seconds to hours or even indefinitely
16- Persist state and can be restarted
17
18## Do
19
20- accept well-defined JSON input and produce structured JSON output
21- use Apify SDK (`apify`) for code running ON Apify platform
22- validate input early with proper error handling and fail gracefully
23- use CheerioCrawler for static HTML content (10x faster than browsers)
24- use PlaywrightCrawler only for JavaScript-heavy sites and dynamic content
25- use router pattern (createCheerioRouter/createPlaywrightRouter) for complex crawls
26- implement retry strategies with exponential backoff for failed requests
27- use proper concurrency settings (HTTP: 10-50, Browser: 1-5)
28- set sensible defaults in `.actor/input_schema.json` for all optional fields
29- set up output schema in `.actor/output_schema.json`
30- clean and validate data before pushing to dataset
31- use semantic CSS selectors and fallback strategies for missing elements
32- respect robots.txt, ToS, and implement rate limiting with delays
33- check which tools (cheerio/playwright/crawlee) are installed before applying guidance
34- use `apify/log` package for logging (censors sensitive data)
35- implement readiness probe handler for standby Actors
36- handle the `aborting` event to gracefully shut down when Actor is stopped
37
38## Don't
39
40- do not rely on `Dataset.getInfo()` for final counts on Cloud platform
41- do not use browser crawlers when HTTP/Cheerio works (massive performance gains with HTTP)
42- do not hard code values that should be in input schema or environment variables
43- do not skip input validation or error handling
44- do not overload servers - use appropriate concurrency and delays
45- do not scrape prohibited content or ignore Terms of Service
46- do not store personal/sensitive data unless explicitly permitted
47- do not use deprecated options like `requestHandlerTimeoutMillis` on CheerioCrawler (v3.x)
48- do not use `additionalHttpHeaders` - use `preNavigationHooks` instead
49- do not assume that local storage is persistent or automatically synced to Apify Console - when running locally with `apify run`, the `storage/` directory is local-only and is NOT pushed to the Cloud
50- do not disable standby mode (`usesStandbyMode: false`) without explicit permission
51
52## Logging
53
54- **ALWAYS use the `apify/log` package for logging** - This package contains critical security logic including censoring sensitive data (Apify tokens, API keys, credentials) to prevent accidental exposure in logs
55
56### Available Log Levels in `apify/log`
57
58The Apify log package provides the following methods for logging:
59
60- `log.debug()` - Debug level logs (detailed diagnostic information)
61- `log.info()` - Info level logs (general informational messages)
62- `log.warning()` - Warning level logs (warning messages for potentially problematic situations)
63- `log.warningOnce()` - Warning level logs (same warning message logged only once)
64- `log.error()` - Error level logs (error messages for failures)
65- `log.exception()` - Exception level logs (for exceptions with stack traces)
66- `log.perf()` - Performance level logs (performance metrics and timing information)
67- `log.deprecated()` - Deprecation level logs (warnings about deprecated code)
68- `log.softFail()` - Soft failure logs (non-critical failures that don't stop execution, e.g., input validation errors, skipped items)
69- `log.internal()` - Internal level logs (internal/system messages)
70
71**Best practices:**
72
73- Use `log.debug()` for detailed operation-level diagnostics (inside functions)
74- Use `log.info()` for general informational messages (API requests, successful operations)
75- Use `log.warning()` for potentially problematic situations (validation failures, unexpected states)
76- Use `log.error()` for actual errors and failures
77- Use `log.exception()` for caught exceptions with stack traces
78
79## Graceful Abort Handling
80
81Handle the `aborting` event to terminate the Actor quickly when stopped by user or platform, minimizing costs especially for PPU/PPE+U billing.
82
83```javascript
84import { setTimeout } from 'node:timers/promises';
85
86Actor.on('aborting', async () => {
87 // Persist any state, do any cleanup you need, and terminate the Actor using `await Actor.exit()` explicitly as soon as possible
88 // This will help ensure that the Actor is doing best effort to honor any potential limits on costs of a single run set by the user
89 // Wait 1 second to allow Crawlee/SDK useState and other state persistence operations to complete
90 // This is a temporary workaround until SDK implements proper state persistence in the aborting event
91 await setTimeout(1000);
92 await Actor.exit();
93});
94```
95
96## Standby Mode
97
98- **NEVER disable standby mode (`usesStandbyMode: false`) in `.actor/actor.json` without explicit permission** - Actor Standby mode solves this problem by letting you have the Actor ready in the background, waiting for the incoming HTTP requests. In a sense, the Actor behaves like a real-time web server or standard API server instead of running the logic once to process everything in batch. Always keep `usesStandbyMode: true` unless there is a specific documented reason to disable it
99- **ALWAYS implement readiness probe handler for standby Actors** - Handle the `x-apify-container-server-readiness-probe` header at GET / endpoint to ensure proper Actor lifecycle management
100
101You can recognize a standby Actor by checking the `usesStandbyMode` property in `.actor/actor.json`. Only implement the readiness probe if this property is set to `true`.
102
103### Readiness Probe Implementation Example
104
105```javascript
106// Apify standby readiness probe at root path
107app.get('/', (req, res) => {
108 res.writeHead(200, { 'Content-Type': 'text/plain' });
109 if (req.headers['x-apify-container-server-readiness-probe']) {
110 res.end('Readiness probe OK\n');
111 } else {
112 res.end('Actor is ready\n');
113 }
114});
115```
116
117Key points:
118
119- Detect the `x-apify-container-server-readiness-probe` header in incoming requests
120- Respond with HTTP 200 status code for both readiness probe and normal requests
121- This enables proper Actor lifecycle management in standby mode
122
123## Commands
124
125```bash
126# Bootstrap & local development
127apify create [name] # Create new Actor project from a template
128apify init # Initialize Actor in current directory
129apify run # Run Actor locally with simulated platform env
130apify run --purge # Run after clearing previous local storage
131apify validate-schema # Validate .actor/input_schema.json
132
133# Authentication & account
134apify login # Authenticate account (token stored in ~/.apify)
135apify logout # Remove stored credentials
136apify info # Print currently authenticated account info
137
138# Deployment & remote execution
139apify push # Deploy Actor to platform per .actor/actor.json
140apify pull <actor> # Download Actor code from the platform
141apify call <actor> # Execute Actor remotely on the platform
142apify actors build <actor> # Create a new build of an Actor
143apify runs ls # List recent runs
144
145# Discovery (search Apify Store for community Actors)
146apify actors search "<query>" --user-agent <your-agent-name>
147apify actors info <actor> # Details about a specific Actor
148
149# Secrets (referenced from actor.json via "@mySecret")
150apify secrets add <name> <value> # Store a secret locally; uploaded on push
151apify secrets ls # List stored secret keys
152
153# Direct API access
154apify api <endpoint> # Authenticated HTTP request to Apify API
155
156# Help
157apify help # List all commands
158apify <command> --help # Detailed help for a specific command
159```
160
161Note: If no dedicated Actor exists for your target, search Apify Store for community options with `apify actors search "<query>" --user-agent <your-agent-name>` before building from scratch.
162
163Tip: Inside a running Actor, prefer the SDK (`Actor.getInput()`, `Actor.pushData()`, `Actor.setValue()`) over the equivalent `apify actor` runtime subcommands.
164
165## Apify Platform Environment
166
167When the Actor runs on the Apify platform, the API token is automatically available via the `APIFY_TOKEN` environment variable (note: the variable is `APIFY_TOKEN`, not `APIFY_API_TOKEN`). The Apify SDK reads it automatically, so you do not need to pass it explicitly. Locally, run `apify login` once and the SDK will use your stored credentials.
168
169## Safety and Permissions
170
171Allowed without prompt:
172
173- read files with `Actor.getValue()`
174- push data with `Actor.pushData()`
175- set values with `Actor.setValue()`
176- enqueue requests to RequestQueue
177- run locally with `apify run`
178
179Ask first:
180
181- npm/pip package installations
182- apify push (deployment to cloud)
183- proxy configuration changes (requires paid plan)
184- Dockerfile changes affecting builds
185- deleting datasets or key-value stores
186
187## Project Structure
188
189.actor/
190├── actor.json # Actor config: name, version, env vars, runtime settings
191├── input_schema.json # Input validation & Console form definition
192└── output_schema.json # Specifies where an Actor stores its output
193src/
194└── main.js # Actor entry point and orchestrator
195storage/ # Local-only storage for development (NOT synced to Cloud)
196├── datasets/ # Output items (JSON objects)
197├── key_value_stores/ # Files, config, INPUT
198└── request_queues/ # Pending crawl requests
199Dockerfile # Container image definition
200AGENTS.md # AI agent instructions (this file)
201
202## Local vs Cloud Storage
203
204When running locally with `apify run`, the Apify SDK emulates Cloud storage APIs using the local `storage/` directory. This local storage behaves differently from Cloud storage:
205
206- **Local storage is NOT persistent** - The `storage/` directory is meant for local development and testing only. Data stored there (datasets, key-value stores, request queues) exists only on your local disk.
207- **Local storage is NOT automatically pushed to Apify Console** - Running `apify run` does not upload any storage data to the Apify platform. The data stays local.
208- **Each local run may overwrite previous data** - The local `storage/` directory is reused between runs, but this is local-only behavior, not Cloud persistence.
209- **Cloud storage only works when running on Apify platform** - After deploying with `apify push` and running the Actor in the Cloud, storage calls (`Actor.pushData()`, `Actor.setValue()`, etc.) interact with real Apify Cloud storage, which is then visible in the Apify Console.
210- **To verify Actor output, deploy and run in Cloud** - Do not rely on local `storage/` contents as proof that data will appear in the Apify Console. Always test by deploying (`apify push`) and running the Actor on the platform.
211
212## Actor Input Schema
213
214The input schema defines the input parameters for an Actor. It's a JSON object comprising various field types supported by the Apify platform.
215
216### Structure
217
218```json
219{
220 "title": "<INPUT-SCHEMA-TITLE>",
221 "type": "object",
222 "schemaVersion": 1,
223 "properties": {
224 /* define input fields here */
225 },
226 "required": []
227}
228```
229
230### Example
231
232```json
233{
234 "title": "E-commerce Product Scraper Input",
235 "type": "object",
236 "schemaVersion": 1,
237 "properties": {
238 "startUrls": {
239 "title": "Start URLs",
240 "type": "array",
241 "description": "URLs to start scraping from (category pages or product pages)",
242 "editor": "requestListSources",
243 "default": [{ "url": "https://example.com/category" }],
244 "prefill": [{ "url": "https://example.com/category" }]
245 },
246 "followVariants": {
247 "title": "Follow Product Variants",
248 "type": "boolean",
249 "description": "Whether to scrape product variants (different colors, sizes)",
250 "default": true
251 },
252 "maxRequestsPerCrawl": {
253 "title": "Max Requests per Crawl",
254 "type": "integer",
255 "description": "Maximum number of pages to scrape (0 = unlimited)",
256 "default": 1000,
257 "minimum": 0
258 },
259 "proxyConfiguration": {
260 "title": "Proxy Configuration",
261 "type": "object",
262 "description": "Proxy settings for anti-bot protection",
263 "editor": "proxy",
264 "default": { "useApifyProxy": false }
265 },
266 "locale": {
267 "title": "Locale",
268 "type": "string",
269 "description": "Language/country code for localized content",
270 "default": "cs",
271 "enum": ["cs", "en", "de", "sk"],
272 "enumTitles": ["Czech", "English", "German", "Slovak"]
273 }
274 },
275 "required": ["startUrls"]
276}
277```
278
279## Actor Output Schema
280
281The Actor output schema builds upon the schemas for the dataset and key-value store. It specifies where an Actor stores its output and defines templates for accessing that output. Apify Console uses these output definitions to display run results.
282
283### Structure
284
285```json
286{
287 "actorOutputSchemaVersion": 1,
288 "title": "<OUTPUT-SCHEMA-TITLE>",
289 "properties": {
290 /* define your outputs here */
291 }
292}
293```
294
295### Example
296
297```json
298{
299 "actorOutputSchemaVersion": 1,
300 "title": "Output schema of the files scraper",
301 "properties": {
302 "files": {
303 "type": "string",
304 "title": "Files",
305 "template": "{{links.apiDefaultKeyValueStoreUrl}}/keys"
306 },
307 "dataset": {
308 "type": "string",
309 "title": "Dataset",
310 "template": "{{links.apiDefaultDatasetUrl}}/items"
311 }
312 }
313}
314```
315
316### Output Schema Template Variables
317
318- `links` (object) - Contains quick links to most commonly used URLs
319- `links.publicRunUrl` (string) - Public run url in format `https://console.apify.com/view/runs/:runId`
320- `links.consoleRunUrl` (string) - Console run url in format `https://console.apify.com/actors/runs/:runId`
321- `links.apiRunUrl` (string) - API run url in format `https://api.apify.com/v2/actor-runs/:runId`
322- `links.apiDefaultDatasetUrl` (string) - API url of default dataset in format `https://api.apify.com/v2/datasets/:defaultDatasetId`
323- `links.apiDefaultKeyValueStoreUrl` (string) - API url of default key-value store in format `https://api.apify.com/v2/key-value-stores/:defaultKeyValueStoreId`
324- `links.containerRunUrl` (string) - URL of a webserver running inside the run in format `https://<containerId>.runs.apify.net/`
325- `run` (object) - Contains information about the run same as it is returned from the `GET Run` API endpoint
326- `run.defaultDatasetId` (string) - ID of the default dataset
327- `run.defaultKeyValueStoreId` (string) - ID of the default key-value store
328
329## Dataset Schema Specification
330
331The dataset schema defines how your Actor's output data is structured, transformed, and displayed in the Output tab in the Apify Console.
332
333### Example
334
335Consider an example Actor that calls `Actor.pushData()` to store data into dataset:
336
337```javascript
338import { Actor } from 'apify';
339// Initialize the JavaScript SDK
340await Actor.init();
341
342/**
343 * Actor code
344 */
345await Actor.pushData({
346 numericField: 10,
347 pictureUrl: 'https://www.google.com/images/branding/googlelogo/2x/googlelogo_color_92x30dp.png',
348 linkUrl: 'https://google.com',
349 textField: 'Google',
350 booleanField: true,
351 dateField: new Date(),
352 arrayField: ['#hello', '#world'],
353 objectField: {},
354});
355
356// Exit successfully
357await Actor.exit();
358```
359
360To set up the Actor's output tab UI, reference a dataset schema file in `.actor/actor.json`:
361
362```json
363{
364 "actorSpecification": 1,
365 "name": "book-library-scraper",
366 "title": "Book Library Scraper",
367 "version": "1.0.0",
368 "storages": {
369 "dataset": "./dataset_schema.json"
370 }
371}
372```
373
374Then create the dataset schema in `.actor/dataset_schema.json`:
375
376```json
377{
378 "actorSpecification": 1,
379 "fields": {},
380 "views": {
381 "overview": {
382 "title": "Overview",
383 "transformation": {
384 "fields": [
385 "pictureUrl",
386 "linkUrl",
387 "textField",
388 "booleanField",
389 "arrayField",
390 "objectField",
391 "dateField",
392 "numericField"
393 ]
394 },
395 "display": {
396 "component": "table",
397 "properties": {
398 "pictureUrl": {
399 "label": "Image",
400 "format": "image"
401 },
402 "linkUrl": {
403 "label": "Link",
404 "format": "link"
405 },
406 "textField": {
407 "label": "Text",
408 "format": "text"
409 },
410 "booleanField": {
411 "label": "Boolean",
412 "format": "boolean"
413 },
414 "arrayField": {
415 "label": "Array",
416 "format": "array"
417 },
418 "objectField": {
419 "label": "Object",
420 "format": "object"
421 },
422 "dateField": {
423 "label": "Date",
424 "format": "date"
425 },
426 "numericField": {
427 "label": "Number",
428 "format": "number"
429 }
430 }
431 }
432 }
433 }
434}
435```
436
437### Structure
438
439```json
440{
441 "actorSpecification": 1,
442 "fields": {},
443 "views": {
444 "<VIEW_NAME>": {
445 "title": "string (required)",
446 "description": "string (optional)",
447 "transformation": {
448 "fields": ["string (required)"],
449 "unwind": ["string (optional)"],
450 "flatten": ["string (optional)"],
451 "omit": ["string (optional)"],
452 "limit": "integer (optional)",
453 "desc": "boolean (optional)"
454 },
455 "display": {
456 "component": "table (required)",
457 "properties": {
458 "<FIELD_NAME>": {
459 "label": "string (optional)",
460 "format": "text|number|date|link|boolean|image|array|object (optional)"
461 }
462 }
463 }
464 }
465 }
466}
467```
468
469**Dataset Schema Properties:**
470
471- `actorSpecification` (integer, required) - Specifies the version of dataset schema structure document (currently only version 1)
472- `fields` (JSONSchema object, required) - Schema of one dataset object (use JsonSchema Draft 2020-12 or compatible)
473- `views` (DatasetView object, required) - Object with API and UI views description
474
475**DatasetView Properties:**
476
477- `title` (string, required) - Visible in UI Output tab and API
478- `description` (string, optional) - Only available in API response
479- `transformation` (ViewTransformation object, required) - Data transformation applied when loading from Dataset API
480- `display` (ViewDisplay object, required) - Output tab UI visualization definition
481
482**ViewTransformation Properties:**
483
484- `fields` (string[], required) - Fields to present in output (order matches column order)
485- `unwind` (string[], optional) - Deconstructs nested children into parent object
486- `flatten` (string[], optional) - Transforms nested object into flat structure
487- `omit` (string[], optional) - Removes specified fields from output
488- `limit` (integer, optional) - Maximum number of results (default: all)
489- `desc` (boolean, optional) - Sort order (true = newest first)
490
491**ViewDisplay Properties:**
492
493- `component` (string, required) - Only `table` is available
494- `properties` (Object, optional) - Keys matching `transformation.fields` with ViewDisplayProperty values
495
496**ViewDisplayProperty Properties:**
497
498- `label` (string, optional) - Table column header
499- `format` (string, optional) - One of: `text`, `number`, `date`, `link`, `boolean`, `image`, `array`, `object`
500
501## Key-Value Store Schema Specification
502
503The key-value store schema organizes keys into logical groups called collections for easier data management.
504
505### Example
506
507Consider an example Actor that calls `Actor.setValue()` to save records into the key-value store:
508
509```javascript
510import { Actor } from 'apify';
511// Initialize the JavaScript SDK
512await Actor.init();
513
514/**
515 * Actor code
516 */
517await Actor.setValue('document-1', 'my text data', { contentType: 'text/plain' });
518
519await Actor.setValue(`image-${imageID}`, imageBuffer, { contentType: 'image/jpeg' });
520
521// Exit successfully
522await Actor.exit();
523```
524
525To configure the key-value store schema, reference a schema file in `.actor/actor.json`:
526
527```json
528{
529 "actorSpecification": 1,
530 "name": "data-collector",
531 "title": "Data Collector",
532 "version": "1.0.0",
533 "storages": {
534 "keyValueStore": "./key_value_store_schema.json"
535 }
536}
537```
538
539Then create the key-value store schema in `.actor/key_value_store_schema.json`:
540
541```json
542{
543 "actorKeyValueStoreSchemaVersion": 1,
544 "title": "Key-Value Store Schema",
545 "collections": {
546 "documents": {
547 "title": "Documents",
548 "description": "Text documents stored by the Actor",
549 "keyPrefix": "document-"
550 },
551 "images": {
552 "title": "Images",
553 "description": "Images stored by the Actor",
554 "keyPrefix": "image-",
555 "contentTypes": ["image/jpeg"]
556 }
557 }
558}
559```
560
561### Structure
562
563```json
564{
565 "actorKeyValueStoreSchemaVersion": 1,
566 "title": "string (required)",
567 "description": "string (optional)",
568 "collections": {
569 "<COLLECTION_NAME>": {
570 "title": "string (required)",
571 "description": "string (optional)",
572 "key": "string (conditional - use key OR keyPrefix)",
573 "keyPrefix": "string (conditional - use key OR keyPrefix)",
574 "contentTypes": ["string (optional)"],
575 "jsonSchema": "object (optional)"
576 }
577 }
578}
579```
580
581**Key-Value Store Schema Properties:**
582
583- `actorKeyValueStoreSchemaVersion` (integer, required) - Version of key-value store schema structure document (currently only version 1)
584- `title` (string, required) - Title of the schema
585- `description` (string, optional) - Description of the schema
586- `collections` (Object, required) - Object where each key is a collection ID and value is a Collection object
587
588**Collection Properties:**
589
590- `title` (string, required) - Collection title shown in UI tabs
591- `description` (string, optional) - Description appearing in UI tooltips
592- `key` (string, conditional) - Single specific key for this collection
593- `keyPrefix` (string, conditional) - Prefix for keys included in this collection
594- `contentTypes` (string[], optional) - Allowed content types for validation
595- `jsonSchema` (object, optional) - JSON Schema Draft 07 format for `application/json` content type validation
596
597Either `key` or `keyPrefix` must be specified for each collection, but not both.
598
599## Actor README
600
601**Always generate a README.md file as part of Actor development.** The README is the Actor's public landing page on Apify Store - it serves as SEO, first impression, documentation, and support page combined.
602
603### Required: Generate README automatically
604
605When building an Actor, always create a `README.md` in the project root. Do not wait for the user to ask for it. The README is a critical part of a complete Actor.
606
607### README structure
608
609Write in Markdown. Use H2 (`##`) for main sections (these become the table of contents) and H3 (`###`) for subsections. Do not use H1 - the Actor name is automatically the H1. Aim for at least 300 words.
610
611Include these sections in order:
612
6131. **What does [Actor name] do?** - 2-3 sentences explaining what it does, what data it extracts, and how to try it. Link to the target website. Mention Apify platform advantages (API access, scheduling, integrations, proxy rotation, monitoring).
6142. **Why use [Actor name]?** - Business use cases and benefits.
6153. **How to use [Actor name]** - Numbered step-by-step tutorial. Keep it simple and reassuring.
6164. **Input** - Describe input fields. Reference the Input tab. Optionally include a screenshot or JSON example of the input schema.
6175. **Output** - Show a simplified JSON output example. Mention "You can download the dataset in various formats such as JSON, HTML, CSV, or Excel."
6186. **Data table** - If the Actor extracts data, include a table of the main data fields it outputs.
6197. **Pricing / Cost estimation** - Set expectations on cost. Mention free tier limits if applicable. Frame as "How much does it cost to scrape [target site]?"
6208. **Tips or Advanced options** - How to optimize runs, limit compute units, improve speed or accuracy.
6219. **FAQ, disclaimers, and support** - Legality disclaimer for scrapers, known limitations, link to Issues tab for feedback, mention custom solution availability.
622
623### README best practices
624
625- Write SEO-friendly headings with relevant keywords (e.g., "How to scrape [site] data" not just "Tutorial")
626- Bold the most important words in the intro
627- The first 25% of the README matters most - front-load the value proposition
628- Match the tone to the target audience: simple language for no-code users, technical details for developers
629- Include a JSON output example showing 1-2 representative items
630- Reference these top Actors for README best practices: https://apify.com/apify/instagram-scraper and https://apify.com/compass/crawler-google-places
631- Embed YouTube video URLs on their own line (Apify Console auto-renders them)
632- Use HTML for image sizing if needed; CSS is not supported
633
634## MCP Tools
635
636### Apify MCP
637
638If the Apify MCP server is configured, use these tools for documentation:
639
640- `search-apify-docs` - Search documentation
641- `fetch-apify-docs` - Get full doc pages
642
643Otherwise, reference: `@https://mcp.apify.com/`
644
645### Playwright MCP (debugging)
646
647The Playwright MCP server is a useful tool for debugging Actors that interact with the web - it lets the agent drive a real browser to inspect pages, capture selectors, and reproduce issues.
648
649Install with the Claude Code CLI:
650
651```bash
652claude mcp add playwright npx @playwright/mcp@latest
653```
654
655Or add it manually to your MCP config:
656
657```json
658{
659 "mcpServers": {
660 "playwright": {
661 "command": "npx",
662 "args": ["@playwright/mcp@latest"]
663 }
664 }
665}
666```
667
668## Resources
669
670- [docs.apify.com/llms.txt](https://docs.apify.com/llms.txt) - Quick reference
671- [docs.apify.com/llms-full.txt](https://docs.apify.com/llms-full.txt) - Complete docs
672- [crawlee.dev](https://crawlee.dev) - Crawlee documentation
673- [whitepaper.actor](https://raw.githubusercontent.com/apify/actor-whitepaper/refs/heads/master/README.md) - Complete Actor specification
