API reference
Four recursive scan profiles.
Profile limits come from the same public scan normalization and engine policy used by POST /v2/scans. They are ceilings, not expected work or result counts.
Generated limits
Choose a bounded profile.
Every request must set options.maxCredits at or below its profile maximum. The orchestrator can stop earlier when the frontier is exhausted or another bound is reached.
| Profile | Engine mapping | Max request credits | Max depth | Max jobs | Max runtime | Active authorization | Reference |
|---|---|---|---|---|---|---|---|
| Quick | quick | 500 | 2 | 500 | 300s | No active request | Open |
| Balanced | balanced | 2000 | 5 | 2000 | 1800s | No active request | Open |
| Deep Research | deep_research | 10000 | 10 | 10000 | 7200s | No active request | Open |
| Advanced Investigation | advanced_investigation | 50000 | 16 | 50000 | 14400s | Required | Open |
Maximum jobs, results, bytes, time and credits are safety ceilings. Target compatibility, evidence quality, configuration and permission determine actual scheduling. No fixed result count is promised.