Illustrative console workflow
MIYAIP Crawler / New invoke
Task status
Crawler API / asynchronous tasks
Choose a Google, Reddit, TikTok or website interface, submit an authenticated asynchronous task, then retrieve its result, credits and errors by task ID.
Illustrative console workflow
Task status
REQUEST → TASK → RESULT
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.
{ "code": 200, "body": {
"taskId": "example-task-id",
"status": "running",
"costCredits": 2
} }{ "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 →
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.
| Approach | You provide | You receive / manage |
|---|---|---|
| Crawler API | Interface + parameters | Task ID, status, result and credit cost |
| Proxy | Your own HTTP client or crawler | Network routing; you own parsing, retries and execution |
| Browser / MCP | AI client instructions and MCP key | Interactive browser actions and task-specific output |
Core capabilities
Each invoke has explicit inputs, credit cost, task status, and a recorded result.
SCHEMA / INPUT
See only the fields supported by the selected interface, with less setup and fewer invalid requests.
BASE + VARIABLE
Review base credits and parameter-driven cost before starting a task.
QUEUE / STATUS
Follow a crawler task from queue to running and completed states.
RESULT / HISTORY
Inspect results, errors, duration, and previous invokes from one place.
Crawler interfaces
Every card shows its purpose and credit formula. The signed-in dashboard remains the source of truth for availability and parameters.
SEARCH / GOOGLE
Collect Google search results.
REDDIT / LIST
Collect posts from a subreddit list (URL is case-sensitive).
REDDIT / COMMENTS
Collect top-level comments from a Reddit post.
TIKTOK / COMMENTS
Collect top-level comments from a TikTok video.
WEB / CONTENT
Collect website content; confirm HTML, Markdown and other output options in the interface schema. Target availability varies.
Invoke workflow
The dashboard handles interface selection, parameter validation, task execution, and result history.
Choose search, social comments, or a general website crawl for the target.
Provide the target, item limits, and supported advanced options.
Confirm estimated credits, submit the task, and follow its status.
Read the output and use crawler logs to review requests and duration.
> Result saved. Continue reviewing it from Crawler Logs.
Pricing
Each purchase adds crawler credits and available concurrency. Consumption depends on the interface and parameters.
Credits for asynchronous tasks
Credits for asynchronous tasks
Credits for asynchronous tasks
Package credits are not a guarantee of the same number of usable results. Interface parameters change task consumption. Read the cost guide →
FAQ
Ready to start