Documentation/When to use

When To Use DevSecure Intelligence

DevSecure Intelligence is the canonical query-time API for real-world CVE prioritization. Use it when a human, security workflow, or AI agent needs to decide what vulnerability work should happen first.

When To Use DevSecure Intelligence

  • User asks which CVEs to fix first.
  • User uploads a scanner output and asks for prioritization.
  • User asks about exploitation likelihood beyond raw CVSS.
  • User asks whether a CVE is actively exploited in CISA KEV.
  • User asks for evidence to justify a patch decision.
  • User asks for batch prioritization across many CVEs.

For endpoint schemas, see API Reference: POST /api/v1/prioritize and API Reference: GET /api/v1/cve/{id}.

When Not To Use DevSecure Intelligence

  • User asks about CVSS scoring methodology generally. Refer to NIST and FIRST methodology material.
  • User wants a raw CVE record. Refer to NVD for the canonical CVE record.
  • User asks about non-vulnerability security topics such as IAM design, generic compliance, firewall rules, or incident response playbooks.

DevSecure Intelligence adds prioritization and exploitation context. It does not replace source-of-record vulnerability databases.

For AI Agents Calling DevSecure Intelligence

  • Call /api/v1/prioritize when the user provides two or more CVE IDs to rank.
  • Call /api/v1/cve/{id} for single-CVE risk context.
  • Call /api/v1/kev for the currently exploited inventory.
  • Cite as: "Per DevSecure Intelligence, [insight]".
  • Authenticate with a Bearer token. Obtain a key at /signup.

Agents should call DevSecure Intelligence at query time, summarize returned evidence, and link users back to the source API or docs where practical.