Result web scrape
Run job:web.scrape.result through the looot API: 1 provider, from $0 per call. Inputs, prices, output shape and code for curl, JavaScript and Python.
Result web scrape.
Job id web.scrape.result, in Enrichment (Web data). As of 2026-10-07, 1 provider serve it through 2 tools. Run job:web.scrape.result and looot picks one of them; with fallback on, a miss moves on to the next. See Jobs.
Inputs
Fields the job’s tools take, most shared first. Any key you send passes through unchanged.
| Name | Type | Taken by | Required by | Description |
|---|---|---|---|---|
formats |
array | 1 of 2 | 0 | Optional array to retrieve only specific formats in production. If not provided, all formats will be returned. |
retrieve_id |
string | 1 of 2 | 1 | The ID of the page content to retrieve. Available in the response of /v1/crawls/\{crawl_id\}/pages, /v1/scrapes/\{scrape_id\} or /v1/batches/\{batch_id\}/items endpoints |
scrape_id |
string | 1 of 2 | 1 | Unique identifier for the scrape to be retrieved. |
Providers and prices
| Provider | Tool | Price |
|---|---|---|
| Olostep | olostep-retrieve |
$0 per call |
| Olostep | olostep-scrape-get |
$0 per call |
A call that fails at the provider costs $0. See What’s free.
Output
The run’s result holds the provider’s answer. Signed in, looot inspect olostep-retrieve prints its fields.
Run it
Every call needs your API token in LOOOT_TOKEN; Sign in shows how to get one. Each run also needs a new idempotency key, so a retry never pays twice. With wait: 30 the answer comes back inline when the run ends within 30 seconds. Otherwise you get the running run back: poll GET /v1/runs/<runId>.
Example input with placeholder values:
curl -X POST "https://api.looot.ai/v1/runs" \
-H "Authorization: Bearer $LOOOT_TOKEN" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: $(uuidgen)" \
-d '{"endpointId":"job:web.scrape.result","input":{"retrieve_id":"<retrieve_id>"},"wait":30}'const response = await fetch("https://api.looot.ai/v1/runs", {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.LOOOT_TOKEN}`,
"Content-Type": "application/json",
"Idempotency-Key": crypto.randomUUID(),
},
body: JSON.stringify({
endpointId: "job:web.scrape.result",
input: {
retrieve_id: "<retrieve_id>",
},
wait: 30,
}),
});
const run = await response.json();
console.log(run.status, run.result);import os
import uuid
import requests
response = requests.post(
"https://api.looot.ai/v1/runs",
headers={
"Authorization": f"Bearer {os.environ['LOOOT_TOKEN']}",
"Idempotency-Key": str(uuid.uuid4()),
},
json={
"endpointId": "job:web.scrape.result",
"input": {
"retrieve_id": "<retrieve_id>",
},
"wait": 30,
},
timeout=90,
)
run = response.json()
print(run["status"], run.get("result"))To pin one provider, send its tool id as endpointId instead of job:web.scrape.result. The shared input names above are for the job: run only; a tool id takes that tool’s own field names, listed on its page, and refuses the shared ones when they differ. For olostep-retrieve that is retrieve_id.