treg vs looot for web scraping and extraction APIs: where looot costs less
The looot catalog has 149 items for web scraping and extraction APIs from 22 providers. Below are the Olostep endpoints where looot's price per call is lower than treg's for the same operation, checked 2026-11-18.
set up looot - https://looot.ai/skill.mdlooot
Compliance and data quality on every call
What looot documents about compliance and the quality of what a run returns, each line linked to the looot page that states it.
Compliance guardrails
Tenant isolation
Every workspace, credential, run and audit record is scoped to its organization at the data layer. One tenant's connections and history are never reachable from another's.
Source: looot.ai/security
Hash-chained audit log
Every recorded action links to the previous record's hash, so the sequence can be checked end to end. Payloads are digested and sensitive fields are redacted before anything is written.
Source: looot.ai/security
A GDPR Data Processing Agreement
looot's DPA is written to meet Article 28 of the GDPR and applies the EU Standard Contractual Clauses to transfers that need them.
Source: looot.ai/dpa
Named subprocessors and where they run
Annex II lists every subprocessor with its location. The database runs in Ireland (AWS eu-west-1) and the gateway in Frankfurt; the list also names the ones in the United States. Run inputs and provider results are not sent to analytics.
Source: looot.ai/dpa#annex-ii
Scoped agent keys with a spend limit
An agent key carries only the scopes of its owner's role, never a credential write scope, expires after at most 90 days and can carry a monthly spend limit.
Source: looot.ai/dpa#annex-iii
Encrypted provider credentials
Stored provider credentials are encrypted with AES-256-GCM in the gateway's secrets vault, and data in transit uses TLS.
Source: looot.ai/dpa#annex-iii
Data quality
Versioned contracts with schemas
Each operation version is a contract: input schema, output schema, effect (read, write or outreach), idempotency and retry eligibility. Versions are never edited in place.
Source: looot.ai/guarantees
Results checked against their schema
When a result cannot be checked against its schema, or a provider call fails after money may have moved, the run is marked reconciliation pending instead of being marked done.
Source: looot.ai/guarantees
Raw, canonical and mapped output
Every run result carries the provider's raw response, a normalized canonical form and an optional mapped shape, with field-level provenance for each mapped field.
Source: looot.ai/security
Retry only where it is safe
An automatic retry policy attaches only to read operations. An uncertain outcome stops for reconciliation instead of being retried blindly, so one effect is never charged twice.
Source: looot.ai/guarantees
A failed run charges $0
Funds reserve first, then settle, release or refund. When the provider call fails, looot charges $0 and releases the hold.
Source: looot.ai/pricing
Price confidence and catalog state in the open
Each price carries a confidence tag (official and current, official but stale, estimated, or unknown), and every published operation shows its provider, price and verification state in the public catalog.
Source: looot.ai/guarantees
- 149
- looot catalog items in this category
- 22
- providers on looot
- 48
- on your own key, $0 looot fee
- 2
- endpoints where looot costs less than treg
Web scraping
Endpoints where looot costs less than treg, checked 2026-11-18
Same provider and same operation in both public catalogs. Each looot price links to its catalog page, where the live price shows.
| Provider and operation | looot | treg | looot costs |
|---|---|---|---|
| Olostep: Scrape a pageper call (1 Olostep credit) | $0.0018 | $0.002olostep.web.scrape | 10% less |
| Olostep: Map the URLs of a siteper call | $0.0018 | $0.002olostep.web.map.search | 10% less |
Coverage for web scraping and extraction APIs
149 looot public catalog items from 22 providers sit in this category (catalog categories web-data, scrape, web, web-automation), counted on 2026-11-18. Each one has its own page in the public catalog with the price per call.
Your own provider keys
48 of them run on your own provider key with a $0 looot fee; the provider bills you directly, and the run still goes through looot's audit log and spend limits.
Guardrails on every call
- The price of the call shows before it runs; the run reserves that amount from your prepaid balance, settles on the real cost and refunds the difference.
- A crawl or batch scrape reserves its price up front and settles on what ran.
- Each API key can carry a monthly spend limit, so an agent stops at the budget you set.
- Every run is written to a hash-chained, redacted audit log scoped to your organization.
Questions people ask
More on treg and looot
Try looot with your own agent.
Start a workspace, top up, and run any catalog call. The price shows before each run and you pay for what ran.