site_extract
may change things: you confirm before it runsRender a whole section of a site - up to 25 pages - in one call and get every page back as clean text, with JavaScript executed. Same host only; robots.txt is obeyed and anything it disallows is skipped and named. FREE: the crawl PLAN - exactly which pages would be fetched and what robots.txt allows - so you can see what you would get before paying. PAID ($0.14, x402 on Arc/Base/Solana/X1): every page rendered and returned. It costs more than one page because it is up to 25 real browser renders, not a lookup. If a bot wall on the site lets the first page through but blocks the rest, the call fails with `poor-yield` and names every page it could not render, instead of billing you for a list of failures.
Input schema
{
"type": "object",
"properties": {
"url": {
"type": "string",
"description": "the page to start from"
},
"pages": {
"type": "number",
"description": "how many pages, default 10, hard cap 25"
},
"full": {
"type": "boolean",
"description": "true asks for the paid crawl. Without a payment you get a 402 carrying the price and every rail we accept; sign it and call again with `payment`."
},
"payment": {
"type": "string",
"description": "a signed x402 payment (the same base64 payload you would put in the PAYMENT-SIGNATURE header). Pass it here and the purchase completes inside this tool call."
}
},
"required": [
"url"
]
}