LoginSign Up
← Back to all sparks
A

Apify

ANALYTICS
Velocity7.5

Apify retools Actors for the agentic web — agent payments and login-gated MCP access.

web-scrapingai-agentsagentic-paymentsmcpactor-marketplacepermissions
◆Current state
Apify runs a marketplace of 'Actors' — hosted scrapers and automations — and its recent releases aim squarely at AI agents as the new consumer. Agents can now pay per run in USDC via the x402 protocol with no account, reach login-gated apps through MCP connectors, and discover Actors through SEO-friendly published task pages. In parallel, Apify is tightening Actor permissions as agents run more code on users' behalf.
◆Where it's heading
Apify is repositioning from a developer scraping platform into agent-native infrastructure: making Actors callable, payable, and discoverable by autonomous agents, while adding the permission guardrails that agent-driven execution demands. Security defaults are the necessary counterweight to opening the platform to agents.
◆Prediction
Expect more agent-economy plumbing — broader x402/agentic-payment coverage and more MCP-connected apps — alongside continued least-privilege permission tightening as the default execution model becomes agent-initiated.

◆Recent moves

  1. 7d ago

    Pay for Apify Actors with x402

    ⚡ SPARK

    Per-run agent payments in USDC via x402 — no account, billing, or API key — is the clearest signal of Apify's bet on agents as first-class, autonomous customers of its Actors.

  2. 8d ago

    New Actor creation flow

    A guided creation flow that routes builders to the right template by goal and language reduces choice overload — incremental developer-onboarding polish.

  3. 9d ago

    Publish tasks for your Actor to get more users

    Published task pages give each Actor SEO-indexed, agent-readable example pages — a discovery play that fits Apify's push to be found by both search engines and AI agents.

  4. 24d ago

    MCP connectors are live. Actors now work where you do.

    ⚡ SPARK

    MCP connectors let Actors operate behind logins like Notion, Slack, and GitHub without seeing credentials — extending Actors from the open web into authenticated apps, a major reach expansion.

  5. 1mo ago

    Interactive OpenAPI documentation for standby Actors

    An Endpoints tab with live, token-attached OpenAPI calls for standby Actors makes them easier to test and integrate — incremental developer-experience depth.

    View source ↗
  6. 2mo ago

    Full-permission Actors now require approval

    Requiring one-time human approval for full-permission Actors adds a least-privilege guardrail precisely because agents now run Actors autonomously — security catching up with the agent-first direction.

    View source ↗