Integrate with a coding agent
Give your developer or coding agent the same public contract and preserve human decisions.
On this page
Start with public documentation
A coding agent can read these guides and the OpenAPI document without access to your workspace. Ask it to inspect your existing integration conventions and verify available operations before writing code.
Read https://assurance.nexusregen.com/developers/quickstart and the linked current API reference. Inspect this repository and help me map my workflow to Nexus Assurance. Explain movement/load grouping, minimal scopes, retries, corrections, and human-action boundaries. Check published availability before using an endpoint. Keep secrets in server configuration. Use only a supported isolated sandbox for test writes; if it is unavailable, explain the missing prerequisite instead of writing to production.Fetch only the guidance you need
Each guide is available as Markdown from the same source as this page. The documentation index helps a coding agent discover relevant pages; it is not a guarantee that every coding client supports automatic discovery.
Workspace access through customer MCP
The customer MCP connection acts on a consenting user’s authority in an organisation. REST credentials are for unattended server integrations. Reading documentation does not require MCP consent.
Manage customer connections and revoke access in Settings → MCP. Only grant the access needed for your task. The tools page includes the versioned portable integration kit; it does not grant live MCP data access.