Use this when an Anchor Browser task-version request is rejected because the API key is in the wrong place.

The documented endpoint retrieves one task version. Set `TASK_ID` to the task UUID and use `latest`, `draft`, or a version number for the requested version:

```bash
TASK_ID="<task-uuid>"
curl --request GET \
  --url "https://api.anchorbrowser.io/v1/task/${TASK_ID}/latest" \
  --header "anchor-api-key: ${ANCHORBROWSER_API_KEY}"
```

For the official TypeScript SDK, configure `client.setConfig({ auth: () => process.env.ANCHORBROWSER_API_KEY })`; `auth` is a callback. For the official Python SDK, pass `api_key=...` to `Anchorbrowser(...)` or use the documented `ANCHORBROWSER_API_KEY` default. Do not commit API keys.

Check that your request uses the credential mechanism for its client and retry the same request. A successful authentication check does not establish that the task exists or that the account can perform other operations.