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

API

The REST surface: what authenticates against it, how routes are organised, and the complete endpoint list.

API

ReferenceREST APIHow the API is structured, what authenticates against it, and where the complete route list lives.TutorialCalling the APIOne worked path from a login to a run: get a token, call a route, read the response, and handle the failure modes.ReferenceAuthentication APILogging in, refreshing, logging out, minting personal tokens, and the two browser flows that hand identity over from a provider.ReferencePlatform probesThe five routes that answer without a token, and what an operator should assert on each.ReferenceFirst-install setup APIThe unauthenticated routes that diagnose and complete a first install, and the one write that runs exactly once.ReferencePipelines and steps APIReading, validating, saving, and deleting pipeline and reusable step definitions.ReferenceRuns APIStarting runs, reading their state and logs, deciding their approvals, and handling their deliverables.ReferenceExternal triggers APIDefining an entry point another system may call, invoking it safely, and diagnosing a caller that believes it is being ignored.ReferenceVariables and secrets APIThe three stores behind runtime configuration, and which action decides who can recover a stored secret.ReferenceSchedules APIStoring an intent to run a pipeline later, and testing it without waiting for the clock.ReferenceGit integration APIThe two ingress routes providers call, the managed sources that verify them, and the overrides that decide what a repository runs.ReferenceAccess control APIGranting access, revoking it, and asking the platform what a caller may actually do.ReferenceIdentity administration APIAccounts, service accounts, tokens, roles, identity providers, and the audit log that records what they all did.ReferenceGitOps and config sync APIConnecting configuration repositories, syncing from them, reviewing drift, and pushing desired state back.ReferenceTeams APIThe ownership tree, the applications under it, and the team-owned models, agent roles, and MCP profiles.ReferenceAI configuration APIThe three registries a pipeline draws on: model profiles, agent roles, and MCP servers and profiles.ReferenceAssistant and AI surfaces APIConversations, pipeline evaluation, and the hosted MCP endpoint — all running as the calling subject.ReferenceKnowledge Context APIGoverned documents merged into LLM context, and the provider connections that import them.ReferenceMonitoring APIAnalytics over runs, performance, AI usage and security, plus recommendations, alert rules, and saved views.ReferenceDashboards APIDashboards, sections, source bindings, publication history, refreshes, and refresh schedules.ReferenceSystem operations APIRuntime configuration, the runner fleet and its install generation, platform logs, mail delivery, and the data lifecycle.ReferenceInternal service routesComponent-to-component traffic: what calls each route, why it exists, and why none of it is a public surface.ReferenceAll REST endpointsEvery documented route with method, access class, and purpose, grouped by area.