Client API errors

The exact documented responses are shown per operation in the Client API reference. Common cases in the current REST routes include:

Status	Current use
400	Zod validation, unsupported provider/model, or invalid runtime option.
401	Missing or invalid X-API-Key.
403	Package-level limits such as automation count.
404	User-scoped job, agent, or social account not found.
429	Monthly transaction limit reached.
500	Pipeline or persistence failure not mapped to a more specific status.

Asynchronous scrape and agentic jobs persist a failed status and error message when execution fails after the initial HTTP 202 response. Poll the matching status endpoint to obtain that state.