Rate Limits & Usage

Plans

Feature	Trial	Starter ($29/mo)	Pro ($79/mo)	Scale ($199/mo)
Pages processed / month	100	1,000	10,000	50,000
Search queries / month	500	5,000	50,000	200,000
API rate limit	5 req/s	10 req/s	50 req/s	200 req/s

All plans include the full feature set — embedding, reranking, metadata filtering, and SDKs. Plans differ only in volume limits.

Usage Metering

Usage is tracked per billing period:

• Pages processed — Tier 1 files use the actual page count. Tier 2 files estimate at 1 page per ~3,000 bytes.
• Search queries — Each POST /v1/knowledge-bases/:kb_id/search call counts as one query.

Check your current usage at any time:

curl https://api.useragex.com/api/v1/usage \
  -H "Authorization: Bearer YOUR_API_KEY"

Response:

{
  "data": {
    "current_period_start": "2026-02-01T00:00:00.000Z",
    "current_period_end": "2026-03-01T00:00:00.000Z",
    "plan": "starter",
    "limits": {
      "pages_processed": 1000,
      "search_queries": 5000
    },
    "usage": {
      "pages_processed": 342,
      "search_queries": 1205
    },
    "percentage_consumed": {
      "pages": 34,
      "queries": 24
    }
  }
}

Rate Limiting

API rate limits are enforced per-account based on your plan. When exceeded, the API returns:

HTTP 429 Too Many Requests

{
  "error": {
    "code": "RATE_LIMIT_EXCEEDED",
    "message": "Rate limit exceeded"
  }
}

Best practices:

• Add exponential backoff with jitter to your retry logic
• Use the SDKs, which handle basic retry logic
• If you consistently hit rate limits, upgrade your plan

Usage Limits

When you exceed your monthly pages or queries limit, the API returns:

HTTP 429 Too Many Requests

{
  "error": {
    "code": "USAGE_LIMIT_EXCEEDED",
    "message": "Usage limit exceeded for search_queries. Upgrade your plan or wait for the next billing period.",
    "details": {
      "resource": "search_queries",
      "limit": 5000,
      "used": 5000
    }
  }
}

Usage resets at the start of each billing period.