Crawler service online

Crawler API / asynchronous tasks

Crawler API for trackable web data tasks

Choose a Google, Reddit, TikTok or website interface, submit an authenticated asynchronous task, then retrieve its result, credits and errors by task ID.

REQUEST → TASK → RESULT

Know what comes back.

Authenticate with your console login token. Invoke returns a task ID; TaskResult returns status, output and cost. MCP keys belong to the separate Browser/MCP service. The examples below illustrate the envelope, not a guaranteed target-specific result.

1. Task accepted

{ "code": 200, "body": {
  "taskId": "example-task-id",
  "status": "running",
  "costCredits": 2
} }

2. Final result — illustration

{ "code": 200, "body": {
  "taskId": "example-task-id",
  "status": "success",
  "result": { "items": [] },
  "error": null,
  "costCredits": 2,
  "totalCostMs": 3200
} }

Results can contain strings, objects or arrays depending on the interface. Validate required fields before using them. A successful task does not guarantee complete or useful data. See requests, parameters and errors →

Choose the execution model your team needs.

Crawler API suits scheduled collection, search monitoring and content pipelines that can submit a job and process its result later. Use proxies when you want to own the crawler, or Browser/MCP for interactive browser tasks.

ApproachYou provideYou receive / manage
Crawler APIInterface + parametersTask ID, status, result and credit cost
ProxyYour own HTTP client or crawlerNetwork routing; you own parsing, retries and execution
Browser / MCPAI client instructions and MCP keyInteractive browser actions and task-specific output

Compare all three approaches →

Core capabilities

Configure, run, and inspect every task in one workspace

Each invoke has explicit inputs, credit cost, task status, and a recorded result.

Crawler interfaces

Choose the right entry point for each data target

Every card shows its purpose and credit formula. The signed-in dashboard remains the source of truth for availability and parameters.

Invoke workflow

Complete a crawler task in four steps

The dashboard handles interface selection, parameter validation, task execution, and result history.

Pricing

Choose a plan by credits and concurrency

Each purchase adds crawler credits and available concurrency. Consumption depends on the interface and parameters.

Package credits are not a guarantee of the same number of usable results. Interface parameters change task consumption. Read the cost guide →

FAQ

About Crawler Invoke