Developer surface
API and SDK surfaces for teams that want to embed the diagnostic layer.
Use the hosted scan first. When you need the engine inside your own workflow, move to the API, SDK, schema, and profile-aware outputs shown here.
Public endpoints
These routes go live once the API bundle is deployed. Until then, the schema, registries, and vectors on this site show the exact contract.
GET /v1/diagnostic/routes
GET /v1/diagnostic/registry/faults
GET /v1/diagnostic/registry/modules
GET /v1/diagnostic/registry/sensors
GET /v1/diagnostic/registry/thresholds
GET /v1/diagnostic/registry/repair-protocols
GET /v1/diagnostic/registry/profiles
GET /v1/diagnostic/registry/partners
GET /v1/diagnostic/registry/pack-families
GET /v1/diagnostic/registry/integration-modes
GET /v1/diagnostic/schema/case
GET /v1/diagnostic/metrics
GET /v1/diagnostic/conformance
GET /v1/diagnostic/test-vectors
POST /v1/diagnostic/scan
POST /v1/diagnostic/reviewer-simulate
Use the same schema for site scans, plugin scans, and partner-side integrations. The goal is one engine, multiple surfaces — not drift between products.
Platform routes
GET /v1/platform/routes
GET /v1/platform/workspaces
POST /v1/platform/workspaces
GET /v1/platform/workspaces/:id
GET /v1/platform/workspaces/:id/cases
POST /v1/platform/workspaces/:id/cases/scan
POST /v1/platform/workspaces/:id/cases/:caseId/reviewer-simulate
GET /v1/platform/partners
GET /v1/platform/white-label
GET /v1/platform/profiles
GET /v1/platform/pack-families
GET /v1/platform/integration-modes
GET /v1/platform/partner-program
POST /v1/platform/partner-program/apply
GET /v1/platform/referrals
GET /v1/platform/usage
GET /v1/platform/adoption
GET /v1/platform/conformance/summary
GET /v1/platform/audit