Skip to content

Proof artifact index

Inspect the validation evidence behind a completed document job.

Proof is for reviewers who need to validate a result after handoff: redaction checks, preflight reports, evidence bundles, decision logs, provenance ledgers, and API job artifacts. Choose Workflows to understand the multi-step job or Examples to download a representative source and output.

Explore the workflowIntegration overviewProof artifacts

8

Artifact types

8

Workflows

18

API routes

Proof links the surface area together

Each artifact card points to the workflow that creates it, the public PDF that demonstrates it, the screenshot that makes it visible, the toolbox pages that configure it, and the API routes that fetch it.

Workflow recipes
Public examples
Workflow recipes
Proof artifacts
API reference

Coverage currently spans 14 linked toolbox surfaces across review, release, publishing, provenance, and API automation.

ScreensIntegration overview

Proof Artifacts

Verify evidence, reports, ledgers, and jobs.

Artifact catalog

Output types teams can verify, export, and explain

Security posture

Safe release

Redaction verification

Evidence that sensitive text was removed from the generated PDF rather than covered by a visual overlay.

What it proves

Legal, records, and operations teams need proof that release copies cannot leak hidden text through selection, search, copy, or extraction.

Generated outputs

  • Redacted release PDF
  • Removed-text verification report
  • Reviewer exception list

Verification signals

  • Search and copy checks
  • Hidden text inspection
  • Before/after evidence bundle

API routes

POST /v1/processing/redactGET /v1/forensics/{document_id}/redaction-verifyGET /v1/forensics/{document_id}/evidence-bundle
View proof storyExplore the workflowExplore the workflowScreenshotIntegration overview

Publishing readiness

Preflight reports

Standards, accessibility, metadata, and archival checks packaged as a reviewable publishing report.

What it proves

Publishing teams can fix structural issues before distribution and keep a record of the final readiness verdict.

Generated outputs

  • Preflight report
  • PDF/A artifact
  • Accessibility worklist

Verification signals

  • Standards verdict
  • Metadata warnings
  • Reading-order findings

API routes

GET /v1/forensics/{document_id}/standards-preflightPOST /v1/processing/to-pdfa/{document_id}GET /v1/convert/jobs/{job_id}/artifacts
View proof storyExplore the workflowExplore the workflowScreenshotIntegration overview

Governed handoff

Evidence bundles

A packet of generated files, findings, screenshots, route history, and linked source documents for audits or handoffs.

What it proves

Teams can move a PDF from review to release with the context needed to defend what changed and why.

Generated outputs

  • Evidence export
  • Artifact manifest
  • Workspace activity trail

Verification signals

  • Source document lineage
  • Generated artifact list
  • Reviewer and job timestamps

API routes

GET /v1/forensics/{document_id}/evidence-bundleGET /v1/convert/jobs/{job_id}/artifactsGET /v1/documents/{document_id}/versions/activity/feed
View proof storyExplore the workflowExplore the workflowExplore the workflowScreenshotIntegration overview

Review accountability

Decision logs

Reviewer choices, comments, citations, approvals, and exceptions captured alongside the document workflow.

What it proves

Diligence and compliance teams need a compact record of who accepted, rejected, escalated, or revised each finding.

Generated outputs

  • Decision log
  • Cited change summary
  • Reviewer note

Verification signals

  • Page-linked citations
  • Assigned reviewer actions
  • Accepted/rejected finding history

API routes

POST /v1/comparePOST /v1/ai/chatGET /v1/documents/{document_id}/versions/activity/feed
View proof storyExplore the workflowExplore the workflowScreenshotIntegration overview

Document lineage

Provenance ledgers

A durable chain of source files, processing steps, generated outputs, and release artifacts.

What it proves

Operations and compliance teams can prove that an exported packet came from the expected source and transformation path.

Generated outputs

  • Provenance ledger
  • Pipeline run log
  • Artifact lifecycle record

Verification signals

  • Source-to-output chain
  • Processing step timeline
  • Release packet checksum notes

API routes

GET /v1/documents/{document_id}/versions/activity/feedGET /v1/convert/jobs/{job_id}/artifactsPOST /v1/pipelines/{pipeline_id}/run
View proof storyExplore the workflowExplore the workflowExplore the workflowScreenshotIntegration overview

Automation observability

API job artifacts

Machine-readable files, logs, status changes, webhook deliveries, and generated documents from automated PDF jobs.

What it proves

Developers need a predictable artifact lifecycle for polling, webhooks, retries, downloads, and support triage.

Generated outputs

  • Job status stream
  • Downloadable artifacts
  • Webhook delivery log

Verification signals

  • Queued/running/succeeded timeline
  • Retry and error metadata
  • Artifact expiration and download state

API routes

POST /v1/pipelines/{pipeline_id}/runGET /v1/jobs/{job_id}GET /v1/convert/jobs/{job_id}/artifactsPUT /auth/me/webhook
View proof storyExplore the workflowExplore the workflowIntegration overviewIntegration overview

Confidential review

Room access evidence

Recipient gates, grants, watermark maps, revocations, view activity, and export decisions for governed external rooms.

What it proves

Data-room owners need proof of who could access a document, what they viewed, and which policy governed the handoff.

Generated outputs

  • Recipient policy export
  • Watermark map
  • Room activity trail
  • Evidence bundle

Verification signals

  • Grant and deny decision
  • Session and passcode state
  • Preview and download log

API routes

POST /v1/data-rooms/{room_id}/access-checkGET /v1/data-rooms/{room_id}/eventsGET /v1/data-rooms/{room_id}/delivery-artifacts
View proof storyExplore the workflowExplore the workflowScreenshotIntegration overview

Object control

Storage governance reports

Provider health, signed URL decisions, object metadata, migration dry-runs, and checksum verification for workspace storage.

What it proves

Platform teams need to prove where document artifacts live, how temporary access is granted, and whether migration is safe.

Generated outputs

  • Provider health summary
  • Signed URL policy log
  • Migration dry-run report
  • Object audit ledger

Verification signals

  • Provider capability check
  • TTL and scope decision
  • Checksum and dual-read status

API routes

GET /v1/admin/storage/providers/diagnosticsPOST /v1/admin/storage/signed-url/previewPOST /v1/admin/storage/migration/rehearsal
View proof storyExplore the workflowExplore the workflowScreenshotIntegration overview

Developer handoff

Fetch artifacts through the same job lifecycle your app already watches.

Proof artifacts line up with jobs, pipeline runs, webhooks, and document activity. Start in the API matrix, copy a language recipe, then use the demo to preview which outputs a selected public PDF workflow should generate.

Integration overviewIntegration overviewTry builder

Start from a workflow

Trace secure intake, FOIA release, diligence review, publishing preflight, AI knowledge, and batch automation.

Compare public PDFs

See which source documents exercise each tool chain, screenshot, API route, and generated output.

Inspect API artifacts

Open the product story for job artifacts, webhook signals, and automation observability.