Skip to main content

Rate Limits

API requests are rate-limited to ensure fair usage. Cached reads are free — only realtime scraping and expansion consume credits from your unified monthly pool.

Credit Costs

Free Endpoints (0 credits, rate-limited only)

Reading cached data costs nothing — browse and search freely.

  • GET /api/v1/requests (default cached reads)
  • POST /api/v1/requests/search (without expand)
  • GET /api/v1/topics

Realtime Requests (1 credit each)

Live scraping via API consumes credits.

  • GET /api/v1/requests?source=realtime
  • POST /api/v1/requests/search with expand=true

Web Scraping (depth x platforms credits)

Each page of results per platform costs 1 credit. A scrape with depth=3 across 2 platforms costs 6 credits.

Credits by Plan

PlanCreditsRate Limit
Free100 / monthly20 req/min
Pro5,000 / monthly120 req/min
Max15,000 / monthly240 req/min

See pricing for plan details.

Pay As You Go

When your subscription credits run out, PAYG credits are used automatically. Credit packs never expire.

PackPriceCredits
Starter$51,300
Standard$205,300
Bulk$5013,500

Purchase from Settings. Check your PAYG balance via the paygBalance field in GET /api/v1/usage.

Checking Your Usage

Use the GET /api/v1/usage endpoint to check your current usage:

{
  "data": {
    "tier": "free",
    "credits": {
      "used": 42,
      "limit": 100,
      "remaining": 58,
      "resetsAt": "2025-02-01T00:00:00.000Z"
    }
  }
}

This endpoint is free and does not consume credits.

Rate Limit Response

When you exceed your limit, you'll receive a 429 response:

{
  "error": {
    "code": "RATE_LIMITED",
    "message": "Credit limit exceeded (100/100). Resets on 2025-02-01."
  }
}

Tips to Stay Within Limits

  • Use lower scrape depth when exploring new topics
  • Cache responses on your end to reduce API calls
  • Use pagination efficiently - don't fetch more than you need
  • Monitor usage with the /usage endpoint