DocsBook a demo

Platform

Platform overviewArchitectureWorkflow orchestrationGitOps configurationGovernance and AAAAI and MCPKnowledge and contextRuntime and executionEvidence and monitoring

Use cases

All use casesProduction incidentRelease preparationHotfix to productionSecurity scan triage
Why NopsAIIntegrationsSecurity

Resources

All resourcesAI agent governanceMCP governanceMCP securitySelf-hosted platforms
PricingGitHub

Company

How a run worksAboutContactBook a demo

All REST endpoints

Every documented route with method, access class, and purpose, grouped by area.

ReferenceDeveloperOperatorAdministrator

Key points

  • Public routes need no token. Authenticated routes need any valid token. Authorized routes additionally pass an AAA check on the target resource.
  • Administrator routes require the platform administrator role.
  • Service token routes are internal component traffic and are not part of the public surface.
  • Filter by area or search by path fragment to find the route you need.

How it works

Access class describes the gate before resource-level checks. An "authorized" route can still return an empty list if the caller has no matching resources.

Implementation evidence

  • services/nopsai/routes.go

    Route registration for every area.

  • doc/api.md

    Request and response shapes.