A previous release had provenance metadata, but this release does not. View details.
pulldown
Pull down web pages as clean Markdown for LLM agents.
- HTTP-first with browser-like defaults
- Optional Chromium rendering for JS-heavy pages
- Four detail levels:
minimal,readable,full,raw - Core installs decode Brotli-compressed pages correctly
- Concurrent batch fetching with
fetch_many() - Bounded site crawling with
robots.txtsupport and per-domain politeness - Validator-based caching (ETag / Last-Modified) with atomic writes
- SSRF guards: private/loopback/metadata addresses blocked by default
- Response size caps and transient-error retries
- CLI, Python API, and MCP server
Install
pip install pulldown # core
pip install 'pulldown[render]' # + Playwright (Chromium rendering)
pip install 'pulldown[mcp]' # + MCP server
pip install 'pulldown[all]' # everything
Core installs include Brotli support, so br-compressed HTML is decoded before
minimal, readable, full, or raw processing.
Core installs also include lxml_html_clean, avoiding the missing-helper import
issue some agent sandboxes hit on older releases.
For rendered pages, also run playwright install chromium once.
Quick Start
CLI
pulldown get https://example.com
pulldown get https://example.com --detail minimal
pulldown get https://example.com --render --scroll 3
pulldown crawl https://docs.example.com --max-pages 20 --delay-ms 200
pulldown bench https://example.com --runs 5
pulldown cache stats
Python
import asyncio
from pulldown import fetch, fetch_many, crawl, Detail, PageCache
async def main():
# Single fetch
result = await fetch("https://example.com", detail=Detail.readable)
print(result.title, result.content)
# Batch fetch with caching
cache = PageCache(ttl=3600)
results = await fetch_many(
["https://a.com", "https://b.com"],
concurrency=5,
cache=cache,
retries=2,
)
# Crawl a docs site
crawl_result = await crawl(
"https://docs.example.com/",
max_pages=50,
max_depth=2,
respect_robots=True,
per_domain_delay_ms=200,
)
markdown = crawl_result.to_markdown()
asyncio.run(main())
MCP
Add to your client config (e.g. Claude Desktop):
{
"mcpServers": {
"pulldown": {
"command": "python",
"args": ["-m", "pulldown.mcp_server"],
"env": {
"PULLDOWN_CACHE_DIR": "~/.cache/pulldown"
}
}
}
}
Environment variables:
| Variable | Default | Purpose |
|---|---|---|
MCP_TRANSPORT |
stdio |
stdio or http |
MCP_HOST |
127.0.0.1 |
Bind address for HTTP transport |
MCP_PORT |
8080 |
Port for HTTP transport |
PULLDOWN_CACHE_DIR |
unset | Enable caching to this directory |
PULLDOWN_CACHE_TTL |
3600 |
Cache TTL in seconds |
PULLDOWN_ALLOW_PRIVATE |
0 |
Set to 1 to allow private addresses |
Detail Levels
| Level | Output | Best for |
|---|---|---|
minimal |
Title + plain text | Lowest-token summarisation |
readable |
Clean Markdown with links | RAG, reading, structured landing pages (default) |
full |
Full-page Markdown incl. chrome | Pages without clear article body |
raw |
Untouched HTML | Custom parsing downstream |
Security
pulldown refuses to fetch URLs that resolve to private, loopback,
link-local, or cloud-metadata addresses by default. This prevents
LLM-driven SSRF into internal services (e.g., AWS metadata at
169.254.169.254, Redis on localhost:6379). Override with
allow_private_addresses=True if you understand the risk.
Responses above 10 MiB are rejected by default (max_bytes parameter).
Only http and https schemes are accepted; file:, ftp:, etc. are
rejected.
License
MIT
Metadata
Release files for pulldown 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Loss of provenance
These files do not have provenance metadata, despite files in a prior release including this data.
We recommend further investigation before installing these files. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| pulldown-0.3.1.tar.gz | 104.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pulldown-0.3.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 132.8 kB
Release files / pulldown-0.3.1.tar.gz
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | pulldown-0.3.1.tar.gz |
|---|---|
| Size | 104.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e32a46b88dfc8133429b015eb147f1883b5d5301b43ec5779647c3a01f6e2cdc
|
|
BLAKE2b-256 checksum How to use checksums |
642421d4eab0ecb8dc8371ef1d7e89e6cde6501a93128cdf904f9c53b7599f8a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Release files / pulldown-0.3.1-py3-none-any.whl
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | pulldown-0.3.1-py3-none-any.whl |
|---|---|
| Size | 28.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
553486287458e10054cad7683cea85acd3fca0c674533ed35bef63d9e816ab44
|
|
BLAKE2b-256 checksum How to use checksums |
2d9369edf909519a7d895c6f7017d0d6afd8222e9d28cf2da6739a2ca9548975
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Security for pulldown 0.3.1
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.
Loss of provenance
A previous release of these files had provenance metadata, but this release does not.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Release comparison
- Removed 0.2.0 2 files With provenance
- Added 0.3.1 2 files Without provenance
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.