# Watch Trends API

> Watch Trends API is a paid API for AI agents from agents.smarterway.tech, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Retrieves a list of watch trends, likely covering popular or trending wristwatch models, brands, or market data.

## Facts

- Endpoint: GET https://agents.smarterway.tech/services/watch-trends/v1/watches
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/watch-trends-api-f960e8af
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_O-qHfbF5jZDL67siodNzE

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 watch-trends-api-f960e8af
```

Example prompt: Can you pull up the current watch trends for me — I want to see what wristwatch models or brands are popular right now?

## When to prefer this

Choose this endpoint when you need real-time or current trending watch data, particularly for market research, gift inspiration, retail intelligence, or consumer interest analysis in the watch/timepiece domain. It is a lightweight, low-cost ($0.01 USDC) GET endpoint suitable for frequent polling or on-demand lookups.

## Known failure modes

- Invalid or missing query parameters may return a 400 error
- Authentication or payment failure (x402) if the $0.01 USDC microtransaction is not completed
- Service unavailable or timeout returning a 503 or 504
- Empty result set if no trending watches are currently indexed
- Malformed response if the upstream data source is unavailable

## How this service works

watch-trends POST /watches

## Output

A list of trending watches, potentially including watch names, brands, models, popularity metrics, or other trend-related attributes returned as a JSON response.

## 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"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "DELETE",
      "GET",
      "HEAD"
     ],
     "type": "string"
    },
    "headers": {
     "type": "object",
     "additionalProperties": {
      "type": "string"
     }
    },
    "queryParams": {
     "type": "object",
     "additionalProperties": true
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/watch-trends-api-f960e8af/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agents.smarterway.tech](https://www.zero.xyz/host/agents.smarterway.tech/llms.txt)
