Developer guides
Connect Crawlora's agent-native structured public web data APIs to AI agents, LangChain workflows, hosted MCP tools, backend services, scripts, and data pipelines.
Verified HTTP pattern
POST /google/search
Request
POST https://api.crawlora.net/api/v1/google/search
x-api-key: $CRAWLORA_API_KEY
Content-Type: application/json
{
"country": "us",
"keyword": "best CRM software",
"language": "en",
"limit": 10,
"page": 1
}Base URL
https://api.crawlora.net/api/v1
Auth header
x-api-key
Example endpoint
POST /google/search
Use Crawlora as a structured public web data source in frameworks, agents, tools, and backend workflows.
Developer workflow
Build custom tools, loaders, and retrieval ingestion flows.
Open guideExpose Crawlora endpoints as callable tools for agent-native workflows.
Open guideDesign structured web data tools for agent planning and summarization.
Open guideCall Crawlora endpoints from n8n's HTTP Request node with a ready-to-import workflow template.
Open guideCall Crawlora endpoints from Make's HTTP module in no-code scenarios.
Open guideCall Crawlora endpoints from Webhooks by Zapier in no-code Zaps.
Open guideFeed structured public web data into LlamaIndex readers and retrieval pipelines.
Open guideUse Crawlora's hosted MCP endpoint for supported Crawlora endpoints.
Open guideUse the official TypeScript and JavaScript SDK from GitHub Packages.
Open guideUse the official Python SDK in scripts, notebooks, and pipelines.
Open guideBuild bounded workers with the official Go SDK module.
Open guideTest endpoints directly from the terminal.
Open guideDeveloper workflow
Use normalized fields instead of raw HTML as the primary input.
Open guideRoute each task to an endpoint designed for the source platform.
Open guideUse rendered execution where supported.
Open guideKeep proxy routing outside application logic.
Open guideSurface unusable upstream states instead of hiding them.
Open guideTrack usage and pricing impact as integrations scale.
Open guideDeveloper workflow
Use Crawlora for structured public web data workflows. Customers are responsible for compliance with applicable laws, third-party rights, platform rules, and Crawlora terms. Keep API keys server-side, validate inputs, and avoid collecting or storing unnecessary sensitive data.
Read Crawlora termsDeveloper workflow
Use these pages to move between endpoint discovery, examples, pricing, and responsible-use guidance.
Developer workflow
Common questions for this Crawlora developer integration path.
Use Crawlora with official TypeScript, Python, and Go SDKs, HTTP clients, backend services, scripts, data pipelines, LangChain-style tools, MCP workflows, and AI-agent tool calls.
Yes. Wrap Crawlora HTTP calls as custom tools, loaders, or ingestion steps.
Yes. Expose narrow Crawlora API calls as callable tools in your agent layer.
Yes. Use Crawlora's hosted MCP endpoint for supported tools, or create a lightweight MCP wrapper around HTTP endpoints when you need custom policy controls.
For repeatable workflows, normalized JSON is easier to validate, summarize, and store than arbitrary page HTML.
Crawlora uses credit-based usage, with successful 2xx responses consuming credits according to endpoint rules where applicable.
Use the SDK guides, cURL examples, and integration pages linked from this index.
Choose an endpoint, test it, then wrap it as a backend call or agent tool.