mirror of
https://github.com/crewAIInc/crewAI.git
synced 2026-07-01 13:18:10 +00:00
* feat: adopt directory-based docs versioning with Edge channel Switch docs.crewai.com from navigation-only versioning (every version selector entry rendered the same docs/<lang>/* source files) to Mintlify's directory-based versioning so each version selector entry renders its own snapshot. Add an "Edge" channel under docs/edge/<lang>/* that always reflects main HEAD for unreleased work, eliminating pre-release leakage onto frozen release labels. External links to canonical /<lang>/* URLs are preserved via wildcard redirects that always land on the current default version. Layout: - docs/edge/<lang>/* rolling source (you edit here) - docs/edge/enterprise-api.*.yaml - docs/v<X.Y.Z>/<lang>/* frozen, immutable snapshots - docs/v<X.Y.Z>/enterprise-api.*.yaml - docs/images/ shared, append-only - docs/docs.json nav + redirects URLs follow the Mintlify-idiomatic shape: /edge/<lang>/<page> for Edge, /v<X.Y.Z>/<lang>/<page> for every frozen snapshot. The wildcard redirects /<lang>/:slug* -> /<default>/<lang>/:slug* keep stale links working, and every freeze rewrites them (plus all per-section/per-page redirects) so destinations always resolve to the current default without depending on a second redirect hop. Release flow integration (devtools release): - New module crewai_devtools.docs_versioning.freeze() materialises docs/v<X.Y.Z>/ from docs/edge/, rewrites openapi: refs inside the snapshot, inserts the version into every language block in docs.json, and refreshes all redirect destinations. - _update_docs_and_create_pr() in cli.py now calls that freeze during Phase 2 of devtools release. Edge changelogs are updated first (so the snapshot freeze picks them up), then the snapshot is staged alongside docs.json, branched as docs/freeze-v<X.Y.Z>, and the PR is titled [docs-freeze] docs: snapshot and changelog for v<X.Y.Z> — the title prefix the new CI guard reads. - The PR still gates tag, GitHub release, PyPI publish, and the enterprise release as before; no new PRs are added. - Pre-releases (1.X.YaN, 1.X.YbN, ...) skip the snapshot — they ride Edge — and the docs PR title omits the [docs-freeze] prefix. - docs_check (AI-generated docs scaffolding) writes to docs/edge/<lang>/* so newly-generated unreleased docs land in Edge and never accidentally touch a frozen snapshot. Migration scripts (one-shot): - scripts/docs/freeze_historical_versions.py reconstructs all 16 historical snapshots (v1.10.0 .. v1.14.7) from git tags via git archive | tar, rewriting openapi: MDX refs so each snapshot reads its own enterprise-api YAML rather than the live one. - scripts/docs/prefix_version_paths.py one-shot-migrates docs.json: rewrites every page path in 16 versioned blocks to point under docs/v<X.Y.Z>/, inserts a new Edge entry per language, tags v1.14.7 as Latest (default), prunes pages whose target file doesn't exist in the snapshot (e.g. docs/ar/ didn't exist before v1.12.0), and writes the wildcard + per-section redirects. - scripts/docs/freeze_current_edge.py is now a thin CLI wrapper around docs_versioning.freeze for manual one-off freezes (e.g. retroactively snapshotting a forgotten release). CI guards (.github/workflows/docs-snapshots.yml): - Frozen snapshots under docs/v[0-9]*/ are immutable; only PRs whose title contains [docs-freeze] (i.e. release-cut PRs generated by devtools release or the manual wrapper) may modify them. - Images under docs/images/ are append-only since snapshots share a single image directory. Deleting or renaming an image breaks every historical snapshot that still references it. Restored docs/images/crewai-otel-export.png from PR #3673; it was deleted in PR #4908 but v1.10.0 / v1.10.1 snapshots still reference it. Restoring instead of editing the snapshots preserves historical rendering fidelity and validates the new append-only rule retroactively. Tests: - lib/devtools/tests/test_docs_versioning.py covers the freeze: file copy, openapi rewrite, version insertion, default demotion, redirect upserts, per-section redirect rewriting, idempotency, and invalid inputs. Verified locally with mintlify broken-links: 0 broken links across the full site (Edge + 16 frozen versions, 4 locales). AGENTS.md (repo root) is the contributor guide for the new model; RELEASING.md is the release-cut runbook; README's Contribution section links to both. Co-authored-by: Cursor <cursoragent@cursor.com> * style: resolve linter issues --------- Co-authored-by: Cursor <cursoragent@cursor.com>
197 lines
7.2 KiB
Plaintext
197 lines
7.2 KiB
Plaintext
---
|
|
title: Scrapegraph Scrape Tool
|
|
description: The `ScrapegraphScrapeTool` leverages Scrapegraph AI's SmartScraper API to intelligently extract content from websites.
|
|
icon: chart-area
|
|
mode: "wide"
|
|
---
|
|
|
|
# `ScrapegraphScrapeTool`
|
|
|
|
## Description
|
|
|
|
The `ScrapegraphScrapeTool` is designed to leverage Scrapegraph AI's SmartScraper API to intelligently extract content from websites. This tool provides advanced web scraping capabilities with AI-powered content extraction, making it ideal for targeted data collection and content analysis tasks. Unlike traditional web scrapers, it can understand the context and structure of web pages to extract the most relevant information based on natural language prompts.
|
|
|
|
## Installation
|
|
|
|
To use this tool, you need to install the Scrapegraph Python client:
|
|
|
|
```shell
|
|
uv add scrapegraph-py
|
|
```
|
|
|
|
You'll also need to set up your Scrapegraph API key as an environment variable:
|
|
|
|
```shell
|
|
export SCRAPEGRAPH_API_KEY="your_api_key"
|
|
```
|
|
|
|
You can obtain an API key from [Scrapegraph AI](https://scrapegraphai.com).
|
|
|
|
## Steps to Get Started
|
|
|
|
To effectively use the `ScrapegraphScrapeTool`, follow these steps:
|
|
|
|
1. **Install Dependencies**: Install the required package using the command above.
|
|
2. **Set Up API Key**: Set your Scrapegraph API key as an environment variable or provide it during initialization.
|
|
3. **Initialize the Tool**: Create an instance of the tool with the necessary parameters.
|
|
4. **Define Extraction Prompts**: Create natural language prompts to guide the extraction of specific content.
|
|
|
|
## Example
|
|
|
|
The following example demonstrates how to use the `ScrapegraphScrapeTool` to extract content from a website:
|
|
|
|
```python Code
|
|
from crewai import Agent, Task, Crew
|
|
from crewai_tools import ScrapegraphScrapeTool
|
|
|
|
# Initialize the tool
|
|
scrape_tool = ScrapegraphScrapeTool(api_key="your_api_key")
|
|
|
|
# Define an agent that uses the tool
|
|
web_scraper_agent = Agent(
|
|
role="Web Scraper",
|
|
goal="Extract specific information from websites",
|
|
backstory="An expert in web scraping who can extract targeted content from web pages.",
|
|
tools=[scrape_tool],
|
|
verbose=True,
|
|
)
|
|
|
|
# Example task to extract product information from an e-commerce site
|
|
scrape_task = Task(
|
|
description="Extract product names, prices, and descriptions from the featured products section of example.com.",
|
|
expected_output="A structured list of product information including names, prices, and descriptions.",
|
|
agent=web_scraper_agent,
|
|
)
|
|
|
|
# Create and run the crew
|
|
crew = Crew(agents=[web_scraper_agent], tasks=[scrape_task])
|
|
result = crew.kickoff()
|
|
```
|
|
|
|
You can also initialize the tool with predefined parameters:
|
|
|
|
```python Code
|
|
# Initialize the tool with predefined parameters
|
|
scrape_tool = ScrapegraphScrapeTool(
|
|
website_url="https://www.example.com",
|
|
user_prompt="Extract all product prices and descriptions",
|
|
api_key="your_api_key"
|
|
)
|
|
```
|
|
|
|
## Parameters
|
|
|
|
The `ScrapegraphScrapeTool` accepts the following parameters during initialization:
|
|
|
|
- **api_key**: Optional. Your Scrapegraph API key. If not provided, it will look for the `SCRAPEGRAPH_API_KEY` environment variable.
|
|
- **website_url**: Optional. The URL of the website to scrape. If provided during initialization, the agent won't need to specify it when using the tool.
|
|
- **user_prompt**: Optional. Custom instructions for content extraction. If provided during initialization, the agent won't need to specify it when using the tool.
|
|
- **enable_logging**: Optional. Whether to enable logging for the Scrapegraph client. Default is `False`.
|
|
|
|
## Usage
|
|
|
|
When using the `ScrapegraphScrapeTool` with an agent, the agent will need to provide the following parameters (unless they were specified during initialization):
|
|
|
|
- **website_url**: The URL of the website to scrape.
|
|
- **user_prompt**: Optional. Custom instructions for content extraction. Default is "Extract the main content of the webpage".
|
|
|
|
The tool will return the extracted content based on the provided prompt.
|
|
|
|
```python Code
|
|
# Example of using the tool with an agent
|
|
web_scraper_agent = Agent(
|
|
role="Web Scraper",
|
|
goal="Extract specific information from websites",
|
|
backstory="An expert in web scraping who can extract targeted content from web pages.",
|
|
tools=[scrape_tool],
|
|
verbose=True,
|
|
)
|
|
|
|
# Create a task for the agent to extract specific content
|
|
extract_task = Task(
|
|
description="Extract the main heading and summary from example.com",
|
|
expected_output="The main heading and summary from the website",
|
|
agent=web_scraper_agent,
|
|
)
|
|
|
|
# Run the task
|
|
crew = Crew(agents=[web_scraper_agent], tasks=[extract_task])
|
|
result = crew.kickoff()
|
|
```
|
|
|
|
## Error Handling
|
|
|
|
The `ScrapegraphScrapeTool` may raise the following exceptions:
|
|
|
|
- **ValueError**: When API key is missing or URL format is invalid.
|
|
- **RateLimitError**: When API rate limits are exceeded.
|
|
- **RuntimeError**: When scraping operation fails (network issues, API errors).
|
|
|
|
It's recommended to instruct agents to handle potential errors gracefully:
|
|
|
|
```python Code
|
|
# Create a task that includes error handling instructions
|
|
robust_extract_task = Task(
|
|
description="""
|
|
Extract the main heading from example.com.
|
|
Be aware that you might encounter errors such as:
|
|
- Invalid URL format
|
|
- Missing API key
|
|
- Rate limit exceeded
|
|
- Network or API errors
|
|
|
|
If you encounter any errors, provide a clear explanation of what went wrong
|
|
and suggest possible solutions.
|
|
""",
|
|
expected_output="Either the extracted heading or a clear error explanation",
|
|
agent=web_scraper_agent,
|
|
)
|
|
```
|
|
|
|
## Rate Limiting
|
|
|
|
The Scrapegraph API has rate limits that vary based on your subscription plan. Consider the following best practices:
|
|
|
|
- Implement appropriate delays between requests when processing multiple URLs.
|
|
- Handle rate limit errors gracefully in your application.
|
|
- Check your API plan limits on the Scrapegraph dashboard.
|
|
|
|
## Implementation Details
|
|
|
|
The `ScrapegraphScrapeTool` uses the Scrapegraph Python client to interact with the SmartScraper API:
|
|
|
|
```python Code
|
|
class ScrapegraphScrapeTool(BaseTool):
|
|
"""
|
|
A tool that uses Scrapegraph AI to intelligently scrape website content.
|
|
"""
|
|
|
|
# Implementation details...
|
|
|
|
def _run(self, **kwargs: Any) -> Any:
|
|
website_url = kwargs.get("website_url", self.website_url)
|
|
user_prompt = (
|
|
kwargs.get("user_prompt", self.user_prompt)
|
|
or "Extract the main content of the webpage"
|
|
)
|
|
|
|
if not website_url:
|
|
raise ValueError("website_url is required")
|
|
|
|
# Validate URL format
|
|
self._validate_url(website_url)
|
|
|
|
try:
|
|
# Make the SmartScraper request
|
|
response = self._client.smartscraper(
|
|
website_url=website_url,
|
|
user_prompt=user_prompt,
|
|
)
|
|
|
|
return response
|
|
# Error handling...
|
|
```
|
|
|
|
## Conclusion
|
|
|
|
The `ScrapegraphScrapeTool` provides a powerful way to extract content from websites using AI-powered understanding of web page structure. By enabling agents to target specific information using natural language prompts, it makes web scraping tasks more efficient and focused. This tool is particularly useful for data extraction, content monitoring, and research tasks where specific information needs to be extracted from web pages. |