Add Circle/x402 paid crawl endpoint for autonomous agents
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 25/100
Línea de trabajo
Start by locating the existing /crawl, /crawl/job, /crawl/stream, and /llm/job API entry points and the crawl/job pipeline they use. Review how request schemas, authentication, and results are handled before defining the additive /x402/crawl behavior. Done would include the paid route, payment verification, crawl output with a receipt, and documentation of supported networks, pricing, schemas, and retries.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Proposal: add an optional Circle/x402 paid crawl endpoint for autonomous agents
I ran a static Circle/x402 readiness scan against Crawl4AI to see whether it could become an agent-payable service. Crawl4AI is a strong fit because agents already need on-demand crawling, extraction, and LLM-ready web data.
Readiness summary
- Score from the scan: 46/100 — good candidate, medium effort.
- The repo has meaningful primitives for crawling jobs, schemas, rate/concurrency concerns, and receipt/proof-like result concepts.
- I did not find x402 or Circle Agent Wallet/Marketplace-specific documentation.
- The scanner did not fully detect Crawl4AI's Python/FastAPI-style routes, but source references show Docker/API surfaces such as
/crawl,/crawl/job,/crawl/stream, and/llm/jobpatterns.
Why this is useful
AI agents often need one-off crawling or extraction without a long-lived API key, dashboard account, or shared credit pool. A Circle/x402 paid route would let an agent:
- Discover a paid crawl endpoint.
- Inspect price and input schema.
- Pay in USDC from a Circle Agent Wallet.
- Receive crawl output plus a receipt/proof object.
Suggested first implementation
Start with a narrow additive endpoint rather than changing the whole auth or deployment model:
POST /x402/crawl
-> return 402 Payment Required when no valid payment is supplied
-> verify x402 payment on Base/USDC
-> run the existing crawl/job pipeline
-> return { data, receipt }
A receipt shape for agent buyers could look like:
{
"receipt": {
"amount": "0.01",
"asset": "USDC",
"network": "base",
"resource": "POST /x402/crawl",
"requestHash": "sha256:...",
"resultHash": "sha256:...",
"jobId": "crawl_..."
}
}
Circle Agent Marketplace readiness docs
If this is interesting, I would also document:
- supported network(s)
- USDC price per crawl or per page
- request JSON schema
- response JSON schema
- receipt/proof object
- timeout and retry behavior
- how Circle Agent Wallet / x402 clients should pay
I generated this from Budcle, a small scanner for identifying Circle/x402 adoption gaps in open-source API projects: https://github.com/batikanor/Budcle
This is intentionally additive: existing Crawl4AI library usage, Docker deployment, and auth choices can remain unchanged while adding one agent-payable path for x402-capable clients.
- Lenguaje dominante
- Python
- Estrellas
- 85.9k
- Forks
- 8.9k
- Merge medio
- 5 d 7 h
- PR fusionados (30 d)
- 23
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de unclecode/crawl4ai
-
[Bug]: Text after an inline <link>, <meta>, <style> or <noscript> is dropped from cleaned_html and markdownPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
unclecode/crawl4ai#2416 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
[Bug]: Since 0.9.1, Linux launches chrome-headless-shell instead of ChromiumPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
unclecode/crawl4ai#2382 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
[Bug]: BestFirstCrawlingStrategy fetches a full batch past max_pagesPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
unclecode/crawl4ai#2381 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
[Bug]: CrawlerRunConfig.clone() drops fallback_fetch_function, so deep crawls never use itPosiblemente ocupada @siva23367 la tomó hace 1 día. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
unclecode/crawl4ai#2379 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
[Bug]: Docker memory guard reads host RAM when no container limit is set — cgroup v2 "max" defeats get_container_memory_percentPosiblemente ocupada @Battleplus la tomó hace 57 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
unclecode/crawl4ai#2123 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de unclecode/crawl4ai
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
changelog investigate
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
ramnes/notion-sdk-py#423 ·
-
type-bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día