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

> ## Agent Instructions
> Setting up Context.dev for a user? Follow https://docs.context.dev/agent-quickstart.md. MCP clients sign in with OAuth and need no API key; application code reads CONTEXT_DEV_API_KEY.

# Limits and errors

> Manage monitor allowances and handle state, validation, and access failures.

Use `GET /monitors/limits` to read the organization’s allowance and current count. Paused monitors still count. Current plan defaults are in [Plans and billing](/account/billing#plan-limits).

## Limits

Monitor names accept 1–200 characters and tags allow up to 20 values. Targets and webhook receivers must use public HTTP(S) URLs. Target-specific limits are in [Targets](/monitors/targets); schedule limits are in [Schedules](/monitors/schedules).

The Monitors API has an organization-wide limit of 1,000 requests per minute. The separate Webhook Deliveries API allows 600. See [rate limits](/optimization/rate-limits).

## Errors

| Status and code | Action |
| - | - |
| `400 INPUT_VALIDATION_ERROR` | Correct the target/detection pair, schedule, or fields. |
| `401` | Check the key and balance. |
| `403 MONITOR_LIMIT_EXCEEDED` | Delete unused monitors or change the allowance; pausing does not free a slot. |
| `403 INSUFFICIENT_PERMISSIONS` | Grant the required monitor scope. |
| `404 NOT_FOUND` | Check the organization and resource ID. |
| `409 MONITOR_PAUSED` | Resume before requesting Run now. |
| `409 MONITOR_NO_WEBHOOK` | Configure a webhook before rotating its secret. |
| `429 RATE_LIMITED` | Honor `Retry-After`. |
| `503 SEARCH_UNAVAILABLE` | Retry or list without search filters. |

## Runs and usage

A run failure appears in the run record and monitor `last_error`. Failed monitors continue on schedule until they recover or are automatically paused; see [Schedules](/monitors/schedules).

`GET /monitors/credit-usage` returns settled usage, sorted highest first, over at most the 10,000 most recent runs in the selected window. Use shorter windows for high-volume accounts. Read [runs and changes](/monitors/runs-and-changes) for result states.