Parse a document through the configured content-acquisition provider
POST
/v1/content-acquisition/parseRuntime multipart gateway used by managed agent computers. Documents may be at most 50 MB.
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: multipart/form-data · Required
| Field | Type | Required | Description |
|---|---|---|---|
| file | string | Yes | — |
| options | string | No | JSON-encoded provider parse options. |
What the API returns
Each response code below includes the documented payload shape for the ACP API.
200Provider parse response with acquisition metadataapplication/json
| Field | Type | Required | Description |
|---|---|---|---|
| computerAgents | object | Yes | — |
| computerAgents.contentAcquisition | object | Yes | — |
| computerAgents.contentAcquisition.operation | search | scrape | parse | Yes | — |
| computerAgents.contentAcquisition.provider | firecrawl | Yes | — |
| computerAgents.contentAcquisition.providerMode | hosted | local | Yes | — |
| computerAgents.contentAcquisition.usageMode | billable | observability_only | Yes | — |
| computerAgents.contentAcquisition.durationMs | number | Yes | — |
| computerAgents.contentAcquisition.creditsUsed | number | Yes | — |
400Invalid document upload
None.
413Document exceeds the 50 MB upload limit
None.
502Content-acquisition provider failure
None.
503Content acquisition is unavailable in this deployment
None.
Parse a document through the configured content-acquisition provider
Loading...
Response 200
Loading...