getProjectVerification

Read as Markdown

GET /api/v1/project-evidence/{evidenceId}/verification/{verificationId}

Versioned acceptance statements, actor-attributed claims and supplied evidence. Independent resource/source authorization precedes summaries, relations, report reads, export and retries. Passing reports and imported references stay reported and cannot establish human acceptance. Reports are inert bounded text with digests, redaction diagnostics and retention; verification writes are reserved for trusted CP-022 adapters. Context query parameters use a JSON-encoded typed reference.

Access

Use a credential with commentary.evidence.read.

Provider access, workspace membership, and agent grants are enforced separately. A token does not expand access to a repository or resource. Set up developer access.

Parameters

Name	Location	Type	Required	Description
evidenceId	path	string	Yes
verificationId	path	string	Yes

Call the endpoint

Replace path placeholders and your credential. For body operations, create request.json using the required fields above; this command does not invent resource identifiers or consent.

curl --request GET \
  'https://commentary.dev/api/v1/project-evidence/<evidenceId>/verification/<verificationId>' \
  --header 'Authorization: Bearer <your-token>'

Responses

Status	Meaning	Payload
200	Authorized domain result with the exact applicable ETag.	ProjectAgentgetProjectVerificationOutput
400	Bounded v1 machine-readable failure.	object
401	Bounded v1 machine-readable failure.	object
403	Bounded v1 machine-readable failure.	object
404	Bounded v1 machine-readable failure.	object
409	Bounded v1 machine-readable failure.	object
412	Bounded v1 machine-readable failure.	object
413	Bounded v1 machine-readable failure.	object
422	Bounded v1 machine-readable failure.	object
428	Bounded v1 machine-readable failure.	object
429	Bounded v1 machine-readable failure.	object
500	Bounded v1 machine-readable failure.	object
503	Bounded v1 machine-readable failure.	object

Successful response fields

Field	Type	Required	Description
data	ProjectAgentVerification	Yes
idempotencyReplayed	boolean	No

Recover from errors

Use the returned status and error body. Correct invalid fields before retrying; reconnect or narrow the target for authentication and permission errors. For conditional writes, reload the latest version before preparing a new request. Respect rate-limit headers and retry only when the operation’s idempotency contract permits it.

Contract and related guidance

Operation ID: getProjectVerification. Download the OpenAPI contract for complete constraints and code generation. Browse endpoints.