Developer guide
What the developer guide covers today and what is coming.
Developer guide
These docs are for developers building on top of VerifyWise. They cover how to connect your own systems to the platform, with quickstarts, how things behave and API references. For step-by-step help using the screens, see the product guides instead.
What's covered today
The guide covers two areas. Agent Control is how you connect a terminal agent so its tool calls are checked before they run. Claude Code and Cursor have ready-made wiring, and any other agent can use the generic contract. The platform REST API is how you read and write your governance data programmatically with a bearer token.
Agent Control
Agent Control governs what your agent does. Read these in order, or jump to the API reference when you need a specific endpoint.
- Agent Control: how it works: What Agent Control governs and the two ways to connect an agent.
- Connect your agent: Get a tool call checked in about 5 minutes, with wiring for Claude Code and Cursor.
- Connect any agent: The generic contract and the MCP proxy path for any other terminal agent.
- Governing tool calls: The four decisions, approval polling, run correlation and fail-modes.
- API reference: Endpoints, headers, auth and error codes for the tool-call hook.
Platform REST API
Read and write your governance data (projects, risks, vendors, models and more) over REST. Authenticate with a token you create in the app, then call the endpoints listed in the interactive API reference.
- Platform REST API: The base URL, authentication, response shape, status codes and the current limits that apply to every endpoint.
- Working with resources: The CRUD pattern for projects, risks, vendors and more, with the few places they differ.
- Bulk importing datasets: Upload a CSV or spreadsheet to register a dataset through the API.
- Automations API: Create and manage automations programmatically.
- Compliance, reports and exports: Pull compliance progress, generate reports and use the document exports.
- Inbound integrations: Create incidents from another system and submit public intake forms.