The documented REST API uses the /api/v1/ prefix. MCP tools call operations backed by the same API surface and can also change as tools are added or corrected.

​
Change policy

​
Client requirements

  • Parse required fields explicitly and tolerate unknown fields.
  • Do not depend on JSON object key order.
  • Handle error status independently from the exact error-body shape.
  • Pin generated clients to a reviewed OpenAPI version.
  • Re-run integration tests after OpenAPI or MCP tool changes.

​
Deprecation notices

A deprecation notice should identify the affected endpoint or tool, replacement, migration steps, date announced, and planned removal date. Breaking changes should be recorded in the FullHunt Product Changelog.

​
Current compatibility notes

  • REST authentication uses X-API-KEY, not bearer authentication.
  • Enterprise impersonation filters use q.
  • OEM exposes oem_scan_status; standard and Enterprise scan workflows do not.
  • The MCP server currently defines 63 tools. Clients should refresh cached tool lists after releases.