Install
openclaw skills install @crawlora-org/crawloraFetches structured public web data via the Crawlora REST API — search engines, e-commerce, social, finance, maps, app stores, media, and reviews — returning clean JSON instead of HTML. Use whenever the user needs real data from a public website (prices, listings, reviews, transcripts, SERPs, trends, financials, places) and would otherwise have to scrape or parse HTML.
openclaw skills install @crawlora-org/crawloraCrawlora is a hosted API that turns public websites into clean, normalized JSON. The current public-data catalog contains 1,729 tools across 210 platform groups, and the repository ships 100 focused research skills. One API key gives you the endpoints in the bundled catalog — search engines, marketplaces, social and video, finance and crypto, maps, app stores, media, and reviews — so an agent can fetch real data without running a browser, proxies, or HTML parsers.
Account usage, recent-IP, website-monitor management, generic URL scraping, APK analysis, and bulk profile-dataset endpoints are intentionally excluded from this skill. Dedicated skills cover the specialized workflows, and this helper rejects those paths as well.
Use Crawlora when the user asks for live data that lives on a public website, e.g.:
Prefer a more specific Crawlora skill if one is installed (e.g.
product-price-research, youtube-research, app-review-mining,
serp-keyword-research). This umbrella skill covers everything else.
Get a free Crawlora API key (2,000 credits/mo, no card) at https://crawlora.net.
Export it so the helper and any curl calls can read it:
export CRAWLORA_API_KEY
Set CRAWLORA_API_KEY to the key you received before running the helper.
All requests go to https://api.crawlora.net/api/v1 with the header
CRAWLORA_API_KEY from the environment. A missing/invalid key returns 401.
reference/catalog.md — it
lists every endpoint grouped by platform, with method, path, and parameters.
Match the user's job to a platform group, then to an endpoint.scripts/crawlora.sh (see below). It handles auth and prints JSON.jq and answer. Most endpoints return paginated lists;
pass page/count params where documented.# GET with query params (key=value):
scripts/crawlora.sh /amazon/search k=laptop | jq '.'
scripts/crawlora.sh /google/suggest q="web scraping" | jq '.'
scripts/crawlora.sh /youtube/transcript/dQw4w9WgXcQ | jq '.'
# POST endpoints take a JSON body (note the -X POST):
scripts/crawlora.sh -X POST /google/search '{"keyword":"web scraping api","language":"en","country":"us"}' | jq '.'
scripts/crawlora.sh -X POST /google/trends/explore/interest-over-time '{"keywords":["bitcoin"]}' | jq '.'
Use scripts/crawlora.sh for all requests; it keeps the API key out of command-line arguments.
The catalog marks each endpoint's HTTP method. Path params like {id} are
substituted into the URL; GET params go in the query string; POST params go
in the JSON body.
See reference/catalog.md for the complete list of
endpoints (method, path, params, description) grouped by platform.
scripts/crawlora.sh /amazon/search k="standing desk" →
read .data[].price to compare listings.scripts/crawlora.sh /youtube/transcript/<id> and summarize.scripts/crawlora.sh -X POST /google/trends/explore/interest-over-time '{"keywords":["electric bikes"]}'.scripts/crawlora.sh /yahoo-finance/ticker/NVDA/quote (see the
Yahoo Finance group in the catalog for the exact path/params).2xx responses; failures aren't charged.
Free tier is 2,000 credits/mo. Get a key at https://crawlora.net.CRAWLORA_API_KEY only — never hardcode it, never put
it in a URL query param, never commit it.503 when the upstream serves a challenge page; retry
or fall back to another search provider (Google ↔ Bing ↔ Brave).