Apify clone
Actor runs, datasets, and key-value stores for scraping agents. Error responses use recorded fixture shapes — no live API calls.
Clone ID: apify · Tier: fixture · Binary: clones-fixture
Start here
| Question | Answer |
|---|---|
| Best for | Agents that launch Apify actors, poll run status, and read dataset output. |
| Connect with | Route mode for api.apify.com, REST at {base}/apify/api/..., hosted https://{sessionId}.clones.molar.it/apify/api, or MCP molar_clone_spawn |
| Known limits | Recorded responses only; unimplemented paths return 501; read-only by default unless promoted stateful |
| Seeds | empty — apply on spawn or via molar_clone_seed |
MCP tools
Fixture clones use shared control-plane tools — no vendor-specific MCP surface.
| Tool | Description |
|---|---|
molar_clone_spawn | Spawn fixture session (kind: "apify", optional seed) |
molar_clone_seed | Apply a named seed to an existing session |
molar_clone_route | Map api.apify.com to the active session |
molar_clone_stop | Tear down the session |
See MCP server for world_snapshot, world_restore, and cross-clone tools.
REST API coverage
The clone handles these recorded endpoints (local base http://localhost:8000/apify/api):
GET /v2/actsGET /v2/acts/act_8a7b6c5d/runs/run_i9j8k7l6GET /v2/datasetsGET /v2/key-value-storesPOST /v2/acts/act_8a7b6c5d/runs
If your agent calls a path not in this list, the clone returns 501 unimplemented_in_clone and logs the request. Submit missing coverage via the dashboard Developers → 501 request form.
Seeds
| Seed | When to use |
|---|---|
empty | Starting state for minimal / blank workspace scenarios |
molar clones spawn apify --seed empty
Connect
| Mode | URL pattern |
|---|---|
| Local REST | http://localhost:8000/apify/api{path} |
| Hosted REST | https://{sessionId}.clones.molar.it/apify/api{path} |
| Route mode | Point api.apify.com at the clone via molar_clone_route |
| Dashboard | Clones explorer — filter by apify |
Set MOLAR_CLONE_APIFY_URL for BYOC fleets.
See Fixture clones overview and API & SDK.