Scrape a URL through the configured content-acquisition provider

POST/v1/content-acquisition/scrape

Runtime gateway used by managed agent computers. The provider payload is forwarded and augmented with Computer Agents acquisition metadata.

How to call this endpoint

Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.

Path, query, and header parameters

These parameters control which ACP object the endpoint acts on and how the request is processed.

Path parameters
None.
Query parameters
None.

Body schema

Content type: application/json · Required

FieldTypeRequiredDescription
urlstringYes
formatsmarkdown | html | rawHtml | links | images | summary[]No
onlyMainContentbooleanNo
removeBase64ImagesbooleanNo
blockAdsbooleanNo
timeoutintegerNo
waitForintegerNoOptional post-load rendering wait in milliseconds. Must not exceed half of timeout; no browser actions are enabled.
includeTagsstring[]No
excludeTagsstring[]No

What the API returns

Each response code below includes the documented payload shape for the ACP API.

200Provider scrape response with acquisition metadataapplication/json
FieldTypeRequiredDescription
computerAgentsobjectYes
computerAgents.contentAcquisitionobjectYes
computerAgents.contentAcquisition.operationsearch | scrape | parseYes
computerAgents.contentAcquisition.providerfirecrawlYes
computerAgents.contentAcquisition.providerModehosted | localYes
computerAgents.contentAcquisition.usageModebillable | observability_onlyYes
computerAgents.contentAcquisition.durationMsnumberYes
computerAgents.contentAcquisition.creditsUsednumberYes
400Invalid or disallowed scrape request
None.
502Content-acquisition provider failure
None.
503Content acquisition is unavailable in this deployment
None.
Scrape a URL through the configured content-acquisition provider
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow