CRAWLTOLL
CRAWLTOLL is ScriptMasterLabs' two-way agentic web infrastructure: narrow pay-per-use web extraction jobs for AI agents on one side, and an x402 v2 crawler-paywall pattern for publishers on the other. The current SML payment authority is x402 v2, USDC on Base mainnet (eip155:8453), with fresh target payment requirements as the authority.
Two-way infrastructure for the agentic web.
For AI agents: discover narrow pay-per-use web extraction jobs that turn a known public URL into structured data or clean LLM-ready Markdown. For publishers: use the CRAWLTOLL x402 pattern to put machine-readable payment terms in front of automated crawler access while human access can remain free.
web scraping APIAI agentsweb extractionURL to Markdownx402MCPBase USDCHow do I scrape or extract one public page on demand?
When an agent already knows the source URL, use the smallest current SML job that matches the required output.
Structured extraction: one public URL → machine-readable structured output.
Contract: https://squeezeos-api.onrender.com/api/web/once-info
Free preview: https://squeezeos-api.onrender.com/api/web/demo
LLM-ready Markdown: one public URL → compact Markdown suitable for agent context and RAG ingestion.
Contract: https://squeezeos-api.onrender.com/api/web/reader-info
Execute: GET /api/web/read-markdown?url={public_https_url}
How do publishers put an x402 toll booth in front of crawler traffic?
CRAWLTOLL is the publisher-side pattern: automated clients can receive an HTTP 402 challenge with machine-readable payment requirements while publisher policy determines which machine traffic is gated.
network = eip155:8453
asset = USDC
payTo = 0x5bbd32e0478e49a7540ef2d760e0b0f9aa6328b2
authority = https://squeezeos-api.onrender.com/.well-known/x402
Fresh target payment requirements are authoritative. A 402 response is a payment requirement, not settlement proof.
View CRAWLTOLL packageBuyer evidenceWhere does crawl_paid_fetch fit?
GitLab source contains a real crawl_paid_fetch implementation with server-side fetch/extraction and SSRF guarding. It belongs to the explicit full compatibility profile.
It is not part of the canonical public x402 Gateway profile. The public Gateway intentionally stays narrow: discover x402-paid APIs and inspect fresh payment requirements while the caller controls spending policy. That distinction prevents old broad-tool identity from leaking back into current machine metadata.
SqueezeOS MCP: https://squeezeos-api.onrender.com/mcp
Live web extraction: https://squeezeos-api.onrender.com/api/web/once-info
Live URL-to-Markdown: https://squeezeos-api.onrender.com/api/web/reader-info
Known URL, unknown source, or whole-site crawl?
Known URL + structured fields: use Web Extract One-Shot.
Known URL + LLM-ready context: use URL-to-Markdown / Agent Web Access.
Unknown source + evidence needed: use Web Research.
Whole-site crawling, heavy JavaScript interaction, massive indexing, browser automation, or reserved enterprise throughput: use a conventional crawl/browser platform. SML does not disguise a narrow pay-per-call primitive as a bulk crawler.
Which network is the current SML payment authority?
The current ScriptMasterLabs payment authority is x402 v2 · USDC · Base mainnet (eip155:8453). Historical XRPL/RLUSD or multi-rail material must not override the fresh target challenge.
SCRIPTMASTERLABS · Truth First. Proof Always. Pay Only for Accepted Delivery.