Web Tasks API: batch extraction, crawling and research

Run batch extraction, crawling or public-page research in the background. Start a job, follow its progress and collect the result, or cancel pending work.

Web Tasks

Three kinds of asynchronous work: batch extraction, crawling and research. A successful start is acceptance, not completion.

MCP tool	HTTP route	What it does
`web_scrape_batch`	`POST /tasks/v1/scrape/batch`	Start a batch extraction job from a supplied list of URLs.
`web_batch_status`	`GET /tasks/v1/scrape/batch/{id}`	Read batch status and collect its results.
`web_batch_status`	`POST /tasks/v1/scrape/batch/{id}/cancel`	Cancel pending batch work. With MCP, send cancel: true.
`web_crawl`	`POST /tasks/v1/crawl`	Start a crawl job that discovers and reads linked pages.
`web_crawl_status`	`GET /tasks/v1/crawl/{id}`	Read crawl status and collect its results.
`web_crawl_status`	`POST /tasks/v1/crawl/{id}/cancel`	Cancel pending crawl work. With MCP, send cancel: true.
`web_task_start`	`POST /tasks/v1/research`	Start research from public pages and return an answer with sources.
`web_task_status`	`GET /tasks/v1/research/{id}`	Read research progress, sources, result and billing.
`web_task_cancel`	`POST /tasks/v1/research/{id}/cancel`	Cancel pending research work.

Batch extraction and crawling

Use web_scrape_batch for a supplied list of URLs and web_crawl to discover linked pages. Starts return jobId. Check web_batch_status or web_crawl_status; send cancel: true to those MCP tools to stop pending work. HTTP uses the explicit status and cancellation routes above. Use the owning account key or wallet credentials; do not buy another execution to read status.

Research tasks

Describe a research question and optionally provide up to five public URLs. Task plans, searches, reads and synthesizes an answer with sources. It currently does not orchestrate crawling or browser actions.

{
  "task": "Read this public pricing page and summarize the plans with source links.",
  "mode": "research",
  "urls": [
    "https://oassis.dev/"
  ]
}

HTTP: POST /tasks/v1/research. MCP: web_task_start. Creation returns an ID. Use the same API key for status and cancellation; x402 creation also returns an access_token.

For HTTP status, call GET /tasks/v1/research/{id}; for cancellation, call POST /tasks/v1/research/{id}/cancel. For an API-key task, send the owning Authorization: Bearer key. For an x402 task, send Task-Token: YOUR_ACCESS_TOKEN with both requests. For MCP, use web_task_status or web_task_cancel with {"id":"TASK_ID","access_token":"TASK_TOKEN"}.

MCP task creation requires an API key and reserves the maximum budget; actual execution cost is charged and unused credits are released. API-key HTTP reserves credits and settles actual cost. HTTP/x402 charges the selected limits.max_cost_usd execution package upfront ($0.10 by default). Status and cancellation are free with the task token. Unused budget has no automatic on-chain refund. Inspect status, sources and missing evidence: research may return a partial result.

Start with account credits

curl -i -X POST https://api.oassis.dev/tasks/v1/research -H 'Authorization: Bearer YOUR_API_KEY' -H 'Idempotency-Key: research-001' -H 'Content-Type: application/json' -d '{"task":"Research public hosting providers","limits":{"max_cost_usd":0.1}}'

A $0.10 maximum reserves 50 credits. Actual costs are charged and unused credits are released. Use the same key for status and cancellation.

Start over HTTP with x402

An unpaid start returns 402. Use an x402-capable client to pay the quote and retry; plain curl does not complete payment.

curl -i -X POST https://api.oassis.dev/tasks/v1/research   -H 'Content-Type: application/json'   -d '{"task":"Read this public pricing page and summarize the plans with source links.","mode":"research","urls":["https://oassis.dev/"],"limits":{"max_cost_usd":0.1}}'

Read progress and results

curl -i https://api.oassis.dev/tasks/v1/research/TASK_ID   -H 'Task-Token: YOUR_ACCESS_TOKEN'

Inspect the returned status and result. Open the source links and check missing evidence before relying on an answer. Status is free with the task token.

Cancel a task

curl -i -X POST https://api.oassis.dev/tasks/v1/research/TASK_ID/cancel   -H 'Task-Token: YOUR_ACCESS_TOKEN'

Cancellation is free with the task token. It does not automatically refund the HTTP execution package.

Use Web Tasks through MCP

web_task_start
{"task":"Read this public pricing page and summarize the plans with source links.","mode":"research","urls":["https://oassis.dev/"]}

web_task_status
{"id":"TASK_ID","access_token":"TASK_TOKEN"}

web_task_cancel
{"id":"TASK_ID","access_token":"TASK_TOKEN"}

Connect to https://api.oassis.dev/mcp. Task creation requires an API key and reserves credits; status and cancellation are free for the owning account. The access token belongs to one task; it is not a general API key.

Continue with MCP integration, x402 payments or the OpenAPI reference.