ImportError: cannot import name 'service_container' from 'crawlee'

**Apify now supports agentic payments through x402 protocol** Agents can now pay and run Actors without an account or API token. All they need is to provide a payment payload in the request header. The integration is live on both API and MCP server. For more info, see docs here: https://docs.apify.com/platform/integrations/x402

ellativity · 2w ago

**Confirmation dialog when running full-permission Actors** After launching [Actor permissions](https://docs.apify.com/platform/actors/development/permissions) last year, we're continuing to adopt least-privileged access and stricter defaults to improve security for both users and AI agents. We've seen growing adoption in the community and 70 of the top 100 Actors in Apify Store now use limited permissions. Thank you to everyone who reviewed and migrated their Actors. Full permissions are meant for Actors that genuinely need broad access to perform admin-level tasks on your account, like managing other Actors, runs or accessing account-wide resources. To make sure users understand what access they’re granting, **starting May 4th**, we're introducing a one-time confirmation step for new users of full-permission Actors. **Your existing users are not affected**, this only applies to users who haven’t run the Actor yet. Once approved, the Actor runs as usual with no further prompts. Users get transparency, and Actors that legitimately need full permissions keep working smoothly after the initial approval. **What should you do?** If your public Actor uses full permissions, consider whether it truly needs them. Most scraping, data extraction, and automation Actors work fine with limited permissions. Switching gives you: - Higher Actor Quality Score - Better visibility in Apify Store - No friction for new users or AI agents Migration guide: https://docs.apify.com/platform/actors/development/permissions/migration-guide If your Actor genuinely needs full permissions, that's completely fine. Just know that new users will see the confirmation step before running it, so clearly communicating why it’s needed in the README can help with adoption. Any questions? let us know in <#1090592836044476426>

hurt-tomato · 3w ago

**Update to MCP and CLI search** As from April 1, 2026, Actors that are **not** set to limited permissions will no longer be indexed in API calls, which include MCP and CLI search. The best way to ensure your Actors can be discovered and run via Apify MCP is by updating permissions: https://docs.apify.com/platform/actors/development/permissions For any questions about permissions, please join <#1090592836044476426>

ellativity · 3w ago