# Analyze a Cloudflare checkup

> AI remediation suggestions for a saved Cloudflare Checkup.

Source: https://docs.vigilbase.com/one/api/reference/services/post-services-cloudflare-checkups-analyze

`POST https://one.vigilbase.com/api/services/cloudflare/checkups/analyze`

AI remediation suggestions for a saved Cloudflare Checkup. The client names the run; the result is read server-side within the caller's tenant scope, never taken from the request body.

## Authorizations

Send one of these:

- `Authorization` (string, header, required): Bearer access token from Vigilbase Identity (`auth.vigilbase.com`), sent as `Authorization: Bearer <token>`. The CLI gets one with `vigilbase login`.
- `Authorization` (string, header, required): Organisation API key (`vb_one_…`) from **Settings → API keys** in Vigilbase One, sent as `Authorization: Bearer vb_one_…`. Needs a key with write access: read-only keys get `403` with the code `read_only_key`. See [organisation API keys](https://docs.vigilbase.com/one/api#organisation-api-keys).

## Body (application/json)

- `toolRunId` (string, required)
- `customerId` (string)

## Responses

### 200

Success

### 401

Authentication required

### 403

Not permitted

## Example request

```bash
# Token from `vigilbase login`, or a write API key (vb_one_…)
curl --request POST \
  --url 'https://one.vigilbase.com/api/services/cloudflare/checkups/analyze' \
  --header "Authorization: Bearer $VIGILBASE_TOKEN" \
  --header 'Content-Type: application/json' \
  --data '{"toolRunId":"<uuid>","customerId":"<uuid>"}'
```