> ## Documentation Index
> Fetch the complete documentation index at: https://docs.keenable.ai/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Every page is listed in https://docs.keenable.ai/llms.txt. To pick a product for a job, read https://docs.keenable.ai/choose.md
> Setup steps for agents, covering the SDKs, the MCP server and the CLI: https://docs.keenable.ai/skill.md
> Keenable search and fetch work without an API key. To add them to code, use the official SDK for the project's language: https://docs.keenable.ai/sdks.md
> Without a key, call POST https://api.keenable.ai/v1/search/public or GET https://api.keenable.ai/v1/fetch/public with an X-Keenable-Title header that names your app.
> With a key, send it in the X-API-Key header and read it from the KEENABLE_API_KEY environment variable. Never ask a user to paste a key into chat. Every access method: https://docs.keenable.ai/auth.md
> To get an API key without the console, use device login: https://docs.keenable.ai/authentication.md#device-login
> MCP server: https://api.keenable.ai/mcp (no key, or X-API-Key; keyless Codex uses https://api.keenable.ai/mcp-public), or https://api.keenable.ai/mcp-oauth for OAuth sign-in. These docs are an MCP server at https://docs.keenable.ai/mcp and the OpenAPI spec is at https://docs.keenable.ai/api-reference/openapi.json
> Keenable searches and fetches public web pages. If a question needs no web information, skip the call.
> On 402 with an API key (code insufficient_credits), stop and ask a human to add credits; don't retry. On 429, wait the number of seconds in Retry-After, then retry. Before you ship, follow https://docs.keenable.ai/production.md
> Every error, with its cause and fix, is in https://docs.keenable.ai/errors.md and moving from another search API is covered in https://docs.keenable.ai/migrate.md
> Before you compare Keenable with another search API, read https://docs.keenable.ai/guides/evaluate-search-apis.md

# Count monitors

> Count your organization's monitors by status and by kind of schedule with GET /v1/monitors/stats.

Count your organization's monitors by status and by kind of schedule, without paging through the list. `manual` counts monitors without a schedule.

## When to use it

Use it on a dashboard, or before you create many monitors, to see how many are active. Your organization's active monitors count toward a limit. See [Limits](https://docs.keenable.ai/products/monitors#limits). A response looks like this:

```json theme={"theme":{"light":"github-light-high-contrast","dark":"dark-plus"}}
{
  "total": 12,
  "by_status": { "active": 9, "paused": 2, "disabled": 0, "completed": 1 },
  "by_schedule": { "cron": 5, "interval": 3, "once": 1, "manual": 3 }
}
```

A non-zero `disabled` count means Keenable stopped some monitors. Find them with [List monitors](https://docs.keenable.ai/api-reference/monitors/list.md) and `status=disabled`.

## SDK, CLI and MCP

| Client | Call |
| - | - |
| Python, TypeScript | `client.monitors.stats()` |
| Go | `client.Monitors.Stats(ctx, nil)` |
| Rust | `client.monitors().stats()` |
| CLI | `keenable monitors stats` |
| MCP | No tool. Use the API, an SDK or the CLI. |

The SDK methods need SDK 0.2.0 or later. See [SDKs → Monitors](https://docs.keenable.ai/sdks.md#monitors) and [CLI → Monitors](https://docs.keenable.ai/cli.md#monitors).

## Related operations

* [List monitors](https://docs.keenable.ai/api-reference/monitors/list.md) lists the monitors behind each count.
* [Bulk actions](https://docs.keenable.ai/api-reference/monitors/bulk.md) pauses or deletes monitors by status.


## OpenAPI

````yaml GET /v1/monitors/stats
openapi: 3.0.3
info:
  title: Keenable API
  version: 1.0.0
  description: Web search, page fetching and monitors API.
servers:
  - url: https://api.keenable.ai
    description: Production
security:
  - apiKey: []
  - bearerAuth: []
paths:
  /v1/monitors/stats:
    get:
      tags:
        - Monitors
      summary: Count monitors
      description: >-
        Counts of your organization's monitors by status and by kind of
        schedule.
      operationId: monitors.stats
      responses:
        '200':
          description: The counts
          headers:
            X-Request-Id:
              $ref: '#/components/headers/XRequestId'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MonitorStats'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/MonitorForbidden'
        '429':
          $ref: '#/components/responses/MonitorRateLimited'
        '503':
          $ref: '#/components/responses/MonitorsUnavailable'
components:
  headers:
    XRequestId:
      description: ID of this request. Include it when you report a problem.
      schema:
        type: string
    RetryAfter:
      description: Seconds to wait before retrying.
      schema:
        type: integer
      example: 1
  schemas:
    MonitorStats:
      type: object
      required:
        - total
        - by_status
        - by_schedule
      properties:
        total:
          type: integer
          example: 12
        by_status:
          type: object
          additionalProperties:
            type: integer
          description: >-
            How many monitors have each status, for example `{"active": 9,
            "paused": 2, "disabled": 0, "completed": 1}`.
        by_schedule:
          type: object
          additionalProperties:
            type: integer
          description: >-
            How many monitors have each kind of schedule; `manual` counts
            monitors with no schedule. For example `{"cron": 5, "interval": 3,
            "once": 1, "manual": 3}`.
    ApiError:
      type: object
      required:
        - error
      properties:
        error:
          type: string
          description: Short error title, such as `Invalid parameter` or `Not found`.
          example: Invalid parameter
        message:
          type: string
          description: What went wrong and what to change. Sometimes absent.
          example: '"max_results": must be an integer between 1 and 50'
        details:
          description: Structured details, when the error has any.
        retryAfter:
          type: integer
          description: >-
            Seconds to wait before retrying. Present on `429` responses from
            Keenable's own rate limits, matching the `Retry-After` header.
  responses:
    Unauthorized:
      description: >-
        No key was sent (`Missing authentication`), or the key is malformed,
        unknown or has the wrong prefix (`Authentication failed`, with
        `Malformed API key` or `Invalid API key` in `message`). Send a valid key
        in `X-API-Key` or `Authorization: Bearer`.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ApiError'
    MonitorForbidden:
      description: >-
        Your key is valid but can't do this. `monitors_not_enabled`: Monitors is
        turned off for your organization; contact support@keenable.ai.
        `monitor_limit_reached`: your organization already has 100 active
        monitors; pause or delete one, then retry.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ApiError'
    MonitorRateLimited:
      description: >-
        Your organization sent more than 120 Monitors requests, or more than 10
        creates, in the last minute (`rate_limited`). Wait, then retry.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ApiError'
      headers:
        Retry-After:
          $ref: '#/components/headers/RetryAfter'
    MonitorsUnavailable:
      description: >-
        The Monitors service didn't answer (`monitors_unavailable`). The request
        may not have been applied. Retry after a few seconds; retry a create
        with the same `Idempotency-Key`.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ApiError'
      headers:
        Retry-After:
          $ref: '#/components/headers/RetryAfter'
  securitySchemes:
    apiKey:
      type: apiKey
      in: header
      name: X-API-Key
      description: >-
        Your API key, such as `keen_...`. Create one in the Keenable console. If
        you send both this header and `Authorization`, the API uses this one.
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        Your API key sent as `Authorization: Bearer keen_...`, for clients that
        only support bearer tokens.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.