Apify
Apify is rebuilding the Actor platform as MCP-first agent infrastructure.
◆Recent moves
- 2d ago
New Actor creation flow
- 3d ago
Publish tasks for your Actor to get more users
Published tasks give each Actor task its own search-indexed Store page, extending Apify's discovery surface from the Actor itself down to specific, long-tail use cases. It is a distribution play aimed at both search engines and AI agents, consistent with the platform's agent-readable direction.
- 18d ago
MCP connectors are live. Actors now work where you do.
⚡ SPARKMCP connectors close the biggest gap in Apify's agent story: Actors could only touch the open web, but can now act inside authenticated apps like Notion, Slack, and GitHub without ever seeing credentials. This is the load-bearing piece of the agent-infrastructure arc.
- 1mo ago
Interactive OpenAPI documentation for standby Actors
Standby Actors that ship an OpenAPI spec now expose an Endpoints tab with live, authenticated request execution in the browser. It is part of making Actors legible and callable — the same instinct behind the MCP work, applied to documentation.
View source ↗ - 1mo ago
Full-permission Actors now require approval
A one-time confirmation gate for full-permission Actors tightens defaults across Console, API, CLI, schedules, and webhooks. Framed around least privilege for users and AI agents, it is the security counterweight to Apify's push to let agents invoke unfamiliar Actors.
View source ↗ - 2mo ago
Multiple datasets for Actors
Actors can now write to multiple schema-validated datasets per run, letting creators separate clean output from debug data. A structural improvement to how Actor output is organized rather than a directional shift.