Spawn an agent for an assessment
POST/api/v1/assessments/:assessment_id/agents/spawn
Spawn an ad-hoc agent against an assessment's project context.
The spawned agent inherits the full project store and can
read/write all prior discovery data (sitemap, vulnerabilities, test
plan, etc.). Only allowed while the assessment is running,
completed, or scope_review.
- Scope required:
assessments:update+ write permission. - Rate-limit tier: read/default.
- Not idempotent — each call spawns a fresh agent.
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 409
- 422
- 429
- 500
Successful Response
Bad request — malformed input or failed validation.
Missing, expired, or invalid credentials.
Authenticated but not authorized for this resource. Note: cross-organization reads return 404, not 403.
Resource not found, or hidden for tenant-enumeration safety (the caller lacks permission to know whether the resource exists).
Conflict — the current resource state does not allow this operation (e.g. assessment already started, email already in use).
Semantic validation failure — request shape was valid but contents were not.
Too many requests — rate limited. Retry after the window resets.
Internal server error — unexpected failure.