Search intelligence
Monitor rankings, suggestions, result pages, and competitive visibility across Google surfaces.
Web scraping API platform
Explore documented REST endpoints and MCP tool metadata, test requests in Playground, and move production workloads into a console that tracks keys, usage, and response context.
Documented operations
107
Public API surface
MCP tools
17
AI-agent callable metadata
API-key routes
107
Production scraping surface
107 endpoints
API key routes
0 endpoints
Session routes
0 endpoints
Public routes
17 tools
MCP tool metadata for AI agents
Use cases
Crawlora exposes common scraping targets as documented operations, so developers can focus on the product logic around the data.
Monitor rankings, suggestions, result pages, and competitive visibility across Google surfaces.
Collect product detail, search, review, and category signals from commerce platforms.
Build pipelines for creator, tag, playlist, profile, and transcript intelligence.
Pull app metadata, rankings, ratings, privacy disclosures, and review streams.
Expose app and marketplace lookups as named MCP tools that agents can call from structured workflows.
API surface
Filter the live catalog by product surface and auth mode, then open the exact endpoint in Docs or Playground. Supported endpoints also surface MCP tool names for agent workflows.
Product catalogs
16 surfaces
Interactive catalog
107 matches
/amazon/product/{asin}apiKeyAmazonRetrieve Amazon product details
/amazon/searchapiKeyAmazonSearch Amazon products
/amazon/suggest/{keyword}apiKeyAmazonRetrieve Amazon search suggestions
/appstore/appapiKeyMCP appstore.appAppStoreRetrieve full App Store app details
/appstore/developer/{dev_id}apiKeyMCP appstore.developerAppStoreRetrieve apps by developer ID
/appstore/listapiKeyMCP appstore.listAppStoreRetrieve App Store collection rankings
/appstore/privacy/{id}apiKeyMCP appstore.privacyAppStoreRetrieve App Store privacy disclosures
/appstore/ratingsapiKeyMCP appstore.ratingsAppStoreRetrieve App Store ratings histogram
Workflow
The same console path covers API selection, request testing, credentials, and the operational data needed after launch.
Search the catalog by path, product surface, method, or auth requirement.
Open generated docs with parameters, body fields, examples, and response notes.
Send a request from Playground with generated inputs and response modes.
Track API keys, request usage, response context, and recent integration activity.
Production integration
Docs and testing are only the start. Crawlora also gives developers a path to credentials, usage context, and protected operations.
Docs, Playground, REST paths, and MCP tool names read from the same Swagger-backed source.
Public, session, API key, and admin routes are labeled before a developer tries a call.
Console views surface request volume, request ids, response context, and recent usage signals.
Agent builders can map supported endpoints such as App Store and Google Play lookups to MCP tool calls.
Account routes keep sensitive controls behind the expected auth mode.
Protected controls stay separated from public and API-key routes in the catalog.
Start with the API surface