# three.ws x402 Rate Limit Probe

> three.ws x402 Rate Limit Probe 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).

Checks the current rate limit status, remaining call quota, and daily spending capacity for a specific three.ws x402-gated endpoint

## Facts

- Endpoint: POST https://three.ws/api/x402/rate-limit-probe?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-x402-rate-limit-probe-c2ce64ca
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5NG0PBMmu56-et_oAj0wD

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-x402-rate-limit-probe-c2ce64ca -d '<json body>'
```

Example prompt: Before sending another request to the three.ws crypto-intel endpoint, check whether I still have remaining calls today and whether any cooldown is active — I need to know my limit, how many I've used, and when the quota resets.

## When to prefer this

Use this endpoint when you need to programmatically check rate limit headroom before invoking a three.ws x402-gated API, or when implementing retry logic that should back off during cooldowns. It is the canonical pre-flight check for any agent that loops over three.ws endpoints and needs to avoid hitting hard limits or wasting micropayment budget.

## Known failure modes

- Missing or invalid 'input' object returns a 400 validation error
- Unsupported HTTP method in the 'method' enum field causes rejection
- Invalid bodyType value outside 'json', 'form-data', 'text' causes schema rejection
- Payment not included or insufficient USDC ($0.001 required) results in 402 Payment Required
- Network timeout if the three.ws service is temporarily unavailable

## 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 with the endpoint's call limit, remaining calls today, daily cap in atomic units, daily amount spent in atomic units, remaining capacity in atomic units, price per call in atomic units, reset timestamp, and whether a cooldown is currently active along with its TTL in seconds.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "type": "object"
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST",
      "PUT",
      "PATCH"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "limit": 500,
  "endpoint": "/api/x402/crypto-intel",
  "reset_at": "2026-06-29T00:00:00.000Z",
  "price_atomic": 10000,
  "cooldown_active": false,
  "remaining_calls": 42,
  "daily_cap_atomic": 5000000,
  "daily_spent_atomic": 4580000,
  "cooldown_ttl_seconds": null,
  "remaining_capacity_atomic": 420000
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/three-ws-x402-rate-limit-probe-c2ce64ca/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)