crewai-piloterr
CrewAI tools for Piloterr, a web data API.
PiloterrGoogleSearchToolsearches Google.PiloterrScrapeWebsiteToolreads a web page and returns its title and readable text. Piloterr fetches the page on its own infrastructure, in one of three ways:crawler: plain HTTP, the default;rendering: a headless browser, for JavaScript pages;webunlocker: for pages behind anti-bot protection.
Installation
pip install crewai-piloterr
Get an API key at app.piloterr.com and set it in the environment:
export PILOTERR_API_KEY="your-api-key"
Usage
from crewai import Agent, Crew, Task
from crewai_piloterr import PiloterrGoogleSearchTool, PiloterrScrapeWebsiteTool
researcher = Agent(
role="Researcher",
goal="Find and read sources on the web",
backstory="You search, then read the best pages before answering.",
tools=[PiloterrGoogleSearchTool(n_results=5), PiloterrScrapeWebsiteTool(engine="rendering")],
)
task = Task(description="Summarize what piloterr.com offers.", expected_output="A short summary", agent=researcher)
Crew(agents=[researcher], tasks=[task]).kickoff()
PiloterrGoogleSearchTool
Returns a JSON list of results with title, link, snippet and position.
| Option | Default | Description |
|---|---|---|
n_results |
10 |
Results requested, 1 to 100 |
country |
Two-letter country code, such as us |
|
language |
Language code, optionally with a region, such as en-gb |
|
location |
City or region to search from |
PiloterrScrapeWebsiteTool
Returns the page title as a heading, followed by the readable text. Scripts and styles are removed.
| Option | Default | Description |
|---|---|---|
engine |
crawler |
crawler, rendering or webunlocker |
wait_in_seconds |
Rendering only: extra wait after the page loads, 0 to 30 | |
max_characters |
20000 |
Truncate the text; None keeps it all |
timeout |
120 |
Seconds to wait for Piloterr |
Both tools take api_key (default PILOTERR_API_KEY). They return API errors to the agent as text, and the key never appears in them.
Development
pip install -e ".[test]"
pytest
License
MIT
Metadata
Release files for crewai-piloterr 0.1.0
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 |
|---|---|---|---|---|
| crewai_piloterr-0.1.0.tar.gz | 7.1 kB | Without provenance | Details for crewai_piloterr-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| crewai_piloterr-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for crewai_piloterr-0.1.0-py3-none-any.whl |
Total release size: 14.0 kB
Release files / crewai_piloterr-0.1.0.tar.gz
| Download URL | crewai_piloterr-0.1.0.tar.gz |
|---|---|
| Size | 7.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a95fbf44f28b8c724107630b777cb229c6018913641c562eba25b02ef86f59ae
|
|
BLAKE2b-256 checksum How to use checksums |
60f68509b838ff574a7d3b8c9e2e395ee87932c2df2f1e97f9374438b924bf60
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Release files / crewai_piloterr-0.1.0-py3-none-any.whl
| Download URL | crewai_piloterr-0.1.0-py3-none-any.whl |
|---|---|
| Size | 6.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
895e1bf5526d6aac56f3813a6f423182d4e56cf2e12dc546dd158cd402f80e6b
|
|
BLAKE2b-256 checksum How to use checksums |
6a414d28f56a2130152a8747df76aec4fdc7b42fb7f9f1732af2e58705dbb370
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.4
|
Security for crewai-piloterr 0.1.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.