Expose selected Crawlora endpoints as tool calls so agents can retrieve normalized JSON before summarizing or ranking results.
What you will build
Agent receives task
Planner selects Crawlora tool or endpoint
Crawlora returns normalized JSON
Agent summarizes, ranks, or compares
Store result or produce report
APIs used
Only endpoints that exist in the generated endpoint metadata are linked here. Missing optional endpoints are intentionally omitted.
GETBingapiKey3 credits/request
Search Bing web results
/bing/search
Returns normalized Bing web search results for a query string, including organic results, optional context panel data, related queries, people-also-ask questions, news modules, video modules, and page-based pagination. Empty optional blocks are omitted from the JSON response. Locale defaults to country=us and lang=en-us. Results are fetched with a Chrome-impersonated request client and return 503 on a genuine transport failure or challenge page. Bing occasionally serves a well-formed page whose results share no significant term with the query; when every hedged attempt hits this, the response is still returned as 200 with data.low_confidence set to true (and the X-Low-Confidence header) instead of being withheld, so callers get Bing's real answer plus an honest signal to double-check it rather than nothing. Queries that use the site: operator (for example site:gov.hu) are not supported: Bing serves a bot-verification challenge for them, so they are rejected with 400 before any request is made. Use the DuckDuckGo (/api/v1/duckduckgo/search), Brave (/api/v1/brave/search), or Yahoo (/api/v1/yahoo-search/search) search endpoints for domain-restricted searches instead.
Searches JustWatch titles using the public credential-free website GraphQL endpoint. Country must be a two-letter ISO code such as `US`; language must be a two-letter code such as `en`.
Returns transcript segments for a YouTube video using YouTube's native player captions.
Set `format=text`, `format=srt`, or `format=vtt` to receive plain-text output instead of the standard response envelope.
Returns `404` when the video currently has no transcript/captions available in any language — this is a normal, non-retryable result, not an error condition.
Returns `503` when the request is temporarily blocked or rate-limited; retrying after a short delay may succeed.
Returns normalized product details for an Amazon ASIN on `amazon.com`, including pricing, availability, overview data, inline review samples, and descriptive content.
Store tool inputs, response summaries, and source identifiers so agent outputs can be audited.
Error handling
Validate required inputs before calling Crawlora
Retry 429 and temporary 5xx responses with capped backoff
Log endpoint, input, timestamp, and request ID when present
Treat empty results as a state your application can handle
Open /docs/errors for production retry guidance
Rate-limit and credit planning
Estimate usage by multiplying requests by endpoint credit cost. The table below only shows real credit costs available from the billing constants.
Endpoint
Credit cost
Docs
Search Bing web results
3 credits/request
/docs/bing/bing-search
Google Maps search API
5 credits/request
/docs/google-map/google-map-search
Search Nominatim places
1 credit/request
/docs/geocoding/geocoding-search
Search JustWatch titles
3 credits/request
/docs/just-watch/justwatch-search
Retrieve transcript for a YouTube video
3 credits/request
/docs/youtube/youtube-transcript
Search TikTok videos
8 credits/request
/docs/tiktok/tiktok-search
Search the App Store
1 credit/request
/docs/app-store/appstore-search
Search Google Play
1 credit/request
/docs/google-play/googleplay-search
Retrieve Amazon product details
2 credits/request
/docs/amazon/amazon-product
Search for products, users, or launches on Product Hunt
3 credits/request
/docs/product-hunt/producthunt-search
Production checklist
Keep API keys server-side
Use request timeouts
Back off on rate limits
Store raw responses or source IDs for auditability
Monitor credits and failures
Avoid unnecessary refreshes
Review responsible-use requirements
Responsible public web data workflows
Crawlora is designed for responsible structured public web data workflows. Customers are responsible for using Crawlora in compliance with applicable laws, third-party rights, target-platform rules, and Crawlora terms.