---
title: "Verify Claude on a computer"
description: "Checks the account's Claude login for the computer's claude command."
canonical: "https://www.cool.computer/docs/api-reference/integrations/verify-claude-on-a-computer"
---
# Verify Claude on a computer

> Checks the account's Claude login for the computer's claude command.

```http
POST https://api.cool.computer/api/computers/{id}/provider-credentials/claude/verify
```

Checks the account's Claude login for the computer's claude command. 401 means the login must be renewed with cool integrations connect claude. Callers: an account bearer, or the computer's own runtime token (which `cool` uses inside the VM) for this computer.

## Authorization

- A Cool Computers API key, user access token, or claimed agent access token in the Authorization header. Follow https://www.cool.computer/auth.md for agent registration and https://www.cool.computer/authentication.md for direct user credentials.

## Parameters

- `id` (path, string, at least 1 characters, required): The computer's name, such as agent-atlas, or its id (cmp_…). Every caller may use either, the computer's own runtime token included.

## Responses

- `204`: The Claude login is healthy.
- `400`: Bad Request.
- `401`: Unauthorized.
- `404`: Not Found. `computer_not_found`: the computer does not exist or is not yours.
- `429`: Too Many Requests. If the problem code is api_request_rate_exceeded, wait for Retry-After seconds; other problem codes describe a separate limit.
- `500`: Internal Server Error.
- `503`: Service Unavailable.
- `default`: A machine-readable API error with a stable code and recovery instruction.

An error is an `application/problem+json` document with a stable `code`; [API errors](/docs/api-reference/errors) says how to handle one.

## Example

```sh
curl -X POST "https://api.cool.computer/api/computers/$PARAM_ID/provider-credentials/claude/verify" \
  -H "authorization: Bearer $TOKEN"
```
