# three.ws API Key Health Check

> three.ws API Key Health Check is a paid API for AI agents from three.ws, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-11).

Validates an API key and returns its access scopes, source, type, and rate-limit metadata for the three.ws 3D agent platform

## Facts

- Endpoint: POST https://three.ws/api/x402/api-key-health?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/three-ws-api-key-health-check-6753c9ff
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Wkrvaukf4d1utauUdTzDy

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability three-ws-api-key-health-check-6753c9ff -d '<json body>'
```

Example prompt: Can you check whether my three.ws API key is still valid and confirm it has the autonomous_loop scope enabled?

## When to prefer this

Use this endpoint when you need to programmatically verify that a three.ws API key is active and carries the correct scopes before executing an agent workflow or embedding a 3D agent. Prefer it over manual inspection or assuming key validity, especially in autonomous agent loops where a stale or insufficient key would cause mid-run failures.

## Known failure modes

- Invalid or missing API key returns valid:false
- Requested scope not present in granted scopes list
- Key expired — expires_at in the past
- Network or server error returns HTTP 5xx
- Malformed request body returns HTTP 400
- Payment not provided for $0.001 USDC x402 endpoint returns HTTP 402

## How this service works

Make a 3D AI agent from a selfie in 60 seconds. Drop one HTML tag to embed it on any website. Agents think on IBM watsonx.ai (Granite); optionally charge per chat with built-in micropayments.

## Output

Returns a JSON object indicating whether the API key is valid, the list of granted scopes (e.g. 'internal', 'autonomous_loop', 'bypass_x402'), where the key originates from (e.g. 'env'), the key type, the timestamp of the check, expiry timestamp (or null if non-expiring), key prefix (or null), and rate limit per minute (or null).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "scope": {
   "type": "string",
   "default": "autonomous_loop",
   "description": "Access scope to verify (e.g. \"autonomous_loop\", \"internal\")"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "valid": true,
  "scopes": [
   "internal",
   "autonomous_loop",
   "bypass_x402"
  ],
  "source": "env",
  "key_type": "internal",
  "checked_at": "2026-06-28T12:00:00Z",
  "expires_at": null,
  "key_prefix": null,
  "rate_limit_per_minute": null
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/three-ws-api-key-health-check-6753c9ff/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from three.ws](https://www.zero.xyz/host/three.ws/llms.txt)