01
Pick the testing surface
Choose whether the immediate target is code, binary, AI agent behavior, or runtime detection.
Evidence: Use the Products taxonomy to map the target to Nora Scan, Nora Guard, Nora Veridic, or Nora Vision.
Choose the path that matches your job, then follow numbered steps that point to live product, API, example, report, and support routes. No placeholder subpages or fake commands are required.
15-20 min / Beginner
Move from target selection to evidence-backed vulnerability review without starting from a blank product page.
Choose whether the immediate target is code, binary, AI agent behavior, or runtime detection.
Evidence: Use the Products taxonomy to map the target to Nora Scan, Nora Guard, Nora Veridic, or Nora Vision.
Read the proof module, FAQ, and comparison section for the selected product before you design a test.
Evidence: Start with Nora Scan when the target is source code or vulnerability triage.
Review the example catalog and select the smallest pattern that matches your scan or review workflow.
Evidence: Examples route to live implementation patterns instead of placeholder quickstart pages.
Choose the evidence destination before running the workflow: API response, report, support review, or buyer-facing memo.
Evidence: The Reports route is the public handoff surface for security and research artifacts.
20-30 min / Intermediate
Move from API reference to a documented engineering handoff with SDK and example routes.
Start with endpoint taxonomy, request/response expectations, and integration boundaries.
Evidence: The API documentation is the canonical reference entry for public integration handoff.
Choose the implementation language and confirm whether the SDK route or direct API route is the better first step.
Evidence: SDK guides are linked from the docs landing and developer hub for language-specific work.
Match your planned integration to an existing example before writing custom glue code.
Evidence: The examples route carries implementation patterns for scans, workflows, webhooks, and custom connectors.
Use a contact route when the integration requires API access, webhook review, or account-specific configuration.
Evidence: Contact intent links preserve context for API access requests and keep account-specific questions out of generic documentation.
25-35 min / Intermediate
Move from workflow intent to automation architecture, examples, and support review.
Write the job as trigger, decision, action, and evidence destination before selecting a product route.
Evidence: Nora Flow is the product route for security workflow orchestration, approval design, and repeatable evidence handoff.
Use the automation docs to align terminology before mapping workflow pieces.
Evidence: Automation docs provide the shared guide for orchestration and workflow design.
Identify which steps should be reusable pieces and which require custom approval logic.
Evidence: Automation docs provide the shared guide for orchestration and workflow design.
Route sensitive automation plans through contact before connecting external systems.
Evidence: The contact route carries a webhook-specific intent for implementation review.
Related resources
Need help choosing a path? Share your implementation question