Limits & quotas
Every numeric limit enforced by the platform, in one table.
Reference for capacity planning. Platform-wide unless noted per-user.
Jobs
| Limit | Value | Scope |
|---|---|---|
| Concurrent jobs per user | 5 | per user |
| Parallel-lane worker slots | 6 | platform-wide (verify_emails, delivery_check, import, filter, sort) |
| Result file retention | 7 days | per job |
| Max run time per job | 24 hours | per job; results so far are kept and the remainder is queued again automatically (see Jobs lifecycle) |
| SSE stream max duration | 6 hours | per stream |
| Max EF per job | 5 (default) | per user, adjustable up to 50 |
The parallel lane is a pool separate from the serial lane used by extraction modules.
Veille
| Limit | Value |
|---|---|
| Frequency min | 1 day |
| Frequency max | 365 days |
Pipelines
| Limit | Value |
|---|---|
| Max nodes | 20 |
| Max inputs/node | 1 (MVP) |
AI spending (BYOK)
Hard per-user caps on AI features (billed to your own provider key) with email alerts. Configurable in Settings up to 10× the default.
| Cap | Default | Max | Scope |
|---|---|---|---|
| Per request | $10 | $100 | per user |
| Per day | $10 | $100 | per user, UTC day |
| Per month | $100 | $1,000 | per user, UTC month |
Requests that would exceed a cap are blocked before the provider is ever called; you get an email at 80% and when a cap is reached. See AI spending caps.
Auth rate limits
Per-endpoint windows. Exceeding returns 429 Too Many Requests.
| Endpoint | Limit | Window |
|---|---|---|
| Signup | 3 attempts | per hour, per IP |
| Login | 5 attempts | per 15 min, per IP+email |
| Password reset request | 3 attempts | per hour, per IP+email |
| Password change (logged-in) | 5 attempts | per hour, per user |
| Resend email verification | 3 attempts | per hour, per user |
| Feedback thread creation | 20 attempts | per hour, per user |
| Session lifetime | 7 days | sliding window |
Creation quotas
Per account, shared between the session, API keys and the MCP connector. Jobs and pipelines draw on the same counter, and every attempt counts, including the ones refused by validation.
| What | Limit | Window |
|---|---|---|
Job and pipeline creations (POST /api/jobs, POST /api/jobs/<type>, POST /api/jobs/{id}/resume, POST /api/pipelines) |
30 | per 10 minutes |
| Job and pipeline creations (same endpoints) | 300 | per 24 hours |
Checks that create nothing (POST /api/pipelines/validate, POST /api/estimate) |
120 | per 10 minutes |
Beyond a limit the API answers 429 with a Retry-After header (seconds) and a message that states the limit and the wait, for example Too many launches in a short time: 30 maximum per 10 minutes. Try again in 7 minutes. Wait for the header value before retrying; retrying earlier does not shorten the wait.
These quotas apply to what an account asks for. The stages a running pipeline starts by itself, monitoring runs and automatic continuations are not counted.
To launch many pipelines, check each one with POST /api/pipelines/validate first and keep at most 5 jobs pending or running at a time.
Module-specific
scrap: 5 EF per job by default (per user, adjustable up to 50). See Job cost (EF).emails:normalanddeepmodes with different EF profiles- All multi-proxy modules:
itemsarray bounded at 1–10000 per request