Resource endpoints
The following /v1 routes use bearer authentication. They are an endpoint map, not a promise that every route is exposed through MCP. Evidence operations may additionally require a current session and server-issued route arguments.
Workspace configuration
Use the public ws_… workspace ID in these paths.
| Method | Path | Purpose |
|---|---|---|
GET | /v1/workspaces/{workspaceId}/diligence-settings | Workspace diligence defaults |
GET | /v1/workspaces/{workspaceId}/ai-settings | AI configuration |
GET | /v1/workspaces/{workspaceId}/ai-prompts | Saved prompts |
GET | /v1/workspaces/{workspaceId}/workflow-settings | Workflow configuration |
GET | /v1/workspaces/{workspaceId}/property-definitions | Custom property definitions |
GET | /v1/templates | Workspace text templates |
GET | /v1/templates/{templateId} | One text template, using its public template_… ID |
Projects and tasks
| Method | Path | Purpose |
|---|---|---|
GET | /v1/projects | Select a project in a workspace |
GET | /v1/projects/{projectId} | Project details |
GET | /v1/projects/{projectId}/diligence-settings | Effective project settings |
GET | /v1/projects/{projectId}/overview | Bounded project orientation |
GET | /v1/projects/{projectId}/qoe | Project financial analysis |
GET | /v1/projects/{projectId}/gap-analysis | Persisted checklist coverage |
GET | /v1/tasks | Task list |
GET | /v1/tasks/{taskId} | Selected task |
GET | /v1/tasks/{taskId}/files | Evidence linked to the task |
List responses can be paginated. Follow the returned continuation rather than assuming the first page contains the complete project.
Files and structured evidence
| Method | Path | Purpose |
|---|---|---|
POST | /v1/files/search | Search for candidate source files |
POST | /v1/files/search/batch | Submit independent source searches |
GET | /v1/files | List files in the selected scope |
GET | /v1/files/{fileId} | Selected file metadata |
GET | /v1/files/{fileId}/status | Processing status |
GET | /v1/files/{fileId}/structured | Available file-derived structure |
GET | /v1/structured-data/catalog | Discover supported structured-data schemas |
GET | /v1/projects/{projectId}/structured-artifacts | Discover extracted artifacts |
GET | /v1/projects/{projectId}/structured-data/rows | Query one supported row schema |
POST | /v1/projects/{projectId}/structured-data/rows/aggregate | Governed aggregation over structured rows |
GET | /v1/projects/{projectId}/contract-matrix | Contract and clause inventory |
GET | /v1/projects/{projectId}/file-relationships | Document version and relationship context |
POST | /v1/files/grep | Literal search in processed source text |
POST | /v1/files/diff | Compare two selected source files |
Inspect the catalog before choosing structured fields and filters. Use aggregation for totals and counts when supported. An extracted row or search result routes a reviewer to evidence; it does not replace checking the operative source for a material conclusion.
For an AI integration, use the MCP source workflow, including its exact source and continuation routes. Do not reconstruct source URLs from file IDs or use the retired /content endpoint.
Entities
| Method | Path | Purpose |
|---|---|---|
GET | /v1/entities | Entities in the authorized scope |
POST | /v1/entities/search | Find an entity |
GET | /v1/entities/{entityId}/overview | Selected entity with linked-source context |
GET | /v1/entities/{entityId}/risk | Available risk-domain observations |
GET | /v1/entities/{entityId}/files | Linked evidence |
GET | /v1/entities/{entityId}/graph | Relationship context |
Entity discovery requires an explicit project. Screening observations and relationship hints should be checked against current sources before treating them as identity or risk conclusions.
Requests and comments
| Method | Path | Purpose |
|---|---|---|
GET | /v1/requests | Requests in the selected scope |
GET | /v1/requests/{requestId} | One request |
GET | /v1/comments | Discussion for a selected target |
See Writeback endpoints for supported mutations. Project and entity /bundle routes and the old report routes have been replaced or retired; do not build new integrations around them.