Scrapingant Scrape
by Vaaya in Search & web
ScrapingAnt — Scrape a URL through a managed headless-Chrome cluster (datacenter proxies). Pass `url`; optional `browser` (default true — set false for plain HTTP fetch), `wait_for_selector` (CSS selector to await), `js_snippet` (base64 JS to execute on the page), `block_resource`, `proxy_country` (2-letter), `timeout` (5-60s), `cookies`, `return_page_source`. Returns the rendered page as `{ raw: "<html>…" }`. For Cloudflare/anti-bot-walled pages use scrapingant/scrape_residential.
https://vaaya.ai/api/run/scrapingant/scrape- Price
- $0.01
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 245 ms
- 369 ms slowest 5%
- Last check
- Passed
- 2 h ago, next any minute now
Reliability
How to call it
POST https://vaaya.ai/api/run/scrapingant/scrape
Each call costs $0.01 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
POST https://vaaya.ai/api/run/scrapingant/scrape
content-type: application/json
{
"url": "https://example.com"
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
block_resource | string or array of string | No | |
browser | boolean | No | |
cookies | string | No | |
js_snippet | string | No | |
proxy_country | string | No | |
return_page_source | boolean | No | |
timeout | integer | No | |
url | string (uri) | Yes | |
wait_for_selector | string | No |
Example response
The provider's example. We can't check it without paying.
{
"charged_cents": 1,
"data": {},
"ok": true
}Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.01.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://vaaya.ai/api/run/scrapingant/scrape' \
-H 'content-type: application/json' \
--data-raw '{"url":"https://example.com"}'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://vaaya.ai/api/run/scrapingant/scrape' \
-H 'content-type: application/json' \
--data-raw '{"url":"https://example.com"}' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fvaaya.ai%2Fapi%2Frun%2Fscrapingant%2Fscrape&method=POST
const res = await pay("https://vaaya.ai/api/run/scrapingant/scrape", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"url": "https://example.com"
}),
});
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://vaaya.ai/api/run/scrapingant/scrape",
json={
"url": "https://example.com",
},
)
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 2 h ago | Passed | 402 | 263 ms | $0.01 |
| 6 h ago | Passed | 402 | 138 ms | $0.01 |
| 11 h ago | Passed | 402 | 241 ms | $0.01 |
| 15 h ago | Passed | 402 | 163 ms | $0.01 |
| 19 h ago | Passed | 402 | 143 ms | $0.01 |
Show 10 older checks
| 23 h ago | Passed | 402 | 169 ms | $0.01 |
| 27 h ago | Passed | 402 | 269 ms | $0.01 |
| 30 h ago | Passed | 402 | 351 ms | $0.01 |
| 34 h ago | Passed | 402 | 351 ms | $0.01 |
| 38 h ago | Passed | 402 | 286 ms | $0.01 |
| 41 h ago | Passed | 402 | 460 ms | $0.01 |
| 45 h ago | Passed | 402 | 236 ms | $0.01 |
| 2 days ago | Passed | 402 | 232 ms | $0.01 |
| 2 days ago | Passed | 402 | 181 ms | $0.01 |
| 2 days ago | Passed | 402 | 263 ms | $0.01 |