This release is a pre-release and may not be stable for production use.
strands-apify
Apify tools for the Strands Agents SDK - web scraping, social media, search, and automation.
This package gives Strands agents access to Apify Actors: serverless cloud programs that scrape websites, social platforms, search engines, and e-commerce sites, returning structured JSON or Markdown.
Installation
Requires Python 3.11 or newer.
pip install strands-apify
Set your Apify token:
export APIFY_TOKEN=your_apify_token_here
Get a token at Apify Console > Settings > API & Integrations.
Quick start
from strands import Agent
from strands_apify import APIFY_CORE_TOOLS
agent = Agent(tools=APIFY_CORE_TOOLS)
result = agent("Scrape https://example.com and summarize it.")
Or register specific tools:
from strands import Agent
from strands_apify import apify_web_fetch, apify_google_search_scraper
agent = Agent(tools=[apify_web_fetch, apify_google_search_scraper])
Convenience presets:
APIFY_CORE_TOOLS- generic Actor/task/dataset tools and single-page fetchAPIFY_SOCIAL_TOOLS- Instagram, LinkedIn, Twitter/X, TikTok, FacebookAPIFY_SEARCH_TOOLS- Google Search, Google Maps, YouTube, multi-page crawler, e-commerceAPIFY_ALL_TOOLS- everything (use sparingly; many tools may overwhelm an LLM's tool choice)
Tools
Core tools
Generic Apify platform access - run any Actor, run saved tasks, fetch dataset items, and fetch a single web page.
| Tool | What it does |
|---|---|
apify_run_actor |
Run any Apify Actor by id with custom input; returns run metadata |
apify_get_dataset_items |
Fetch items from an Apify dataset with pagination |
apify_run_actor_and_get_dataset |
Run an Actor and fetch its default dataset in one step |
apify_run_task |
Run a saved Actor task |
apify_run_task_and_get_dataset |
Run a task and fetch its dataset in one step |
apify_web_fetch |
Fetch a single URL via the Web Fetch Actor, return Markdown, HTML, text, links or raw content |
apify_scrape_url |
Deprecated, use apify_web_fetch. Not in APIFY_CORE_TOOLS; import it directly if you still need it |
from strands_apify import apify_web_fetch, apify_run_actor_and_get_dataset
# Single URL
apify_web_fetch(url="https://example.com", formats=["markdown", "links"])
# Any Actor with custom input
apify_run_actor_and_get_dataset(
actor_id="apify/website-content-crawler",
run_input={"startUrls": [{"url": "https://docs.example.com"}], "maxCrawlPages": 5},
)
Social media tools
Scrape structured data from popular social platforms.
| Tool | Platform | Actor |
|---|---|---|
apify_instagram_scraper |
Instagram (profiles, posts, hashtags, places) | apify/instagram-scraper |
apify_linkedin_profile_posts |
LinkedIn profile posts | apimaestro/linkedin-profile-posts |
apify_linkedin_profile_search |
LinkedIn profile search | harvestapi/linkedin-profile-search |
apify_linkedin_profile_detail |
LinkedIn profile details | apimaestro/linkedin-profile-detail |
apify_twitter_scraper |
Twitter/X (search, handles, URLs) | apidojo/twitter-scraper-lite |
apify_tiktok_scraper |
TikTok (search, hashtags, profiles, URLs) | clockworks/tiktok-scraper |
apify_facebook_posts_scraper |
Facebook page posts | apify/facebook-posts-scraper |
from strands_apify import apify_twitter_scraper, apify_linkedin_profile_search
apify_twitter_scraper(search_query="from:NASA min_faves:100", results_limit=30)
apify_linkedin_profile_search(
search_query="software engineer",
locations=["San Francisco"],
profile_scraper_mode="Full",
)
Search & crawling tools
Search engines, maps, video, multi-page crawls, and e-commerce.
| Tool | What it does | Actor |
|---|---|---|
apify_google_search_scraper |
Google search (organic, ads, People Also Ask) | apify/google-search-scraper |
apify_google_places_scraper |
Google Maps places and reviews | compass/crawler-google-places |
apify_youtube_scraper |
YouTube search and video/channel URLs | streamers/youtube-scraper |
apify_website_content_crawler |
Multi-page website crawl with Markdown extraction | apify/website-content-crawler |
apify_ecommerce_scraper |
Product data from Amazon, eBay, Walmart, etc. | apify/e-commerce-scraping-tool |
from strands_apify import apify_google_search_scraper, apify_website_content_crawler
apify_google_search_scraper(search_query="best AI frameworks 2025", country_code="us")
apify_website_content_crawler(
start_url="https://docs.example.com",
max_pages=20,
max_depth=3,
)
Configuration
| Variable | Description | Required |
|---|---|---|
APIFY_TOKEN |
Your Apify token from console.apify.com | Yes |
STRANDS_APIFY_QUIET |
Set to 1 to suppress the rich panels printed on each tool call. Panels are auto-suppressed in non-interactive environments (CI, Docker, web services); use this flag to silence them in interactive shells too. |
No |
STRANDS_APIFY_MAX_TIMEOUT_SECS |
Ceiling for timeout_secs. Default 600. |
No |
STRANDS_APIFY_MAX_ITEMS |
Ceiling for limit, dataset_items_limit, results_limit, search_limit, max_reviews and max_pages. Default 1000. LinkedIn profile posts stays at its own 100 unless this is set lower. |
No |
STRANDS_APIFY_MAX_CRAWL_DEPTH |
Ceiling for max_depth. Default 5. |
No |
STRANDS_APIFY_MAX_MEMORY_MBYTES |
Ceiling for memory_mbytes. Default and maximum 32768; it can only be lowered. |
No |
Limits on agent-supplied values
The agent picks numeric parameters itself, so every tool caps them before calling Apify: a request for a million
results or a day-long run is cut to the ceiling above. Timeouts, item limits and depths below the ceiling are passed
through unchanged. memory_mbytes is always snapped to the power of 2 the platform requires (1000 becomes 1024) and is
at least 128, even when the memory ceiling is set lower. Each tool description tells the model its ceilings, e.g.
(clamped to 1000 max by default).
timeout_secs is the Actor run's own time limit, so a capped run is stopped after 600 seconds. Raise
STRANDS_APIFY_MAX_TIMEOUT_SECS for long crawls. To page through more than 1000 dataset items, call
apify_get_dataset_items with offset.
Contributing
See CONTRIBUTING.md for development setup and guidelines.
License
Apache-2.0
References
Metadata
Release files for strands-apify 0.1.3b2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| strands_apify-0.1.3b2.tar.gz | 44.3 kB | With provenance | Details for strands_apify-0.1.3b2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| strands_apify-0.1.3b2-py3-none-any.whl | Python 3 | none | any | Details for strands_apify-0.1.3b2-py3-none-any.whl |
Total release size: 71.2 kB
Release files / strands_apify-0.1.3b2.tar.gz
| Download URL | strands_apify-0.1.3b2.tar.gz |
|---|---|
| Size | 44.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9ec337eaaf4fab449e6904550b1e37d7c6c08a557ef181eef6c05de971980a60
|
|
BLAKE2b-256 checksum How to use checksums |
634a32be2d126a876ce6412346202dcf9d034f780e78e22b847925fb39835733
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logRelease files / strands_apify-0.1.3b2-py3-none-any.whl
| Download URL | strands_apify-0.1.3b2-py3-none-any.whl |
|---|---|
| Size | 27.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3cfe1cc57f4da0b3c5514eafa2dd8aa88f50afc394857295595a099fcc9c4044
|
|
BLAKE2b-256 checksum How to use checksums |
51f34809ceca4dbf601365bea135bfd05eb39ee91dee222669a7ff3e3f7e95f9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logSecurity for strands-apify 0.1.3b2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for strands_apify-0.1.3b2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.